Re: Spamcop failing to detect true originating IP

"Brian (SnSR)" <[email protected]>
Newsgroups gmane.mail.spam.spamcop.help
Organization SpamCop
Message-ID <[email protected]>
WazoO wrote:
> "wskrispy" <[email protected]> wrote in message
> news:[email protected]...
> 
>>Hiyas. I'm no antispam maven and don't have much ambition to become one,
>>but I've been using the Spamcop website sporadically over the last few
> 
> 
> However, doing some legwork may help resolve the issue.
> 
> 
>>months to report a bunch of spams with originating IPs not already in
>>the SC blocking list. About 5 days ago the SC site seems to have
>>changed. Apparently the parser progs are treating my pasted spams
>>differently.
> 
> 
> I'm not aware of any change.  There's not a flood of folks making
> the same claim.  So, the imnplication is that something changed on
> your end.  Coincidemtally, a thread in the spamcop newsgroup
> reads pretty close to the same story, but the result turns out to
> that the user's ISP decided to implement some brain-dead
> filtering on outgoing e-mail, such that the SpamCop submittals
> were seen as virus infected due to the attached .eml file (the
> forward as attachment of the spam) and the ISP's e-mail
> habdler decided to put a big warning about the virus into the
> outgoing e-mail, which of course screwed it up entirely as fas
> as the SpamCop parser was concerned.
> 
> Test: CC: your next submittal to an off-site address such that
> you can see what your ISP might be doing to your outgoing.
> .

He is copy/pasting into the web page, not forwarding, so the above is 
irrelevant.

> 
>>I quickly set up Mailhosts just now but the problem remains. I guess
>>I'll have to read more to see if my Mailhosts setup is correct, but like
>>I said I don't plan to get too deep into this. I'm on vacation from
>>heavyduty putering for at least a year.
> 
> 
> I believe you'd have a whole different set of error messages if
> your MailHost configuration was wrong ..
> 
> 

I've had the same error message a number of times in the past, but, at 
the moment, I don't recall what the cause of it was. It would be helpful 
to share a tracking URL so someone may be able to figure out what the 
problem is.
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.