On Thu, Apr 22, 2004 at 10:40:33AM -0700, Mitch (WebCob) wrote:
>> -----Original Message-----
>> From: Dennis Schafroth [mailto:[EMAIL PROTECTED]
>>
>> So, instead of the
>>
>> "to [EMAIL PROTECTED] drop"
>>
>> rule, I use
>>
>> "to [EMAIL PROTECTED] delivery=|
>> /path/to/script/delete_pending_from_bouncemsg.sh >>
>> ~/.tmda/logs/delete_pending"
That's an interesting way to solve this problem. Of course, it requires
that the bounce provide sufficient information so that you can positively
determine the correct pending message to delete. If the bounce contains
sufficient information, you could simply grep for the confirmation address.
In my case, I'd grep for:
[EMAIL PROTECTED]
Here's an example confirmation address (that won't confirm anything):
[EMAIL PROTECTED]
All I have to do is extract 1082657194.16902 and then delete:
~/.tmda/pending/1082657194.16902.msg
That's a clever way to do it that I hadn't thought of. Previously, the
only way I thought to delete pending messages from a bounce was to tag
the envelope address for all confirmations. E.g. a confirmation would
look like this:
Return-Path: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Then any bounces would go to the envelope header, while actual confirmations
would go to the From or Reply-To address.
Personally, I still think using a specially tagged envelope address is a more
elegant solution, because it works for all cases. Delivering the bounce
address to a special script only works if the bounce contains sufficient
information to identify the correct pending email. Still it's a step.
Cheers,
- Mark
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
