Hi all,
I carefully read a thread from a few years ago about warming up IP
addresses using Postfix:
https://www.mail-archive.com/[email protected]/msg97100.html
One answer was to use a database lookup
(https://www.mail-archive.com/[email protected]/msg97102.html)
and another answer was to use smtpd_recipient_restrictions and randmap
(https://www.mail-archive.com/[email protected]/msg97107.html).
However, both answers *seem* to base the rate limiting on the
destination domain name, not the destination MX server. Since a
considerable amount of email goes to Microsoft and Google from custom
domain names, this shortcoming means the rate limiting will let a lot
more email go to Google and Microsoft than intended.
I tried to resolve the problem with my own TCP Tables based program that
is invoked via transport_maps. It handles MX lookups and responds with
":" or a fallback relay if the rate is exceeded for a given provider. It
works great!
But, I discovered that TCP Tables are consulted on the from address as
well as to address. And, they are consulted twice per recipient and they
are cached. All of those attributes make it impossible for my TCP Tables
program to accurately determine the rate for relaying to a provider.
Does anyone have other ideas?
jamie
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]