[Helpdesk] FW: Delivery Status Notification (Failure) spam filter??

K.A. Rodgers krisrodgers at msn.com
Sun Jan 29 14:04:00 MST 2006


Can anyone help with this?

My e-mails are being blocked by the intended recipient's spam filter.

Below is the diagnosis (not sure how they did it). Is it correct?

I have Norton Anti-virus, and the virus definitions are updated weekly. I
don't know what else to do. I haven't had this problem with any other
recipient.

Also, I don¹t know how to contact my ISP, which is msn, about this type of
problem ‹ except to call them. They don¹t seem to have any electronic
spam-reporting procedure. Has anyone else dealt with msn for this type of
thing?

Thanking you in advance.


Subject: RE: Delivery Status Notification (Failure)

Cathy and Ms. Rodgers

The message from Ms. Rodgers indicates that it was blocked from an IP
address of "65.54.249.91".

Researching where the message came from, it appears that Kris Rodgers
has had her email compromised with an attached spam.  The site below
gives some information about the attachment that is making her email
denied by our server.

http://www.urgentmessage.org/highlyconfidential/_l25126.html

http://www.urgentmessage.org/IPfreely/_i?filter=65.54.249.91

More information about the number of people who are sending email with
the same attached spam.

http://www.senderbase.org/search?searchBy=ipaddress&searchString=65.54.2
49.91

Last but not leaset is a spam trace on the IP address that has created
the compromise to Ms. Rodgers.

http://www.spamtrace.info/email/13885/

My suggestion to Kris Rodgers is that she use her virus checking
program, update the software, and make sure she keeps up updated weekly.

***
BELOW IS THE MESSAGE THAT BOUNCED, WITH VIEW HEADERS ON (I have deleted
recipient's addresses):

------ Forwarded Message
From: <postmaster at mail.hotmail.com>
Date: Fri, 27 Jan 2006 18:52:49 -0800
To: <krisrodgers at msn.com>
Subject: Delivery Status Notification (Failure)

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.


Reporting-MTA: dns;hotmail.com
Received-From-MTA: dns;mail.hotmail.com
Arrival-Date: Fri, 27 Jan 2006 18:52:47 -0800

Final-Recipient:
Action: failed
Status: 5.2.1
Diagnostic-Code: smtp;550 5.2.1 Mail from 64.4.51.86 refused: spam site.

------ End of Forwarded Message

X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtIDHQuM5FgLk=
Received: from omc1-s34.bay6.hotmail.com ([65.54.248.236]) by
bay0-mc4-f16.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211);
     Fri, 27 Jan 2006 18:53:08 -0800
Received: from hotmail.com ([64.4.51.86]) by omc1-s34.bay6.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211);
     Fri, 27 Jan 2006 18:52:49 -0800
From: postmaster at mail.hotmail.com
To: krisrodgers at msn.com
Date: Fri, 27 Jan 2006 18:52:49 -0800
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
    boundary="9B095B5ADSN=_01C6157AD96B98B600009C02hotmail.com"
X-DSNContext: 7ce717b1 - 1196 - 00000002 - 00000000
Message-ID: <xefwTrQ2W00007b5a at hotmail.com>
Subject: Delivery Status Notification (Failure)
Return-Path: <>
X-OriginalArrivalTime: 28 Jan 2006 02:52:49.0300 (UTC)
FILETIME=[ECA61D40:01C623B5]

This is a MIME-formatted message.
Portions of this message may be unreadable without a MIME-capable mail
program.

--9B095B5ADSN=_01C6157AD96B98B600009C02hotmail.com
Content-Type: text/plain; charset=unicode-1-1-utf-7

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.


--9B095B5ADSN=_01C6157AD96B98B600009C02hotmail.com
Content-Type: message/delivery-status

Reporting-MTA: dns;hotmail.com
Received-From-MTA: dns;mail.hotmail.com
Arrival-Date: Fri, 27 Jan 2006 18:52:47 -0800

Final-Recipient:
Action: failed
Status: 5.2.1
Diagnostic-Code: smtp;550 5.2.1 Mail from 64.4.51.86 refused: spam site.

--9B095B5ADSN=_01C6157AD96B98B600009C02hotmail.com
Content-Type: message/rfc822

Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
     Fri, 27 Jan 2006 18:52:47 -0800
Message-ID: <BAY107-DAV14D4931813552E601FBF9BBC170 at phx.gbl>
Received: from 71.32.100.4 by BAY107-DAV14.phx.gbl with DAV;
    Sat, 28 Jan 2006 02:52:47 +0000
X-Originating-IP: [71.32.100.4]
X-Originating-Email: [krisrodgers at msn.com]
X-Sender: krisrodgers at msn.com
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Fri, 27 Jan 2006 19:52:44 -0700
Subject: Re: Tracing Email Problem
From: "K.A. Rodgers" <krisrodgers at msn.com>

Message-ID: <C0002A8C.43CB%krisrodgers at msn.com>
Thread-Topic: Tracing Email Problem
Thread-Index: AcYjmCCqoE4ZLczvR2utdIzEOkR+rgAHcjRn
In-Reply-To: 
Mime-version: 1.0
Content-type: multipart/related;
    boundary="B_3221236364_2019689"
X-OriginalArrivalTime: 28 Jan 2006 02:52:47.0800 (UTC)
FILETIME=[EBC13B80:01C623B5]

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3221236364_2019689
Content-type: multipart/alternative;
    boundary="B_3221236364_2026214"


--B_3221236364_2026214
Content-type: text/plain;
    charset="US-ASCII"
Content-transfer-encoding: 7bit


--B_3221236364_2026214
Content-type: text/html;
    charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: Tracing Email Problem</TITLE>
</HEAD>
<BODY background=3D"cid:3221236364_2014978">
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN
STYLE=3D'font-size:12.0px'>Hello=
,
<BR>
<BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"><B>From: </B>
<B>Date: </B>Fri, 27 Jan 2006 16:33:20 -0700<BR>
<B>To: </B>&lt;krisrodgers at msn.com&gt;<BR>
<B>Cc: 
<B>Conversation: </B>Tracing Email Problem<BR>
<B>Subject: </B>Tracing Email Problem<BR>
<BR>
</SPAN><FONT COLOR=3D"#008080"><FONT SIZE=3D"4"><SPAN
STYLE=3D'font-size:14.0px'>=
Kris Rodgers -<BR>
</SPAN></FONT></FONT><SPAN STYLE=3D'font-size:12.0px'> <BR>
</SPAN><FONT COLOR=3D"#008080"><FONT SIZE=3D"4"><SPAN
STYLE=3D'font-size:14.0px'>=

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cvnm.org/pipermail/helpdesk/attachments/20060129/52052989/attachment.htm


More information about the Helpdesk mailing list