[SpamCop-List] Re: Spamcop Unable to Trace Source of these "Pump 'n' Dump" Spams

[Mike Easter]

Ron B. wrote:
> Spammy now seems to be able to avoid using known IP.
> I've gotten several of these stock spams:
>
www.spamcop.net/sc?id=z851618420z37f098e8234c7477b2fdfc220b4cf8fbz

You are using a mailhosted account, and something is wrong with how it
has been configured compared to the headers submitted to the parser, so
SC sez

// Possible forgery. Supposed receiving system not associated with any
of your mailhosts
Will not trust anything beyond this header
No source IP address found, cannot proceed. //

because the mailhost configuration is happening right at the top from
cesmail to cotse.

If I take the same spam and submit it to a non-mailhosted account parse,
it will be properly parsed

http://www.spamcop.net/sc?id=z851738459za9dd30d1ce32b3cc1f9e41897544170bz
Report Spam to:
Re: 70.105.134.14 (Administrator of network where email originates)
   To: abuse at verizon.net (Notes)

If you didn't configure for a mailhost in which SC is forwarding to a
cotse server that stamps its line like that, you will need to
reconfigure your mailhost, as SC suggests in the error

// Add/edit your mailhost configuration //



-- 
Mike Easter
kibitzer, not SC admin