|
Identifying the original user that sent the email
is another great advantage of Declude Junkmail. We add a customer header
to the message so we can track it. Doesn't work for lists, unfortunately,
due to IMail's handling of the list explosion, but does at least identify to
which list the original message went sent. For all others, we check the
header and contact the users to let them know not to report messages we forward
for them as spam in AOL. After three warnings in a relatively time
period we remove their forwarding, forcing them to pick up mail directly
from our servers instead.
Darin. ----- Original Message -----
From: Ted Galerneau
Sent: Tuesday, November 30, 2004 7:37 AM
Subject: RE: [IMail Forum] AOL The feedback loop
mentioned is for sure and it�s a really good thing to do with AOL. It will keep
you off their blocked list and let you know when there are problems. The one bad
thing is that they only show what address on your email server it came from but
not the address it was going to. We�ve had issues where a user has email
forwarded to their AOL email account from their email account on our email
server. Then some spammer sends a spam to their account on our machine and
forwards to their AOL account, then they mark it as spam and AOL send us a
message as if it came from us. Another issue is some of our clients that email
several AOL clients about legitimate issues, and one reports it as junk mail,
these things can be a pain to manually trace out when they omit what AOL address
it�s going to and being reported from. In any case it�s way
better than ending up on their blocked list like we did at one time. If you get
there it will take considerable time and effort to be removed
again! From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jim
Bruner 1) Our Vice President started
getting these about a week ago. As many as 6 a day. So she asked me what was
going on. I told her there was a spammer using her email address in the from
field and there was nothing i could do about that other that block the AOL
bounce messages. Am i correct here in saying that? Here is the
bounce... ****** 67.114.195.162 is not
on my network nor is it my user****** ****** It appears to me that this
user above 67.x.x.x is performing a dictionary attack on AOL with my users email
address as the sender****** The original message was received at
Mon, 29 Nov 2004 12:37:47 -0500 (EST) from
adsl-67-114-195-162.dsl.pltn13.pacbell.net
[67.114.195.162] *** ATTENTION
*** Your e-mail is being returned to you
because there was a problem with its delivery. The address which was
undeliverable is listed in the section labeled: "----- The following
addresses had permanent fatal errors -----". The
reason your mail is being returned to you is listed in the
section labeled: "----- Transcript of
Session Follows -----". The
line beginning with "<<<" describes the specific reason your e-mail
could not be delivered. The next line contains a second error message which is a
general translation for other e-mail servers. Please direct further questions
regarding this message to your e-mail
administrator. --AOL
Postmaster ----- The following addresses had
permanent fatal errors ----- <[EMAIL PROTECTED]> ----- Transcript of session follows
----- ... while talking to air-xk02.mail.aol.com.: >>> RCPT
To:<[EMAIL PROTECTED]> <<< 550 MAILBOX NOT
FOUND 550
<[EMAIL PROTECTED]>... User unknown 2) Then she replies back to me
saying that she contacted AOL second level support.... this is what they told
her... They said we potentially have a port open and/or a
worm/Trojan that is allowing this. They said we should run a full virus scan on
every computer in the network to make sure they are clean.
They also
said you can go to postmaster.aol.com and set up a feedback loop so you will be
notified anytime anyone from our network sends something into aol that they
consider spam. They said it will create a whitelist that will let you track the
sender as well as being notified of how often this is
happening. Can someone confirm that my
explanation to her is valid? TIA Jim W.
Bruner Network
Admin. |
