On Wed, Jan 16, 2013 at 4:35 PM, Wietse Venema <wie...@porcupine.org> wrote:
> You can twiddle with smtp_mx_mumble_limit, but why bother sending > from mailer1, when the mail is accepted only from mailer2? > I think mailer1 got blocked initially by AOL because my aol_destination_concurrency_limit, aol_destination_recipient_limit, and aol_destination_rate_delay were probably set too aggressively when we initiated the send last night. I've since cranked them down on mailer1 to match the settings of mailer2, but AOL hasn't reacted yet. We're still twiddling with those settings, too. :) Our PHP script we use to send the mail is currently only configured to run from mailer1, and is running right now, and we don't want to have to interrupt it to move a copy over to mailer2 and write something that keeps track of which mailer sent the newsletter to which recipients. Any way to use the transport maps on mailer1 to tell Postfix to use mailer2 for aol.com addresses? Then I could just change that setting, do a postfix reload, and let mailer1 "cool off" in AOL's eyes. Thx, SteveJ
