you may need to increase the main.cf ... destination_concurrency_limit from 20

I am seeing the following in the postfix logs, and we are having a delivery problem to blarg.com. However the destination_concurrency_limit reported at 20 took my by surprise. I was under the impression we had already set it higher. Feb 11 12:36:08 email postfix/qmgr[23132]: warning: mail for

-o syslog_name=XYZ only shows first deferrals with that syslog_name? Retries appear to defer without the custom syslog_name.

We override the syslog_name in the master.cf so that we can run pflogsumm on the resulting log files (split out by rsyslog) and we began noticing discrepancies. Typical line in master.cf smtp104_120_110_27 unix - - n - 150 smtp -o smtp_bind_address=104.120.110.27 -o syslog_name=postfix-app1 -o

Re: Using negative feedback to control sites returning too many connects warnings.

: default_destination_concurrency_negative_feedback = 3/1 On Tue, Aug 16, 2011 at 8:50 AM, Donovan Bray donno...@gmail.com wrote: How about using initial concurrency, negative and positive feedback so that dynamically it loses concurrency faster on failure than it gains on success? I've seen no examples of how

With soft_bounce set to no, we are seeing a lot of send failures that look like they should be permanent 554's being handled as temporary.

Jul 19 19:25:35 myserver postfix/error[14000]: D075AA21004: to= z...@comcast.net, relay=none, delay=0.36, delays=0.36/0/0/0, dsn=4.0.0, status=deferred (delivery temporarily suspended: host mx2.comcast.net[76.96.30.116] refused to talk to me: 554imta33.emeryville.ca.mail.comcast.net comcast