listserv handles most bounces directly. addresses are removed when either
a time or volume threshold has been passed. this sort of approach is vital
if you have busy lists. i believe it also distinguishes between transient
and permanent failures (as dsn encodes them). after you do this you have
to deal with broken mailers that return bounces to the From: line and
annoying mailers that don't use dsn format (or really annoying mailers like
sendmail 8.6 that use mime but don't do dsn or x400 gateways that return
random looking junk that isn't worth trying to parse).
despite my profound annoyance at the way aol works at least their bounce
format can be trivially converted to dsn (so why don't they do it?).
another approach is to simply discard all bounces and periodically probe or
confirm addresses.
btw, bounces remain useful for people who want to prune lists but don't want
to or can't do probes or reconfirmations.
>>>>> "Mike" == Mike Nolan <nolan@celery.tssi.com> writes:
Mike> Mentioning my traffic level raises a question, so to return to
Mike> the general subject of mailing list management, what do other
Mike> list managers running high volume lists do about bounces?
--
paul
pjg@acsu.Buffalo.EDU |public keys at:
| http://urth.acsu.Buffalo.EDU/~pjg/key.html
if the above contains opinions they are mine unless marked otherwise.
Follow-Ups:
References:
|
|
