[Mailhost problem fixed --]

and in reference to your "Please post any problems with mailhosts in the already started topics" ....  this posting was not made in http://forum.spamcop.net/forums/index.php?showtopic=723

In conjunction with previous complaints / suggestions about the Pinned items, this post had already slid off the first page of this particular Forum.

Would you (as I haven't seen Julian posting much lately) then respond to my last post on that above referenced Topic (and admitting that due to the above, I had not seen that you had in fact posted this info here.)

5330[/snapback]

??????

[Mailhost Update]

When you receive your mailhost probe you will now notice that there is a url in it that leads to a webform where you can copy/paste in the complete headers from the probe and also the body of the probe. Once you do that and click the button you will find out immediately whether the mailhost was added or whether there was a problem -- no more waiting for a confirmation or error email. This should make things much easier.

As always -- make sure your add *ALL* your mailhosts before reporting *any* spam. Do *NOT* user quick reporting or the report as spam button in webmail for at least 2 or 3 days until you are sure that all your spams are parsing properly. Look at the parse output carefully and if you have any questions either post the tracking url here or send it deputies <at> spamcop.net with your questions, the tracking url and your registered SpamCop email address. Please put "mailhosts" somewhere in the subject line.

Thanks

[Mailhost Issues - please read before posting]

If you have problems with mailhosts -- 1) registering new hosts; 2) returning probes; 3) spam parses or other issues you may post in this forum. However other than very general responses I will need you to write to deputies service[at]admin.spamcop.net with "mailhosts" in the subject line.

In the body of the email describe your problem, include your registered SpamCop email address and if the issue involves a parse you *must* include a report number or a tracking url. You can include the snippet from the parse that concerns you but without a report number or a tracking url I will not be able to look at the issue. Do not include the spam because I *cannot* parse your spam.

Julian IronPort/Cisco staff continue to squish bugs and to write code to make the system more accourate and easier to use. Yes it is a bit mind boggling if you have many email addresses at different ISPs/hosting companies but the good news is that once it done, it is done.

Thanks for your patience, persistence and helP!

Edit by SteveT to [temporarily?] change the SpamCop Admin e-mail address due to a report of service[at]admin.spamcop.net bouncing.

[Mailhost problem fixed --]

Julian discovered a small problem with the mailhosts logic which apparently started early today (perhaps last nite) which was preventing the system from sending the confirmation message after a probe mail was copy/pasted or forwarded back. The problem has been fixed and you should be able to resend the previous probe mail. If you encounter problems please let us know. Sorry for the problem.

Please post any problems with mailhosts in the already started topics.

[Mailhosts and Quick Reporting]

When a user first starts to add a mailhost (they click on add new host), a

flag "noquick" gets set in their account.

When they submit spam using VER from the held mail page, the quick report

option is nonexistant and is replaced with the text "Quick reporting

prohibited - see mailhosts menu item".

When they submit spam using Jeff's "report as spam" or they forward spam

to the quick submit address, they receive back the normal reply as if they

had done a regular submit. Included in that reply is this text:

"Quick reporting is prohibited until mailhost configuration is verified.

Please report some spam received at each of your mail accounts manually,

check the results carefully. When you are satisfied, use the mailhosts

menu item to re-enable your quick reporting function."

When users are in this mode, they can visit the mailhosts page from the

main menu and see this "

Remove quick-reporting prohibition

If you are sure your mailhost configuration is working correctly, you

may lift the ban on quick reporting here. Please ensure it does work

by manually submitting and checking the spam report before sending it.

Do not proceed unless the spam report appears to work correctly (does

not identify your own service provider as the spam source).

<Allow quick reporting>"

And finally, on the "you must agree" add-mailhost page, I've added this

paragraph: "

SpamCop will initially prohibit "quick reports" (available to

SpamCop email users) from your account.

When you have tested reporting spam from all your mailhosts, you will

be allowed to end this prohibition. Please double-check all your spam

reports until you are satisfied that SpamCop correctly understands your

configuration."

I intend to keep this basic functionality beyond the beta period. It will

be SOP for anyone adding mailhosts going forward.

In addition, users who have successfully configured all mailhosts they

have tried to configure do not have to re-confirm. However, usres who

still have partially-configured mailhosts were imported, so they do have

to confirm before they can do any more quick reports.

-=Julian=-