Chris Dos wrote:
Noel Jones wrote:
Chris Dos 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.
A check_sender_access map that returns REDIRECT should do the trick.
<> REDIRECT someu...@localhost
careful here - this may intercept stuff you don't intend. You might
combine this with a check_recipient_access under smtpd_restriction_classes.
-- Noel Jones
Well, we have hundreds of thousands of different e-mail addresses being used.
We are trying to analyze every
bad bounce back to keep a handle on our clients to make sure they are not
sending UBE or any other kind of
mail they are not supposed to. Analyzing the bounce backs is one method we use
to track the clients.
Chris
Another option is to use the HOLD action to freeze them in the
queue. You can them examine them with postcat and then either
delete them or release them for delivery to the original
recipient with the postsuper command. This could be automated.
This gives the option of delivering the mail to its intended
recipient.
-- Noel Jones
