North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: ** Forged spamming going on

  • From: William Allen Simpson
  • Date: Wed Dec 23 10:05:41 1998

There has been rather a lot of blather in the meantime, but the original
message was pretty important.  To go back to that, I dug up a posting
from the responsible party at ATT from the IETF list.  If [email protected]
is not working, then we (and he) should know about it!

Did you try abuse, Alex?  Did they identify the culprit?

Has been added to the RBL for relaying faked spam?

> From: [email protected]
> Date: Sun, 20 Dec 1998 16:53:26 -0500 (EST)
> Received: from ( [])
>         by (8.8.8/8.8.7) with SMTP id XAA23473;
>         Sat, 19 Dec 1998 23:27:18 -0500 (EST)
>         (envelope-from [email protected])
> AT&T's security dept is non-existent, as far as I am concerned.

< From: "Jonathan Clark" <[email protected]>
< Date: Thu, 5 Mar 1998 00:46:23 -0500
< Subject: Re: Last Call: Anti-Spam Requirements on an SMTP MTA to BCP
< ...
<                             And as far as I am aware AT&T Worldnet has not
< been accused with any evidence of spamming the Internet. Plenty of our users
< have been, and when we identify them, we take appropriate action.
< For over a year now I have had requests out on various anti-spam lists,
< and I make the same offer in this forum, that if anyone receives mail with
< forged headers which appear to implicate AT&T Worldnet for them to please
< send it to me, or to our abuse desk. To date I have received exactly two
< examples. So I don't know whose headers are being forged, but I have no
< evidence that it's ours.
< Also please note that it is a violation of AT&T Worldnet's AUP to use a
< mailbox on our service as a response address for a spam, even if the mailing
< did not originate with us.
< Sascha (or anyone else), if you feel you have a genuine complaint, please
< feel free to contact me directly. However, routine abuse matters should
< go directly to [email protected], since all I'll do is send them there anyway.
[email protected]
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32