Declare FROM: to be an alias. Declare REPLY-TP: to be the actual
email account you want replys to go to. This From: alias receives
bounces and feeds them to a program that harvests the To: field and
appends it into a file. Set a cron job to run 6 days after sending
out the newsletter. This cronjob reads that file and does something
intresting with the file; email it to the postmaster, perform 4,096
repetitions of the Tibetain prayer for the dead for each, delete each
from the subscriber file, email it to the Moscow HQ for the KGB,
In total confusion,
Kirk D Bailey
| Providing Excellent email service for free!! |
| Webmaster, Howlermonkey Email services Co. |
| firstname.lastname@example.org www.howlermonkey.net/ |
>-------- ORIGINAL MESSAGE BELOW --------
>I suppose you could build a script to perform expn or account validity checks as well, and run that once in a while.
>Start a dummy message to an end user, and either capture the failure (no such user) or somesuch.
>From: Frank Bax [mailto:email@example.com]
>Sent: Friday, January 11, 2002 2:34 PM
>To: Mohler, Jeff
>Cc: Helpdesk; firstname.lastname@example.org
>Subject: RE: create a report of undeliverable mails
>Sorry, momentarily forgot the golden rule: "Given enough time and money
>programmers can build any system".
>Now, let's be realistic. I have a mailing list with almost 5,000 email
>addresses on it. It takes a couple of hours for the lowly P2-233 to get
>our monthly message out. After that it takes up to 5 days for all the
>bounce messages to come back. Many messages have been forwarded before
>they are bounced, and the 'bounced' reply give no indication of the
>original email address. So, if its acceptable to wait 5 days for a
>partially complete report, I suppose it could be built.
>Actually, I was thinking the person was looking for such a report WITHOUT
>actually doing a mailing to the list.
>If you must first send out a mailing to get the information, and then
>intercept the bounced messages, I suspect that it would be a better
>approach to simply remove the offending email addresses, rather than simply
>report them. I suspect scripts already exist with this in mind.
>At 02:14 PM 1/11/02 -0800, Mohler, Jeff wrote:
>>Cant do what??
>>Sounds like a simple procmail filter to redirect them all, and some form
>>of an intelligent grep to strip out the parts of the new spool you
>>actually need..and then Email that to yourself as a list of funky Email
>>addresses off your list(s).
>>From: Frank Bax [mailto:email@example.com]
>>Sent: Friday, January 11, 2002 2:03 PM
>>Subject: Re: create a report of undeliverable mails
>>At 03:39 PM 1/11/02 +0100, Helpdesk firstname.lastname@example.org wrote:
>>>How can I have a report of all undeliverable e-mail addresses?
>>You cannot. Wouldn't life be so much simpler with such a report?
>>Majordomo simply takes a message and sends it back out with many recipients
>>(slight over-simplification). Then your mail delivery program
>>(sendmail,etc) takes over. Majordomo does not find out undeliverable
00001&type=1&subid=0">uBid</a><IMG border=0 width=1 height=1