[SpamCop-List] Re: Whoops!

[Mike Easter]

Leon Mayne wrote:
> Accidentally reported my own mailserver again, as we've just
> installed new mailgates which arn't on the trusted relay list. Any
> chance of adding them?
>
www.spamcop.net/sc?id=z756775918z67addfe610800c23841c8114f3b49299z

Jeez -- what is it that junks up those headers so bad?  Those 2
different sections called 'X-Spam-Report' are an abomination.

The two of them combined add 83 lines to the header, and/while the whole
spam is only about half as long as those 'reports'.

That tracker doesn't look like it was done by a mailhosts parse -- but I
think you can configure mailhosts yourself most of the time and
generally the deputies only have to help out if there's trouble and it
isn't working properly..

Now, to the issue of the parse which mistakenly names your server.

That's one of those where SC is bailing 'for no apparent reason' after
it has already [apparently] accepted the important line:

Received line accepted
219.232.166.170 discarded as a forgery, using 139.222.130.186

The Received line which was accepted was the one which made
219.232.166.170 the appropriate target, and then SC abruptly bails on
the project.  That causes your server to be named.  Maybe this is a case
of SC not being familiar with the server yet.  I agree that mailhosting
it would fix the problem.

We were messing with one of these the other day of a similar 'mistake
configuration' - but it was correctable by tinkering - which this one
isn't, which is why I currently think it is an unfamiliar server.

-- 
Mike Easter
kibitzer, not SC admin