[Mailman-Users] Fwd: Subscription bomb tracing - feature request.

[Christopher Lindsey]

>     Chris> Does mailman already have the ability to trace such fraudulent
>     Chris> subscribe requests and such?
> 
> My uneducated guess would be "no".  Educated or not, mailman is probably not 
> the place for such esoterica.  Try SpamCop instead:
> 
>     http://www.spamcop.net/

How does this help you, as an end user, figure out how you were subscribed 
to a mailing list?  You would only get messages from the list or confirmation
requests which would originate at the mailman server.  And besides, it 
uses that ORBS garbage.  :)

What I've done is wrap my mailman -request and -admin aliases with a
procmail script that saves all incoming messages with full headers.  It
doesn't help the end user, but as an administrator I have an archive
showing where requests originated in case someone contacts me later with
problems. 

So far I've only had to use it once.

Of course, Web-based subscription requests can be checked via your HTTP
server's logs.

Chris