Hi, On Mon, Dec 17, 2018 at 12:18 PM Viktor Dukhovni <postfix-us...@dukhovni.org> wrote: > > On Mon, Dec 17, 2018 at 10:47:02AM -0500, Alex wrote: > > > The original reason I had set it in the first place was to try and control > > the amount of email the bulk senders like constantcontact, mailchimp, etc, > > could send at once, filling our queues with thousands of messages at once. > > This does not appear to be that parameter :-) > > Inbound email should not generally result in queue congestion, it > is typically delivered to mailboxes faster than it arrives from > the remote system. Are you accepting email for non-existent > recipients and sending bounces? Best to not do that...
No, we're not doing that. We have check_recipient_access maps that contain a list of all valid users. The problem is that this is a domain with thousands of recipients, and mailchimp and others send mass newsletters to thousands of those recipients at once to our relyhosts, which first scan the emails for spam/viruses and only then forward on. This causes somewhat of a significant delay at times as the server processes all the emails. I recall reading that more recently people are configuring their mail systems to scan the email as it's received without queuing it, and I assume reject temporarily any mail that can't be processed at the time it's received? Thanks, Alex
