> There are a couple types of bounces, the ones I unsubscribe are the ones
> that come back 'user unknown'. There are others, that say 'connection timed
> out' or 'connection deferred' that seem to indicate a temporary glitch in
> the net. This is basically the system saying to you, "The line's busy now,
> but I'm going to call back later."
>
> Why do we need to see these bounces, they make up a good 85-90% of the
> bounce messages I get, and they're meaningless to me. Unless the mail is
> permenantly not delivered, I don't really care how many times the machine
> tries to send it. And regardless of how many of these addresses you clear
> out, there's always going to be new ones from some part of the net that's
> acting up each time a post is made.
The NOTARY standards (soon to appear as RFCs) provide:
+ a standard format for all delivery status messages that can be
parsed and interpreted,
+ standardized and reasonably precise error codes,
+ a way to specify that you don't want to see "delay" messages
Of course, it will take awhile before these are universally deployed,
but the latest sendmail already implements them.
Also, I manage to automatically filter out most of the delay messages
with MH, using the following lines in my .maildelivery file:
Subject "mail warning" destroy ? /dev/null
Subject "Mail Item Format Warning" destroy ? /dev/null
Subject "Waiting Mail" destroy ? /dev/null
Subject "WARNING: message delayed at" destroy ? /dev/null
Subject "Warning From uucp" destroy ? /dev/null
Subject "Returned mail: warning: cannot send message for " destroy ? /dev/null
Subject "Undeliverable RFC822 mail: temporarily unable to deliver" destroy ? /dev/null
Subject "Warning: could not send message for past " destroy ? /dev/null
Subject "Mail not delivered yet, still trying" destroy ? /dev/null
Keith
|
|
