[SpamCop-List] Re: X-MDaemon-Deliver-To header not masked

[Mike Easter]

Filip wrote:
> My Mdaemon mail server uses flag X-MDaemon-Deliver-To flag to
> identify the final receipient. This flag is not masked out in the
> reports, revealing a real email address at my domain.
>
> See these examples:
>
http://www.spamcop.net/sc?id=z764730835z3459769545f263d6db7e83e8f08cf0c5z
>
http://www.spamcop.net/sc?id=z764730823z725e3366f4b780408381b856bdb87342z
>
> Is there anything that can be done about this?

IMO you could interpret the rule faq about Material changes to spam in a
way which would allow you to pre-munge that line before submitting it to
the parser.  For example, you could delete the line.

As a general rule, deputies don't like to give permission to change a
spam in any way which isn't covered directly by the faq, and the faq is
about mungeing your address in the body of a link, not deleting a
headerline.  However, you aren't helping the faq to identify anything.

http://www.spamcop.net/fom-serve/cache/283.html  Material changes to
spam  --  It is okay to munge your personal email address contained
within links in the body of the spam, if SpamCop does not find and munge
them, with one exception. If a report is going to an abuse desk that
does not accept munged reports, you must not make even these minor
changes to the spam.




-- 
Mike Easter
kibitzer, not SC admin