-----SPAM----- appearing in emails (from nowhere!)

Associate
Joined
19 Jun 2003
Posts
1,680
Location
West Yorks, UK
Hi all,
I have a real puzzler. I've been trying to track down a problem with "-----SPAM-----" appearing in email subjects out of the blue. What happens is this:

1) Message from User A arrives in User B's inbox with subject "Help!" (as an example)
2) User B replies to this message
3) Message arrives in User A's inbox with subject "-----SPAM----- RE: Help!"

The odd thing is, there is no outbound spam checking on User B's site, and User A can vary - the majority of emails are from @hotmail.*, but there are a handful coming in from other companies too. User B is running VPOP3 email server, which is configured fine (and has been running OK for a while now). User B also has an SPF record setup on their domain name allowing mail to be relayed through their webhost's server. This server is listed on the www.spamcannibal.org list, but as a generic listing (for the whole webhost).

I'm really stumped as to where this text in the subject is coming from. I've tried sending test messages to my own Hotmail and GMail accounts, and it doesn't get re-written. Anyone got any ideas on what I can do to track it down?

Matt
 
Sounds like the webhosting may be running some sort of spam filtration.

a low level usually inputs the word "spam" into the subject line to advise the email is suspect.

Higher levels generally remove mail before delivery dependant on a rule set of banned words.

Check the control panel for the hosting to see.
 
Its probably the isp at the receiving end. Blueyonder/virgin for example does this and adds *spam* to certain suspect mails.
 
I've started getting this recently, the most common email to have ***SPAM*** inserted into the subject is the Overclockers newsletter. I'm on Virgin so I guess the post from modo77 explains it.
 
Ah, that starts to drop into place. I am responsible for the sending server, so am happy the ---SPAM--- isn't being inserted in the sending server. Therefore, i guess it must be on the receiving end. The sending domain has an SPF record to help get mail through, but it seems this may not be working. The other thing that might be causing it could be that VPOP3 is not structuring email in a particular way to get past some more advanced spam filters.

Need to do some more digging it seems!

Matt
 
Back
Top Bottom