Jamie McClelland via Postfix-users:
> 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.
Indeed, the Postfix scheduler is driven by destination domain
and it does not look up MX records. That was nt a proboem
when the scheudler was designed and implemented.
There is a workaround (solution?) that uses check_recipient_mx_access
and content filter support:
/etc/postfix/main.cf:
smtpd_something_restrictions =
...
check_recipient_access lmdb:/etc/postfix/mx-filter
...
/etc/postfix/mx-filter:
outlook.com filter outlook-smtp:
google.com filter google-smtp:
...
/etc/postfix/master.cf:
outlook-smtp ...same fields as generic 'smtp' client...
google-smtp ...same fields as generic 'smtp' client...
...
A simpler solution does not exist at this time. This requires adding
mx-filter and master.cf entries for every email hosting service.
Wietse
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
