Jump to content
Sign in to follow this  
aryant

Server discarded as fake-Message Source scrambled?

Recommended Posts

I've been with SpamCop a couple of years and recently was blocked from reporting spam because the system was reporting my company's servers. It got complicated because Anteon, my original employer recently was bought out by General Dynamics. My mail now goes to myaddress <at>gdit.com where it is forwarded to myoldaddress<at>anteon.com and then to spamcop.

I requested a waiver, which will probably fix that, but I noticed something odd about the test mail response. When I captured test mail using Message Source the first time, the response was that there was an unnecessary line break (see below), I took that out and now get

"Host ns-util1.anteon.com (checking ip) IP not found ; ns-util1.anteon.com discarded as fake." (As well as traversing more than one domain)

I noticed that the list of IP addresses was also screwy, see the part right after the local test IP, 127.0.0.1

and the two octets just before the last IP. There are 5 odd octets in there, no wonder the robot got confused. I tried replying using IE and Firefox, both came up with the scrambled IP list.

As I said, the waiver will probably fix me up but I thought it worthwhile to point out this strange response. I have the URL from the test mail message, I'm going to send it to deputies<at>... but also offer it here to see if anyone has any useful comments.

X-SpamCop-Checked: 192.168.1.105 216.154.195.36 192.168.1.101 62.241.163.103 62.241.163.20 198.185.182.157 10.170.1.164 4.1.11.41 10.160.0.203 10.160.0.2 63.161.60.61 3.1.0.29 127.0.0.1 64.18.1.204.15.82.24 64.18.5.10 86.2.118.120 62.254.128.6

18.120 62.254.128.6

Share this post


Link to post
Share on other sites

It's been quite a while with no follow-up .. did the waiver request solve anything?

As far as the odd octets, not much of a chance to analyze here with no data. Seeing the actual headers would go a long way, usually offered here as the content of a Tracking URL. Though one would think that by now the ISP(s) involved would have straightened out the issue.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×