John Clark:
> I've been tasked with catching several bounce-back conditions (no longer
> subscriber, connection refused, host not found, email address invalid, etc)
> and adding the offending email address from our email server's messaging
> list to prevent poisoning our mailserver's IP per several
On Tue, Jul 05, 2011 at 01:52:45PM -0500, John Clark wrote:
> I agree. However my main question is what is the best way of capturing these
> bounces and and running an SQL insert to opt out the address. Is there a way
> to append a command to be run upon a message being removed from the queue
> vi
I agree. However my main question is what is the best way of capturing these
bounces and and running an SQL insert to opt out the address. Is there a way
to append a command to be run upon a message being removed from the queue
via maximal_queue_lifetime?
On Tue, Jul 5, 2011 at 1:46 PM, Victor Duc
On Tue, Jul 05, 2011 at 01:42:09PM -0500, John Clark wrote:
> Messages in my deferral queue are set to be removed after 5 days and I have
> been instructed to catch the above stated conditions after 3 days to
> auto-opt-out.
Just set the maximal_queue_lifetime to 3 days. If you're opting users ou
I've been tasked with catching several bounce-back conditions (no longer
subscriber, connection refused, host not found, email address invalid, etc)
and adding the offending email address from our email server's messaging
list to prevent poisoning our mailserver's IP per several ISPs rules.
Messag
