> > I looked for domains that *are not* using the outlook: transport but > > are using the outlook.com relay servers. There are 383 such domains > > -- the vast majority are one email address per domain. These domains > > are competing for the limited number of outlook.com connections and > > they are not being controlled by the outlook: transport process limit > > in master.cf. Adding 383 domains to outlook: in transport.regexp > > seems a bit extreme and would be impossible to maintain. How can we > > control the number of connections made on behalf of this set of > > domains to the outlook.com relay servers? > > With automated logfile analysis, such domains could be added to a > transport map. Once a map is populated there will be a trickle of > updates.
I created transport.outlook.regexp which contains the 383 domains mentioned above. I also added the following in main.cf: transport_maps = regexp:/etc/postfix/transport.regexp, regexp:/etc/postfix/transport.outlook.regexp Only one domain was *not* using the outlook: transport last night (now added to transport.outlook.regexp). The overnight runs were much better as a result of this and limiting our email arrival rate to 500 per minute. We received the following messages with the outlook: transport limited to 4 processes in master.cf: MaxConnections: 54, Connection: 30 Not perfect but much better and no rate limiting. What is the relationship between the number of processes for outlook: transport in master.cf and the number of simultaneous connections that can be made to the outlook.com servers? I changed master.cf to 3 processes for outlook: in hopes of reducing MaxConnections feedback -- I can not go much smaller. Thanks, Greg www.RayStedman.org
