[majority removed]
> It is highly discouraged that you will ever manually edit a file in
> $prefix/templates/$lang, and Mailman's install target will have every
> right to overwrite them on an upgrade. That's what the templates/site
> subdirectory is for; upgrading will never touch site-centric,
admin(11159): [- Mailman Version: 2.0.1 -]
admin(11159): [- Traceback --]
admin(11159): Traceback (most recent call last):
admin(11159): File "/home/mailman/scripts/driver", line 96, in run_main
admin(11159): main()
admin(11159): File "/home/mailman/Mailman/Cgi/handle_opts
> > "AMK" == Ashley M Kirchner <[EMAIL PROTECTED]> writes:
>
> AMK> I have three domains sitting on one machine and mailman
> AMK> installed for each one (meaning, three copies of mailman).
> AMK> Each vhost has it's own web address, and crontask. And I can
> AMK> have th
> Depends on how 'virtual' your setup is, and I suspect, it
> also depends on the MTA.
A single instance of sendmail (8.5.5) deals with all my virtual domains...
and hands off to the lists as defined by /etc/aliases (after the incoming
mail has been mashed into the resulting list name)
> I have
Has anyone been able to completely virtualize the mailing lists under
mailman v2?
I'm not talking about the improvements made in v2 I mean having
multiple domains be able to have the SAME list name. Unless I've missed
something, right now they're limited to being unique per machine. I know
Two questions:
1. Whats the difference between a "first" and a "first fresh" in the bounce
log?
2. And how do I clear the bounce stats for a list??
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listin
Ok - I dont know how widely useful this might be - but it would have saved
my bacon today.
I had a list get flooded by an upstream mail server that was stuck on
sending a message to me. Every message that came in had the same messageID
on it - and mailman dutifully kept pushing them out 200+
