Hello,
it looks like this question has not been answered....and is not answered in
the Majordomo FAQ either.
Could anyone shed some light on this problem/issue?
Thanks,
Otis
>On Sun, 26 Apr 1998, Otis Gospodnetic wrote:
>
>> So in majordomo-owner's mailbox there will be various 'User unknown',
>> 'permanent error',' mailbox full, and other messages.
>>
>> So how do I handle them with a bounce script from a cron?
>
> This is something I'm extremely interested in. Before moving to
> majordomo, we were using some home-grown software to manage our
> mailing lists. We got a lot of bounceback messages.
>
> These bouncebacks fell into a number of categories:
>
> - auto-reply messages (such as "message opened" or "I'm on vacation")
> - transient delivery errors
> - undeliverable messages
> - unidentifiable errors (some mail servers send back so little
> information about the problem that you can't tell which list
> member's mail bounced!)
>
> We wrote a little program which would take a mail spool, split it
> into messages, and then parse each one to try to determine which list
> caused the bounceback, which user in that list bounced, and whether
> the user should be unsubscribed from the list. In the process, if
> the program felt it could extract all of this information from the
> mail message, it would delete the message from the spool file.
>
> This at least reduces the number of messages that have to be examined
> by hand. But I sure wish there were a cleaner, more foolproof method
> to use.
>
> For instance, is there any way to prevent mail clients from sending
> auto-reply messages? If we could eliminate all of those messages
> and only deal with the true bounces, that would probably only amount
> to three or four every day or two.
>
> Anyway, let me know if you're interested in seeing the perl script
> we used to auto-unsubscribe users and to trash the auto-reply messages.
>
>- --------------------------------------------------
>Jason Priebe WRAL OnLine
>priebe@wral-tv.com Raleigh, NC
|
|
