Recently we posted a admin message to a metar list at our site (we combine
the lists so that only one message is received by a subscriber even if
that person subscribed to several lists). Surprisingly, I received the
following message that thought it was a spam message. If you read below,
it tells that since listserv does not fill the To: field with the actual
recipient's address, it got the spam masters attention. How can we fix
this problem in listserv config? I want the e-mail id of the individual to
show up in To: address line rather than
To: Multiple Recipients of list xxx
Any help appreciated..
K.V. Rao
---------- Forwarded message ----------
Date: Sun, 21 Mar 1999 23:34:55 -0800 (PST)
From: [log in to unmask]
Subject: Spam Detection Auto Reply Gateway
(Message delivery cost sponsored by http://serverhosting.net)
This message is generated by the Spam Detection Auto Reply Gateway
in response to the email supposed to be sent by you as
From: <[log in to unmask]>
Subject: Update on India Network - Administrivia
Reply-To: [log in to unmask]
ApparentlyTo:
To: [log in to unmask] (extended list suppressed)
Message-ID: [log in to unmask]
This Gateway kicked in for one of the following reasons:
1. you "spammed" with an unsolicited commercial email (UCE); or
2. you mailed to a list that contains an email address
that does not belong to a real person (you were given
perhaps given a wrong address); or
3. you Bcc'ed the correct recipient or a mailing list the
recipient belongs to. Unfortunately, in order to contain
the menace of UCE, several email recipients now have
filters that reject email unless their email address, or
a mailing list they subscribe to, appears in the To:
or Cc: fields. If that is the case, you may resend your
original message to the following recipient by their
explicit email addresses. Our statistics suggest that
over 96% of UCE gets rejected with this policy.
4. you just have a wrong email address for someone, that
makes it an honest mistake but doesn't exonerate you
from the responsibility to not use it again.
Our Gateway heuristics suggests the email address that may have
triggered this was:
<[log in to unmask]>
If you are operating a commercial list, please remove
this from it now!! If this was intended as a personal
email, please accept our apology and resend it to the
above address directly.
Additionally, your email claimed to be addressed to the
potentially forged email address(es) quoted below. If
you are a spammer, you would know that it is a very
common practice among spammers to use a "To: " header
that has nothing to do with who the message is actually
delivered to. Sort of like writing a fictitious address
on an envelope but dropping it in someone else's mailbox.
Since you may have intentionally abused or otherwise misused our
mailing system, we are adding _your_ email address to a mailing
list of suspected spammers. We reserve the right to sell it to
anyone for legal commercial advertising purposes. We do not
otherwise send unsolicited email.
Due to the volume of the spam this Spam Detection Auto Reply
Gateway receives, and to avoid mail loops caused by auto replies,
all replies to this message are sent into a blackhole.
-=-=- Always check email addresses and save everyone the trouble
and cost of dealing with unwanted email. -=-=-
>From [log in to unmask] Sun Mar 21 23:34:54 1999
> by indnet.org (8.9.3/8.9.3) with ESMTP id CAA25412;
> Mon, 22 Mar 1999 02:36:41 -0500 (EST)
> spool id 514256 for [log in to unmask]; Mon, 22 Mar 1999 00:00:11 -0500
> (8.9.3/8.9.3) with ESMTP id NAA09194 for <[log in to unmask]>; Sun, 21
> Mar 1999 13:42:37 -0500 (EST)
>Date: Sun, 21 Mar 1999 13:42:36 -0500 (EST)
>From: "K.V. Rao" <[log in to unmask]>
>To: [log in to unmask]
>Subject: Update on India Network - Administrivia
>Message-ID: <[log in to unmask]>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Sender: [log in to unmask]
|
