-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 9, 2009, at 12:10 PM, Fil wrote:
When a user reaches the threshold for bouncing, does the e-mail
address
get removed from all lists on the server or just the list for which
they
were bouncing?
It is on a list-per-list basis. Hopefully M
> When a user reaches the threshold for bouncing, does the e-mail address
> get removed from all lists on the server or just the list for which they
> were bouncing?
It is on a list-per-list basis. Hopefully MM3 will be able to offer a
choice with its database backend, but with the file-based MM2
When a user reaches the threshold for bouncing, does the e-mail address
get removed from all lists on the server or just the list for which they
were bouncing?
Jeff
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org
[EMAIL PROTECTED] writes:
> Q1Why are they called 'uncaught' ... ?
This is pretty standard jargon. There are low level routines, each of
which traps the errors it expects. Some trap mice, some trap bears,
some trap bacteria.
Every once in a while, something unimaginable like the Loch Ness
[EMAIL PROTECTED] wrote:
>
>Q1Why are they called 'uncaught' since they have clearly been sent to a
>Mailman address, and then neatly packaged up by Mailman and sent to me as list
>and/or site admin? Are they really just 'unrecognizable' possible bounces (as
>it says in the body of the Mailm
Hi
I've just upgraded to Mailman 2.1.9 from a much earlier installation.
One of the new features that puzzles me is the 'uncaught bounce notification'.
I get these for out-of-office responses and for auto-replies.
The auto-replies come from some artificial mailbox address.
The out-of-office re
Please, anyone knows how doing this?
I'm using the mailman software and I have a question.
When the bounce emails are generated I receive them in my email account but I
would need to have another type of management of those emails. For example, one
inform of those emails or statistics of them
