Re: Adjusting custom transport for comcast.net's throttle

> On May 2, 2016, at 10:40 PM, Noel Jones wrote: > > On 5/2/2016 8:42 PM, Steven Peterson wrote: >> Thank you! This was very helpful. >> >> By setting minimal_backoff_time to 300s globally, postfix now >> attempts to send deferred messages to comcast.net >> every 10 minut

Re: Adjusting custom transport for comcast.net's throttle

On 5/2/2016 8:42 PM, Steven Peterson wrote: > Thank you! This was very helpful. > > By setting minimal_backoff_time to 300s globally, postfix now > attempts to send deferred messages to comcast.net > every 10 minutes. This is an improvement, but > it is not obvious why it s

Re: Adjusting custom transport for comcast.net's throttle

Thank you! This was very helpful. By setting minimal_backoff_time to 300s globally, postfix now attempts to send deferred messages to comcast.net every 10 minutes. This is an improvement, but it is not obvious why it sends every 10 minutes (600s) and not every 5 minutes (300 seconds). Is there

Re: Adjusting custom transport for comcast.net's throttle

> On May 2, 2016, at 5:38 PM, Steven Peterson wrote: > > It is almost as if the minimal_backoff_time that was defined in the custom > transport is not overriding the default setting in main.cf. Not "almost", but "exactly". The "minimal_backoff_time" parameter is a qmgr(8) setting and has no

Adjusting custom transport for comcast.net's throttle

Dear Postfix Experts: I am having difficulties delivering newsletters to comcast.net email addresses and ask for some advice. I have set aside a special transport for the IP (using sender_transport) as it is new without an established reputation. When a queue run is begun, comcast.net will allow