Changes between Version 20 and Version 21 of email-deliverability


Ignore:
Timestamp:
Apr 21, 2014, 12:47:10 PM (6 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • email-deliverability

    v20 v21  
    11= Email Deliverability Strategies =
    22
    3 This week we have been hit hard by email deliverability problems. I think it's time to make some signficant changes to our email strategies. The goals of these changes are:
     3The goals of these changes are:
    44
    55 * Prioritize sending of individual email over sending of bulk email
     
    4343== Provide tools for release mailq back log ==
    4444
    45 See latest proposal: [wiki:bulk-mail-relay bulk mail relay].
     45See current process: [wiki:bulk-mail-relay bulk mail relay].
    4646
    47 Although this runs the risk of getting more IP addresses blocked, it would nonetheless be useful if we had easy method for swapping out IP addresses easily to relieve a big mailq backlog. That could happen either by having multiple IP addresses assigned to each bulk mail server that could be swapped around with a command line tool and/or by temporarily relaying mail to a server in another cabinet (e.g. chun or femi or fela).
     47Thanks to taggart for the idea.  We have multiple relay servers and have our bulk mail servers use round robin DNS to randomly pick the relay servers. See: #6662.
    4848
    49 '''You can now rotate ip addresses on leslie and assata with the command mf-swap-smtp-bind-address.'''
    50 
    51 Another idea suggested by taggart is to setup multiple relay servers and have our bulk mail servers use round robin DNS to randomly pick the relay servers. We could also setup a "graveyard" mx - which is the relay server that should be sent all deliveries that were deferred on first attempt. That way we keep the queues empty for well-responding destination servers and shunt the problem ones aside. Using transport mapping, we can also send email destined to a particular domain name to a particular server that is not having trouble relaying the mail. See: #6662.
    52 
    53 And a yet another idea is to use [http://ngocquyetlinux.blogspot.com/2013/05/postfix-rate-limit-to-domain.html] to rate limit messages based on criteria (like yahoo messages can only be sent x number at a time).
     49We are also rate-limiting outgoing messages when it seems to help.
    5450
    5551== open deliverability tickets ==