Travis Derouin wrote:
>
>Cool, what's the best way of doing this?
Your earlier, rapid response with the number of bouncing members and
their domains leads me to believe you got that info with
bin/list_members, so here's a withlist script to do it.
--cut here---
> >By disabling bounce processing, will this ignore the previous
> >disabling of addresses, since the recipients haven't received the
> >remaining 3 reminders (sounds like a tongue twister)?
>
>
> No. Once a member is disabled by bounce, the proces is taken over by
> the cron/disabled job which se
Travis Derouin wrote:
>
>I am the list owner, but there have been at least 2 non-list owner
>addresses that have also received this same message, when their
>addresses shouldn't have been disabled. Bounce processing was
>enabled, bounce_notify_owner_on_disable is yes.
So did you receive the own
Hi Mark,
Thanks for your reply!
On 2/18/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
> Travis Derouin wrote:
> >
> >I run a mailing list for a daily how-to newsletter for eHow.com.
> >Today, at least a few of us subscribed to the list, including myself,
> >received a false warning:
> >
> >"Your mem
Travis Derouin wrote:
>
>I run a mailing list for a daily how-to newsletter for eHow.com.
>Today, at least a few of us subscribed to the list, including myself,
>received a false warning:
>
>"Your membership in the mailing list eHow has been disabled due to
>excessive bounces The last bounce receiv
Hi,
I run a mailing list for a daily how-to newsletter for eHow.com.
Today, at least a few of us subscribed to the list, including myself,
received a false warning:
"Your membership in the mailing list eHow has been disabled due to
excessive bounces The last bounce received from you was dated
18-
