On Sat, Aug 25, 2018 at 7:06 PM, Wietse Venema <wie...@porcupine.org> wrote: > Rodrigo Severo - F?brica: >> Hi, >> >> >> Trying to deal with a destination server that is really picky about >> the speed I deliver messages to it. >> >> In a setting like transport_destination_concurrency_limit what does >> destination means exactly? > > That depends on the destination_recipient_limit setting, as documented > under > > default_destination_concurrency_limit (default: 20) > > The default maximal number of parallel deliveries to the same > destination. This is the default limit for delivery via the > lmtp(8), pipe(8), smtp(8) and virtual(8) delivery agents. With > per-destination recipient limit > 1, a destination is a domain, > otherwise it is a recipient. > > For example, local delivery has a per-destination recipient limit > of 1, and the concurrency limit prevents one recipient from using > up all local delivery processes. > > Other delivery agents have a per-destination recipient limit of 50 > or so, and there, the concurrency limit prevents one domain from > using up all SMTP delivery processes.
First of all, thanks for your prompt answer. I've read this info. I understand that for other deliver agents, with a per-destination limit greater than one, the limit is per domain. My doubt is: in this case, "per domain" refers to "per email address destination domain" or "per destination server domain (as indicated by MX records)"? Or saying it with another words: if 2 different email address destination domain points to the same servers in their MX records, will the limit be "per email address destination domain" or "per destination server domain"? Regards, Rodrigo Severo
