Wietse Venema:
> David Michard:
> > Hello,
> >
> > I know this question has been discussed on this list* but no suitable
> > solution was provided for our SMTP server settings.
> > A patch** is published but reports on this list say that it does not work.
> >
> > I am responsible for a medium sized mailing-list, through which one
> > email is sent per day to roughly 600 000 subscribers. Since our
> > mailing list is growing, we are having more and more problems with
> > very conservative SMTP servers enforcing a low number of simultaneous
> > connections from a single IP address. Our subscribers wish to receive
> > their email as soon as possible so delaying the email for a few hours
> > is not an option.
>
> You need to cut deals with ISPs and other sites that you have lots
> of customers at. Using a "spread spectrum" approach is just a trick
> to fly under the radar, and that works only with low-volume mail.
>
> > Is it possible to tell postfix to randomly select an IP address, and
> > associated hostname (as many smtp servers perform RDNS lookups and
> > compare it to the HELO/EHLO greeting) when sending an email ?
> > That would be very helpful.
>
> You would use a regexp-based transport map that matches the first
> character(s) of the recipient email address, and that routes mail
> to a Postfix mail delivery agent that has its own smtp_bind_address
> etc. setting in the master.cf file. However, the concurrencies for
> each delivery agent are scheduled independently, as if you are
> running multiple Postfix instances.
s/agent/transport/
The scheduler manages concurrencies by transport and by destination
name. Thus, the total concurrency limit for a specific destination
is the sum of the concurrency limits of all transports that deliver
to that specific destination.
Wietse
