Sorry, SpamCop has encountered errors:
Confirmation codes do not match:

From recipient address: Fvk...A7h [and 43 blank chars]
From header: Fvk...A7h
From body: Fvk...A7h

Could it be possible to teach Mailhosts to forget these blank chars ?

It would be nice but right now it doesn't so you need to remove them.

Yes, it should be. It's OK now, thanks for all.

remove them how? and where? how is it okay? what did you do?



Confirmation codes do not match:

From recipient address: GC.....yh
From header: GC.....yh
From body: GC.....yh


THEY ARE EXACTLY THE SAME! Is there an example of ones that DO match? I'd like to see what that looks like. Why is this a problem at all, its ridiculous.

Look for blank spaces at the end of the lines. Delete those spaces before sending in the reply.

Some email systems appear to be adding spaces to the body of the message being sent. Those are the systems having this problem.

There are problems with the way that some mailservers return headers and also some problems with the way that some email apps display the headers to be returned. Some of the problems include bad wrapping of header lines and excess carriage returns/line feeds. Other problems include mailservers that remove or incompletely pass along X-headers.

I had this problem and resolved it successfully by removing the blank spaces at the end of some lines. The blanks do not appear on every line and range from 1-3 spaces where they do appear.

My question: how will this impact the operation of the service? I am fairly diligent about reporting spams, even though it seems futile in many cases (for example, chinanet). If I will need to edit every header to remove blank spaces, the reporting, however valuable, becomes too much work.

The removing of spaces is ONLY needed when returning the probe during mailhost configuration. You do not need to modify the spam messages.