On 07/13/09 20:57, Tim German wrote:
I like the idea
of pointing the alias to a wrapper. I am going to give that a try.
*nod*
I like the wrapper option because I can leave
normal bounce processing in tact for all other mailing lists.
That's another good point. Not modifying Mailman its se
Thanks for the reply and thanks for pointing me to the correct DSN
files. I am going to give Grant's suggestion of using a small wrapper
a try first. I really only want this functionality for one list, so I
think the wrapper will be a good fit. If the wrapper doesn't work
out, I will pla
Thanks for the reply! No, I am not using mm-handler. I like the idea
of pointing the alias to a wrapper. I am going to give that a try.
Regarding the wisdom of doing this, I understand the concern. This
will be used for a private announce-only list with a captive
audience. All members
Tim German wrote:
>Is it possible to exclude a certain DSN status code from bounce
>processing? I would like for all 5.2.2 (mailbox full) bounces to be
>ignored. I do not want them counted as soft or hard bounces. I just
>want them ignored with no change to the members bounce score. I am
On 07/08/09 14:20, Tim German wrote:
Is it possible to exclude a certain DSN status code from bounce
processing? I would like for all 5.2.2 (mailbox full) bounces to be
ignored. I do not want them counted as soft or hard bounces. I just
want them ignored with no change to the members bounce
Is it possible to exclude a certain DSN status code from bounce
processing? I would like for all 5.2.2 (mailbox full) bounces to be
ignored. I do not want them counted as soft or hard bounces. I just
want them ignored with no change to the members bounce score. I am
currently running v2
