Quick address getting bounced

[jeffih]

Hi Guys,

We recently did a upgrade and emails forwarded to quick address are bounced with error like

----

SpamCop encountered errors while saving spam for processing:

SpamCop could not find your spam message in this email:

----

Even if the email don't contain spam it should not contain first line rite ? and subject of the email shouldn't be "Subject: [spamCop] Errors encountered".

Is this an issue with quick address or Mailhost configuration or in- proper header. Is there any other possibility for this error.

We could try resetting the quick address.

How do i do Mailhost reconfiguration ?

Also if possible , if we can get a corrected email header , we can try re-writing the header according as last resort .. Hope that won't be necessary.

Thnks

Jeffih

[turetzsr]

...Moved from the "How to use .... Instructions, Tutorials > SpamCop Reporting" Forum (described as "System parts & Functions not fully explained under an existing Help menu / option .... Questions still needed to be asked about How to use/do something are to be posted into that function's Forum section.") to the "SpamCop Reporting Help" Forum, since this inquiry has to do with that functionality.

[jeffih]

Hi turetzsr,

Sorry.. i thought this was reporting section. thanks

thanks

jeffih

...Moved from the "How to use .... Instructions, Tutorials > SpamCop Reporting" Forum (described as "System parts & Functions not fully explained under an existing Help menu / option .... Questions still needed to be asked about How to use/do something are to be posted into that function's Forum section.") to the "SpamCop Reporting Help" Forum, since this inquiry has to do with that functionality.

[Lking]

Is this an issue with quick address

my quick reporting is working just fine.

[turetzsr]

<snip>

We recently did a upgrade

...Maybe the problem lies there?

<snip>

Is this an issue with <snip> Mailhost configuration <snip>.

How do i do Mailhost reconfiguration ?

...It's essentially just deleting the existing one(s) and going through the same steps as the initial setup. See if the following help you (you may need the second if the first isn't complete enough):

• dbiel's reply in SpamCop Forum article "'Spamcop encountered errors' - perhaps my fault?"
  
• SpamCop Wiki article "Mail-Host Configuration of your Reporting Account."
  

...If all else fails, see "Mailhost Issues - please read before posting."

...Good luck!

[jeffih]

We suspect that spamassassin is doing some thing to the header and you guys need the non-modified header. Is there a way to over come this ?

[Lking]

We suspect that spamassassin is doing some thing to the header and you guys need the non-modified header. Is there a way to over come this ?

You are correct SpamCop needs a "non-modified header." If your analysis is correct, what you seem to be suggesting is that SpamCop should make changes to overcome what spamassassin is doing to the header.

I'm sure you understand from a programming standpoint, that is a rabbit hole no one would want to go down. Besides if SpamCop were to act/report based on a modified header, it would bring into question the validity of all of their reports.

[SpamCopAdmin]

SpamAssassin should be simply adding X-Headers, as opposed to removing the spam and attaching it.

SpamAssassin vs 'localhost' headers:

The parameter is report_safe

report_safe = 0 indicates "add x-headers"

It may be found in local.cfile or .userprefs file depending on the SA setup.

- Don D'Minion - SpamCop Admin -

- service[at]admin.spamcop.net -