> I really don't want to kick people off my lists just because of a transient
> net problem,
Here's how ezmlm handles bounces.
If messages to you start bouncing, ezmlm waits ten days; then it sends
you a list of message numbers you missed and a copy of the first bounce.
If that warning bounces, ezmlm waits ten days; then it sends you a probe
with a copy of the bounce.
If the probe bounces, ezmlm silently kicks you off the list.
Results in sample situations:
(1) Your account is removed. Messages bounce. Ten days later, ezmlm
sends a warning, which bounces. Ten days later, ezmlm sends a
probe, which bounces. ezmlm removes you from the list.
(2) You briefly run over quota. Your MTA foolishly bounces a few
messages. Ten days later, ezmlm sends its warning, including the
list of missed message numbers. You retrieve the missing messages
from the archive.
(3) You forward copies of incoming mail to a summer account. At the
end of the summer, the account is removed. Messages bounce,
though you don't realize it. Ten days later, ezmlm sends a
warning, which bounces, but you've been alerted to the problem.
You fix the problem. Ten days later, ezmlm sends a probe, which
doesn't bounce.
Warnings and probes are sent from cryptographically secure addresses, so
an attacker can't force you off the list unless he can watch your mail.
All of this depends on qmail's VERPs, which reliably identify the
subscription address and message number for every bounce message.
To join the ezmlm mailing list, send an empty message to
djb-ezmlm-subscribe@koobera.math.uic.edu
The first release will be RSN.
---Dan
Put an end to unauthorized mail relaying. http://pobox.com/~djb/qmail.html
Follow-Ups:
|
|
