nei1_j Posted May 15, 2011 Share Posted May 15, 2011 http://www.spamcop.net/sc?id=z5004958781z8...d18ce35c923b57z Link to comment Share on other sites More sharing options...
Wazoo Posted May 15, 2011 Share Posted May 15, 2011 http://www.spamcop.net/sc?id=z5004958781z8...d18ce35c923b57z Topic Title suggests no linkage to the Forum Section posted into .... SpamCop Reporting Help > Routing / Report Address Issues Moving into the SpamCop Reporting Help section with the Post. Link to comment Share on other sites More sharing options...
SpamCopAdmin Posted May 15, 2011 Share Posted May 15, 2011 Received: from 41.206.12.38 by rms-us002.v300.gmx.net with HTTP The reason the parse fails is because SpamCop is finding 41.206.12.38 as the source of the spam, and there is no date in that "Received" line. Why SpamCop is finding 41.206.12.38 as the source is a completely different matter. 0: Received: from 127.0.0.1 (HELO mailout-us.mail.com) (74.208.5.67) by mta1220.mail.sk1.yahoo.com with SMTP; Sat, 14 May 2011 12:46:54 -0700 Hostname verified: mailout-us.gmx.com YahooMain received mail from Comcast ( 74.208.5.67 ) 1: Received: from 41.206.12.38 by rms-us002.v300.gmx.net with HTTP No unique hostname found for source: 41.206.12.38 Comcast received mail from sending system 41.206.12.38 Those parse statements are just wrong, and I don't know why. (HELO mailout-us.mail.com) (74.208.5.67) is definitely not part of Comcast, and neither is rms-us002.v300.gmx.net. I'm looking into it. - Don D'Minion - SpamCop Admin - - service[at]admin.spamcop.net - . Link to comment Share on other sites More sharing options...
nei1_j Posted May 18, 2011 Author Share Posted May 18, 2011 Thank you Wazoo and Don D. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.