Dear Tim Mapes,
It's not SMTP attack. It's attempt to use open HTTP proxy for spam
message relaying. You can try 3scan
http://www.security.nnov.ru/soft/
to test if it's possible to relay message via given HTTP proxy and
you'll get approximately same records in your logs.
--Friday, April 1, 2005, 7:46:57 PM, you wrote to
NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM:
TM> Has anyone seen this showing up in there SMTP server logs?
TM> Tim Mapes
TM> Fri 2005-04-01 04:55:55: Accepting SMTP connection from [217.128.81.65 :
TM> 3775]
TM> Fri 2005-04-01 04:55:55: Looking up PTR record for 217.128.81.65
TM> (65.81.128.217.IN-ADDR.ARPA)
TM> Fri 2005-04-01 04:55:55: D=65.81.128.217.IN-ADDR.ARPA TTL=(1439)
TM> PTR=[areims-105-2-1-65.w217-128.abo.wanadoo.fr]
TM> Fri 2005-04-01 04:55:55: Gathering A-records for PTR hosts
TM> Fri 2005-04-01 04:55:55: D=areims-105-2-1-65.w217-128.abo.wanadoo.fr
TM> TTL=(1440) A=[217.128.81.65]
TM> Fri 2005-04-01 04:55:55: --> 220 combine.com ESMTP MDaemon 7.2.3; Fri, 01
TM> Apr 2005 04:55:55 -0500
TM> Fri 2005-04-01 04:55:55: <-- POST / HTTP/1.0
TM> Fri 2005-04-01 04:55:55: --> 500 What? I don't understand that.
TM> Fri 2005-04-01 04:55:55: <-- Host: combine.com:25
--
~/ZARAZA
You know my name - look up my number (Beatles)
--
NTBugtraq Editor's Note:
Most viruses these days use spoofed email addresses. As such, using an
Anti-Virus product which automatically notifies the perceived sender of a
message it believes is infected may well cause more harm than good. Someone who
did not actually send you a virus may receive the notification and scramble
their support staff to find an infection which never existed in the first
place. Suggest such notifications be disabled by whomever is responsible for
your AV, or at least that the idea is considered.
--
