Changes between Version 2 and Version 3 of relay-server-by-domain


Ignore:
Timestamp:
Jun 4, 2014, 3:38:09 PM (11 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • relay-server-by-domain

    v2 v3  
    11= Relay Server By Domain =
    22
    3 One of our [wiki:email-deliverability email deliverability] strategies is to relay mail through different IP addresses based on the domain name of the recipient. This strategy is based on our understanding that many big email providers allow or block sending IP addresses based on the ratio of valid email addresses to bad email addresses (among other criteria). By concentrating all email messages sent by our various bulk email servers (mostly leslie, assata - which provides bulk.mayfirst.org, and morales - which provides Portside) we can earn a good reputation based on sending thousands of legit emails per day.
     3One of our [wiki:email-deliverability email deliverability] strategies is to relay bulk email through different IP addresses based on the domain name of the recipient. In other words, all bulk messages sent by our members (this does ''not'' include private/individual messages - only messages sent to email lists) are sent to a different server depending on their destination (all email for Yahoo goes to one server, AOL mail goes to another, etc.). This strategy is based on our understanding that many big email providers allow or block sending IP addresses based on the ratio of valid email addresses to bad email addresses (among other criteria). By concentrating all email messages sent by our various bulk email servers (mostly leslie, assata - which provides bulk.mayfirst.org, and morales - which provides Portside) we can earn a good reputation based on sending thousands of legit emails per day.
    44
    55This strategy allows us to:
    6  * build a better reputation for any given email provider by combining all sent messages so they originate from one IP address
     6 * build a better reputation for any given email provider by combining all sent messages from all MF/PL servers so they originate from one, or a few, IP address
    77 * provide flexibility so we can easily redirect messages being blocked on one server to be redirect to a different relay server
     8 * permanently or temporarily rate-limit sending messages to certain providers, without affecting other providers
     9 * take special action on messages just before being relayed (see, for example, [wiki:dmarc-and-mailing-lists our technique to avoid strict DMARC rules]). By maintaining servers that ''only'' relay email out, we can safely apply rules that will not affect incoming messages.
    810
    911== How to make a change ==
    … …  
    2325
    2426{{{
    25 0 rustin:/etc/postfix-b# ls -d /etc/postfix*
    26 /etc/postfix  /etc/postfix-a  /etc/postfix-b
    27 0 rustin:/etc/postfix-b#
     270 rustin:# ls -d /etc/postfix*
     28/etc/postfix-yahoo-a  /etc/postfix-aol-a  /etc/postfix-therest-a
     290 rustin:#
    2830}}}
    2931
    30 /etc/postfix is the base instance, and a and b are ones available for use. These are configured via dns as a.rustin.mayfirst.org and b.rustin.mayfirst.org.
     32/etc/postfix is the base instance.
    3133
    3234== Adding more instances ==