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

[Skip Montanaro]

    Chris> Does mailman already have the ability to trace such fraudulent
    Chris> subscribe requests and such?

    me> http://www.spamcop.net/

    Chris> How does this help you, as an end user, figure out how you were
    Chris> subscribed to a mailing list?

It doesn't.  I thought that the expectation was that the Mailman
administrator would be doing the legwork.  It seems that getting Mailman to
save subscribe messages in a log file would be a reasonable extension to
help address the problem.

    Chris> And besides, it uses that ORBS garbage.  :)

There's a smiley, but I still should ask, what does ORBS do and why is it
bad?  (Off-list, plz.  I'm sure most of the rest of mailman-users isn't
interesting in novice tutoring...)

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

Right where I thought the work would be getting done...

Skip Montanaro | http://www.mojam.com/
skip at mojam.com | http://www.musi-cal.com/
847-971-7098   | Python: Programming the way Guido indented...