Peter Blair wrote:
> On Mon, Feb 23, 2009 at 12:00 PM, Chris Dos <ch...@chrisdos.com> wrote:
>> I've been tasked to figure out a way for our three postfix relay servers to
>> intercept every hard bounced back
>> e-mail and process it for our web application.
>>
>> We have about nine servers relaying mail through our three postfix servers.
>> These servers send mail on behalf
>> of our clients. I'm trying to figure out a way to intercept a hard bounce
>> back from the destination server
>> and process it internally instead of bouncing back the error to our clients.
>> I've figured out a way to have a
>> copy of the bounce that would have gone to the postmaster account and have
>> that get processed, but it would
>> have still bounced it back to our client as well.
>
> I don't understand-- can't your email generators use an evelope "mail
> from" that tags that message to a particular mail campaign, that is
> unique, and not at all what the header "From:" header is?
>
> Ie: blahblahblah=customer=domain....@bounce.you.org
>
> As long as "blahblahblah" is a key to a recipient of a mail campaign
> owned by the account custo...@domain.com, then you can track your hard
> bounces this way. Just deliver to an application that parses the
> Return-Path (or whatever) and match it up against your db backend.
>
> Maybe I'm missing something, but this doesn't seem like a postfix
> question, but rather something for your company's application to
> address.
Well, the simple fact is that they want me to process the bounce backs and not
send the bounce back to the
user, but process it internally. Is there a way to do this without using VERP?
Chris
