On Mon, 3 Dec 2001, David W. Tamkin wrote:
Irwin's question, if I understood it right, could be phrased as, "How do I stop SmartList from automatically removing users, since the bounces are not from their addresses?"
This is a problem with SmartList's bounce handling depending on mail servers to use standard bounce message syntax and unfortunately they don't.
Microsoft's Internet Exchange causes this problem alot. I'll try the following example, it has been awhile since I had this problem as I hacked qmail/verps into my SmartList configuration. Hopefully nothing has changed with IE server's bounce message.
Here is a bounce message that comes back:
"Your message
To: somelist@lists.cuenet.com Subject: Monthly Announce Announcement Sent: Mon, 3 Dec 2001 15:27:30 -0500
did not reach the following recipient(s):
somebody@someISP.com on Mon, 3 Dec 2001 15:28:17 -0500 The recipient name is not recognized The MTS-ID of the original message is: c=WW;a=CONCERT;p=CONCERT;l=ATAEXCONN010112032028VR6N06QZ MSEXCH:IMS:Exchange:CRTATL:ATAEXCONN01 0 (000C05A6) Unknown Recipient"
SmartList can't determine that somebody@someISP.com is the recipient whose email is bouncing. So SmartList trying to be 'smart', looks for the 'next best' address which it finds in the 'From: " address of the attached copy of the email that bounced as follows:
------_=_NextPart_000_01C17C39.0D1D918A Content-Type: message/rfc822
Message-ID: Pine.LNX.4.21.0112031226120.29639-100000@orbital.cuenet.com From: Cueman cueman@cuenet.com To: somelist@lists.cuenet.com Subject: Monthly Announce Date: Mon, 3 Dec 2001 15:27:30 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-MS-Embedded-Report: Content-Type: text/plain; charset="iso-8859-1"
[body of message snipped]
There are no doubt by now many other examples of this stuff. So the solution is to:
1. Have a special bounce recipe for every possible bounce message out there.
2. See if Sendmail has addressed the issue of some sort of verp system with their professional product and massage that into the scheme of SmartList.
3. Build a new SmartList that has some sort of verp system so that SmartList isn't depended on the cooperation of rouge mail server companies.
I still have the occasional embarrassment of SmartList accidentally unsubscribing the listadministrator. That's a tough one to explain to ordinary folks without CS degrees that are used to things that work.
Cheers,
Cueman