Jump to content

[Resolved] Parser reporting ligitimate relay, not spam source


dzaidle

Recommended Posts

For som time now, the parser has consistently interpreted spam to/through my server's relay as the source, rather than the actual source IP.

While I realize that "X-Originating-Ip:" [62.214.232.88] can be spoofed, in this cas it isn't but the parser ignores it.

Any suggestions I can pass on to the server admin appreciated.

A sample tracking link and the associate original header below:

LINK

http://www.spamcop.net/sc?id=z1405828583z7...49c079b7df6166z

HEADER

Return-Path: <xxx[at]axisbancorp.com>

Received: from gate11.r4.iad.mlsrvr.com (gate11.r4.iad.mlsrvr.com [192.168.1.90])

by mail18b.r4.iad.mlsrvr.com (SMTP Server) with ESMTP id BFB283E3AD1

for <xxx[at]fishgame.com>; Thu, 23 Aug 2007 16:07:22 -0400 (EDT)

Received: from gate20.gate.sat.mlsrvr.com (sat6.emailsrvr.com [64.49.219.6])

by gate11.r4.iad.mlsrvr.com (SMTP Server) with ESMTP id 9A4508A8104

for <xxx[at]fishgame.com>; Thu, 23 Aug 2007 16:07:22 -0400 (EDT)

X-Virus-Scanned: OK

X-spam-Flag: NO

X-spam-Score: 1.002

X-spam-Level: *

X-spam-Status: No, score=1.002 tagged_above=-100 required=6

tests=[html_MESSAGE=0, RCVD_IN_SORBS_DUL=0.001,

URIBL_DNSBL_BLAGR3=1.001]

X-Originating-Ip: [62.214.232.88]

Received: from i3ED6FBEC.versanet.de (i3ED6E858.versanet.de [62.214.232.88])

by gate20.gate.sat.mlsrvr.com (SMTP Server) with ESMTP id 5C9AC1B409C

for <editor[at]fishgame.com>; Thu, 23 Aug 2007 16:07:20 -0400 (EDT)

Received: by 10.22.63.10 with SMTP id JSjFkIBQXXSQz;

Thu, 23 Aug 2007 22:08:08 +0200 (GMT)

Received: by 192.168.235.50 with SMTP id WkXRLnRxjMXWvF.3871365883681;

Thu, 23 Aug 2007 22:08:06 +0200 (GMT)

Message-ID: <000301c7e5c1$4fe1dec0$ecfbd63e[at]Linda>

From: "sebastian bustin" <sebastian-bustin[at]axisbancorp.com>

To: <editor[at]fishgame.com>

Subject: reckhard

Date: Thu, 23 Aug 2007 22:08:03 +0200

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----=_NextPart_000_0008_01C7E5D2.136AAEC0"

X-Priority: 3

X-MSMail-Priority: Normal

X-Mailer: Microsoft Outlook Express 6.00.2900.3028

X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028

X-Antivirus: AVG for E-mail 7.5.484 [269.12.2/967]

Link to comment
Share on other sites

MailHost Configuration of your Reporting Account may or may not help. try selecting "show full Technical details" on your preferences and take another look at your example Tracking URL ... quite a mess ... based on previous issues from others, it may boil down to some 'internal' spam filtering mechaniss involved in the mlsrvr.com sever farm ..... but, MailHost Configuration would be the first thing to try .....\

Noting also that if the host makes additional / further changes in the future, you will probably have to adjust your MailHost Configuration again ....

Link to comment
Share on other sites

MailHost Configuration of your Reporting Account may or may not help. try selecting "show full Technical details" on your preferences and take another look at your example Tracking URL ... quite a mess ... based on previous issues from others, it may boil down to some 'internal' spam filtering mechaniss involved in the mlsrvr.com sever farm ..... but, MailHost Configuration would be the first thing to try .....\

Noting also that if the host makes additional / further changes in the future, you will probably have to adjust your MailHost Configuration again ....

Thanks Wazoo et al. I will do the Mailhosts configuration route and see how it goes.

DZ

Link to comment
Share on other sites

That did it!

Thanks so much, guys, for the help.

DZ

Hi, DZ,

...You're quite welcome!

...Thank you for taking the time to return here and let us know the good news. As such, I shall mark this thread as "Resolved." :) <g>

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...