Re: Spamcop failing to detect true originating IP

wskrispy <[email protected]>
Newsgroups gmane.mail.spam.spamcop.help
Organization SpamCop
Message-ID <[email protected]>
Mike Easter wrote:
> wskrispy wrote:
> 
>>Why is SC suddenly unable, or
>>suddenly unwilling, to see them?
> 
> 
> We can't see the spam or the parsing unless you post the tracking url.
> 
> Put a spam like you are describing into the parser and copy and paste
> the tracking url from the top of the page here.
> 
> Here is your TRACKING URL - it may be saved for future reference:
> http://www.spamcop.net/sc?id=z784681180z3e1208e47d5955be1126a5a1f83d78e9z
> 
> 

Thanks for the responses guys. It looks like the Spamcop parser was 
choking on headers crammed into the email by our SpamAssassin. I don't 
know why Spamcop wasn't previously choking on these... I don't think 
they've changed. I also don't think any ISP-related stuff has changed.

In any case, when I trim the source down to the bare minimum with just 
the originating headers Spamcop is now accepting it (I could have sworn 
I tried this a few days ago and it choked). Ah well, it would be 
interesting to get into it more but other duties call.

--
wsk
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.