[SC-Help] Re: Spamcop treats MX differently depending on where it appears in chain

[Mike Easter]

You have no need to know wrote:
> I am seeing problem when my ISP's mail servers don't report the name
> that
> Spamcom expects in their received line.

SC has an algorithm by which it chains from upper 'from' field IP to the
preceding lower 'by' field hostname and 'considers' the chaining for
integrity based on a combination of what I call 'mx-ness' and SC's
familiarity with the apparent relay, eg if it has been previously sent
to relay testers.  This also requires correlation between the rDNS of
the IP compared to the hostname.

If too many things don't fit, non-mx, unfamiliarity, poor rDNS
relationship -- then SC can't make what I call the 'mx step' and it is
forced to break the chain instead of chaining from the upperline to the
lower line toward the sourceline.

That leads to the server being named as source instead of the source
from which the server received the item.

There are alternate solutions to that problem.  Sometimes the problem
can resolve as familiarity develops.  Sometimes the problem can be
resolved if the rDNS works properly.

The most reliable solution is to engage the mailhosts option.  It is
necessary that the mailhost setup involve any 'variations' from each
other.  The idea is to provide SC with a template of your mailhost's
[stupid] inconsistency.


-- 
Mike Easter
kibitzer, not SC admin