Lists Home |
Date Index |
one of the things about these which confounds me, it that they appear to
always concern bounced messages which are weeks old.
Don Park wrote:
> This is just an example of what is wrong with the mailing list program. My
> ISP bounced two messages bounced in the recent past, two out of probably
> hundreds successfully sent before and after those bounces. My ISP was
> probably going through maintenance or something small crisis like most small
> ISPs do.
> Yet ezmlm is threatening to remove me from the list if a single probe it
> sends bounces. Chances are the probe will not bounce, but if it does, I am
> going to get unsubscribed 'without further notice'. More reasonable policy
> would be to monitor for a week and deal only with those that consistently
> bounce. It is unreasonable for ezmlm to expect 100% uptime from my ISP nor
> is its warning helpful at all since there is nothing I can do about it.
> Don Park
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]
> Sent: Saturday, March 15, 2003 1:27 PM
> To: firstname.lastname@example.org
> Subject: ezmlm warning
> Hi! This is the ezmlm program. I'm managing the
> email@example.com mailing list.
> I'm working for my owner, who can be reached
> at firstname.lastname@example.org.
> Messages to you from the xml-dev mailing list seem to
> have been bouncing. I've attached a copy of the first bounce
> message I received.
> Here are the message numbers:
> --- Enclosed is a copy of the bounce message I received.
> Reporting-MTA: dns; pyramid-02.kattare.com
> Arrival-Date: Mon, 3 Mar 2003 21:26:24 -0800
> Final-Recipient: RFC822; email@example.com
> Action: failed
> Status: 5.7.1
> Remote-MTA: DNS; mail.kattare.com
> Diagnostic-Code: SMTP; 550 5.7.1 <firstname.lastname@example.org>... Relaying denied
> Last-Attempt-Date: Mon, 3 Mar 2003 21:26:26 -0800
> Content-Type: text/rfc822-headers
> Return-Path: <email@example.com>
> Date: Mon, 03 Mar 2003 21:29:48 -0800