X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 30 [X] Return-Path: Received: from [68.202.132.19] (account marv@lancaironline.net) by logan.com (CommuniGate Pro WEBUSER 5.1.7) with HTTP id 1907847 for lml@lancaironline.net; Wed, 07 Mar 2007 16:57:41 -0500 From: marv@lancair.net Subject: Warning messages and forced un-subscribes To: X-Mailer: CommuniGate Pro WebUser v5.1.7 Date: Wed, 07 Mar 2007 16:57:41 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/html;charset="iso-8859-1" Content-Transfer-Encoding: 8bit
Hi all,

We've been experiencing a large number of automatic subscription removals, especially among folks with AOL.com email addresses.  Best I can surmise, they appear to be a result of some of the unusally large digests which have been going out recently.  It seems that AOL's email filters see overly large posts as spam and as a result reject those posts.  The LML listserver software is notified of these "bounces" and assumes the email address in question to be inoperative and removes the subscription from the rolls.  The process isn't inevitable, however, as subscribers whose LML emails are bouncing are sent "warning" messages regarding the problem.  While I'm focused on AOL subcsriptions at the moment, any subscriber may be sent these warning messages and I thought it prudent to go over the process of dealing with them.  I have a "canned" response I send to folks inquiring about them and thought I'd share it with everyone so you'd be a bit better informed should one of them suddenly show up in your email box.

"""
These warning messages are generated by the LML listserver anytime an LML message is bounced back to it. They are used to detect inactive email addresses... after 5 of these warnings go unanswered the email address in question is unceremoniously removed from the subscription rolls, ostensibly because the email address is no longer valid. The bounces may be caused by delays in your ISP's mail server, by an outage in a router somewhere between here and there, or just a clog in the internet backbone somewhere along the way. The only time they are the fault of the recipient is if his email server is volume limited and the the subscriber fails to empty his email box on a regular basis. Regardless of the reason, dealing with these warnings is an extremely simple matter... whenever you get one, just reply to it. You don't need to write anything into the message, you don't need to modify the address or any of the headers, just hit the reply button and send off whatever it is that shows up in your reply editor... all the listserver is looking for is the reference number contained in the subject box of the headers. After you've sent the reply on its way, simply delete the original message and go on about your business. With most email programs, taking the necessary steps to address one of these warnings typically takes no more than a few seconds... reply, send, delete. That's it. Failure to reply to at least one in five of these messages will result in your LML subscription being removed.

If the reply, send, delete option is too much to ask, then your only other option is to remove your normal subscription, switch to the null mode and do your reading of the LML on the website archives. The null mode stops all deliveries of LML emails to your mailbox but retains your email address as a valid one for posting purposes. The decision is up to you. The one thing I can't do is make the warnings stop as long as you're a regular subscriber. They happen, it's just a fact of life. Sorry about that.

"""

I trust this clears up any misconceptions you may have about these warning, and helps our AOL subscribers out there keep their subscriptions intact and uninterrupted.  I hope you found this information useful, as it's intended to keep your LML experience a happy one.  Thanks for your time.

  <Marv>