Kevin Rector wrote:
I've checked the documentation and it seems like this is the best plan
but I'd thought I'd get y'alls input.
Hmm. Sounds about like:
If we hold our mouth right, and we hop up and down while
spinning in a triangle-wise manner, and throat-sing
"Hava Nagila" while drinking ten gallons of the worst rot-gut
Tequila, we think this will work. But we wanted to check
with you.
I wouldn't recommend either procedure for any particular purpose, and if
you're on a University campus and you're trying to get someone else to do
something like this then you might get arrested for "hazing".
For what you want to achieve, why not just set up a separate mailing lists
with all the same subscribers (except the intended victim), closed archives,
and a different listowner password?
There's still a number of different ways that things could leak out of that
idea, but at least it's got a few smaller holes than depending on the victim
not reading the archives, no one else responding to the message after his
delivery is turned back on, etc....
--
Brad Knowles <[EMAIL PROTECTED]>
LinkedIn Profile: <http://tinyurl.com/y8kpxu>
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
