>>>>> "TD" == Todd Day <today @
TD> If someone subscribes from a machine like apple.fruit.com but their
TD> simple email address is user @
com, often their From: address will
TD> be user @
com and the automated packages will sign them up at
TD> that address. [...] When they go to unsubscribe, perhaps they are
TD> using orange.fruit.com that day.
In addition to the "fuzzy" match that majordomo can use (which needs to be
worked on, and is on my list) it also sends exact instructions for removing
yourself even when your address changes. Unfortunately it does this when
you subscribe, and subscribers are often too clueless to save the message.
(Yes, it does say "save this message". If only I could make it blink.)
TD> What recourse for the user? Grab the user list, figure out which
TD> address they got subscribed as, and try again.
Majordomo has the "which" command that will will do a substring search on
all of the subscriber lists. (Yes, you can limit the number of hits, at
least in the version that just went beta.) While the probability of this
matching does go down with the size of the list, it does work rather well
and doesn't require pulling down the whole subscriber list.
Do other list servers not do this? (It's a real question; I've always used
Majordomo). If there's something else that can be done I'd be interested
in hearing about it.
TD> [...] Now I have to deal with tracking down these unsubscribe (and
TD> address change) cases myself.
I say "Ug. Send Received: headers, you get off list. Ug." and go back to
business. It usually doesn't take any time at all to track things down
based on that.
Jason L. Tibbitts III - tibbs @
edu - 713/743-8684 - 221SR1
System Manager: University of Houston High Performance Computing Center
1994 PC800 "Kuroneko" DoD# 1723