On 4 January 2017 at 18:34, Wietse Venema wrote:
> Dominic Raferd:
>>
>> Thanks Wietse that sounds like a good plan, how would I set up a
>> 'special' smtp client for gmail servers with the reduced mx session
>> limit?
>
> /etc/postfix/main.cf:
> transport_maps = hash:/etc/postfix/transport
>
Dominic Raferd:
> > You can reduce the number of MX hosts to try to just 1, by setting
> > up an SMTP client for gmail etc. that has
> >
> > smtp -o smtp_mx_session_limit=1
> >
> > With that, Postfix still tries multiple MX hosts until one responds,
> > and you will have $min_backoff-time or mo
On 4 January 2017 at 16:52, Wietse Venema wrote:
> Dominic Raferd:
>> My idea is to force a delay (2 seconds say) between the initial
>> failure and the re-sending of the same email (same queue-id) to the
>> secondary mx (or fallback relay) - in the intervening time the message
>> may be pulled fr
Dominic Raferd:
> My idea is to force a delay (2 seconds say) between the initial
> failure and the re-sending of the same email (same queue-id) to the
> secondary mx (or fallback relay) - in the intervening time the message
> may be pulled from the queue. Following earlier advice from Wietse
> her
Is there a way to delay re-sending a message following an onward
rejection? I am getting occasional messages back from an onward server
(gmail) about a bad email; within a second we remove the bad email
from the queue and block the originator's ip. But sometimes the first
of these actions is too la
