I'm looking for some good advice for the following type of situation:
1. A subscriber sets a mail-forward from his current address at ISP 1
to a new address at ISP 2.
2. The subscriber's account at ISP 2 is closed, and address 2
produces error messages to the list manager. No clue to address 1
can be easily identified, but ISP 1 can be identified from the
headers or contents of the error message.
3. When asked for help identifying the username and address, there
is absolutely no response from postmaster at ISP 1, and ISP 1 is a
big ISP that also offers domain names, so it's impossible to
identify the subscriber address without their help.
I'm just having one of these cases with [EMAIL PROTECTED] I
get an automated response that my message have been received and
will be attended to, and then nothing. 4-5 days after my original
request, I mailed them the following letter:
---begin-letter
Date: Wed, 14 Apr 1999 18:52:16 +0200
From: Thomas Gramstad <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Notification of forwarded error messages.
I have received no answer to my request, copyed below. Meanwhile,
I continue to receive error messages. Since it is your (now
defunct) user that is causing these error messages, it is your
responsibility to help stop these error messages by providing
the information that I asked for. I will not spend any more time
writing more requests to you. Instead, I will simply forward all
error messages I receive to you, until I get the infomation I need
to stop them. This message, therefore, is a notification to you
that you will receive such error messages, until that time.
Thomas Gramstad
[EMAIL PROTECTED]
---------------
Date: Sat, 10 Apr 1999 01:55:07 +0200
From: Thomas Gramstad <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Request for address information
Message-ID: <[EMAIL PROTECTED]>
Hello,
I need to know which iname address is forwarding to the address
[EMAIL PROTECTED], so that I can remove the iname address from my
mailing list. The address [EMAIL PROTECTED] no longer works and
generates error messages.
Regards,
Thomas Gramstad
[EMAIL PROTECTED]
---------------
Return-Path: <>
Received: from rmx07.globecomm.net (rmx07.iname.net [165.251.8.75])
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id BAA09468
for <[EMAIL PROTECTED]>; Sat, 10 Apr 1999 01:47:41 +0200 (MET DST)
Received: from localhost by rmx07.globecomm.net (8.9.1/8.8.0) with internal id
TAA16150
Date: Fri, 9 Apr 1999 19:47:11 -0400 (EDT)
From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: multipart/report; report-type�livery-status;
boundary="TAA16150.923701631/rmx07.globecomm.net"
Subject: Returned mail: User unknown
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--TAA16150.923701631/rmx07.globecomm.net
The original message was received at Fri, 9 Apr 1999 19:47:09 -0400 (EDT)
from lmtp08.iname.net [165.251.8.81]
**
This is an automatic message to inform you that your email was not
forwarded through iName's server.
The iName email address that you tried to send mail to may not be active.
Reasons for the failed delivery attempt could include:
1. The iName customer has selected a new personalized iName email address
rendering their old iName email address inactive.
2. The iName customer may have signed up for one of iName's free offers
and then not validated their forwarding address.
3 The address may simply be typed incorrectly. Please check that you
typed the email address correctly.
iName provides email users with a permanent, personalized and secure email
address that is independent of how one accesses the Internet. iName acts
as a global forwarding service. All email sent to a permanent iName address
is automatically forwarded to a user specified destination email address.
Please visit iName's Online Support Area at
http://www.iname.com/info/intro/index.html for further information.
**
----- The following addresses had permanent fatal errors -----
<[EMAIL PROTECTED]>
----- Transcript of session follows -----
... while talking to online.no.:
>>> RCPT To:<[EMAIL PROTECTED]>
<<< 550 <[EMAIL PROTECTED]>... User unknown
550 <[EMAIL PROTECTED]>... User unknown
--TAA16150.923701631/rmx07.globecomm.net
Content-Type: message/delivery-status
Reporting-MTA: dns; rmx07.globecomm.net
Received-From-MTA: DNS; lmtp08.iname.net
Arrival-Date: Fri, 9 Apr 1999 19:47:09 -0400 (EDT)
Final-Recipient: RFC822; [EMAIL PROTECTED]
Action: failed
Status: 5.1.1
Remote-MTA: DNS; online.no
Diagnostic-Code: SMTP; 550 <[EMAIL PROTECTED]>... User unknown
Last-Attempt-Date: Fri, 9 Apr 1999 19:47:10 -0400 (EDT)
--TAA16150.923701631/rmx07.globecomm.net
Content-Type: text/rfc822-headers
Received: from smv19.iname.net by rmx07.globecomm.net (8.9.1/8.8.0) with SMTP id
TAA16143 ; Fri, 9 Apr 1999 19:47:09 -0400 (EDT)
Received: from ifi.uio.no (IDENT:[EMAIL PROTECTED] [129.240.64.2])
by smv19.iname.net (8.9.1a/8.9.1SMV) with ESMTP id TAA21895;
Fri, 9 Apr 1999 19:47:04 -0400 (EDT)
Received: (from mdomo@localhost)
by ifi.uio.no (8.8.8/8.8.7/ifi0.2) id BAA08929;
Sat, 10 Apr 1999 01:43:05 +0200 (MET DST)
Date: Sat, 10 Apr 1999 00:41:19 +0200 (MET DST)
From: "Geir J. Netland" <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Star Wars i 60 minutes
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by ifi.uio.no id BAA08923
Sender: [EMAIL PROTECTED]
Precedence: bulk
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smv19.iname.net id TAA21895
--TAA16150.923701631/rmx07.globecomm.net--
---end-letter
As far as I'm concerned, iname.com is guilty of spamming if they
don't do anything with such cases (and I'm sure they are common).
At the very least I think that this behavior, or non-behavior as
the case may be, qualifies for blacklisting.
But is there anything I can do with this situation?
And it is getting better, I've just got another case just like
this one on one of my other lists, and that one is iname.com too.
Thomas Gramstad
[EMAIL PROTECTED]
