On Wed, Mar 17, 2004 at 03:19:34PM -0800, Jeremy T. Bouse wrote:
|
| Honestly after reading everything and having ran several mailing
| lists I would think the easiest solution is to simple have the mailing
| list software sign and archive the original confirmation email which
| could be presented as proof. Clean, simple and much less headache than
| trying to implement a scheme like this.
For the record, I want to follow this thought to its logical conclusion:
all mailing list subscriptions will now need to be password protected,
and you also have to archive every time a mailing list member changes
their subscribed email address.
Lazy unsubs are an interesting problem.
Right now we have conventions: we have majordomo-style
and listserv-style listname-request addresses or listname-unsubscribe
addresses, but the mailing list world lacks a consistent
machine-readable format for unsubscriptions.
My first stab at addressing the problem of lazy unsubs was to define a
modifier in the SPF record specifically for mailing list
unsubscriptions. If MLMs publish something like
"unsubscribe=%{listname}-unsubscribe(_at_)%{d}" then we can slide in another
layer of intelligence. When the user presses "this is junk mail" the
MUA can power up some state logic where the first click triggers an
unsub message to the address, and after 24 hours a subsequent click can
report an unsuccessful unsubscribe to a reputation service, etc.