It’s not a big truck. It’s a series of tubes. And if you don’t understand, those tubes can be filled and if they are filled, when you put your message in, it gets in line and it’s going to be delayed.
Sending email is a major part of our business. Over the years, TheLadders has moved through several iterations of getting emails out to our millions of job seekers and recruiters. We’ve both built in-house solutions and utilized Email Service Providers (ESPs).
Recently, we transitioned onto a new ESP, SendGrid. SendGrid offers us the choice of handing off email via their HTTP or SMTP APIs. We selected SMTP as our transport mechanism because it allows us the luxury of inserting a layer in our infrastructure to handle queueing and resilience of mail transport before handing messages across to the ESP. We are also able to achieve higher overall throughput with SMTP than would be possible with the HTTP API. We’re using Postfix as our mail transport agent because of its scalability properties, the flexibility of its configuration options and our team’s familiarity with running and maintaining the application.
To ensure that our subscribers receive the emails we send them, we divide the different types of messages across multiple sub-user accounts at SendGrid. This spreads our outbound email across different source IPs depending on the chosen sub-user account and allows us to control the reputation of each IP group. In addition to the usual challenges that go along with deploying any new infrastructure — monitor it, scale it, make it highly available — SendGrid’s use of SMTP authentication credentials to determine which sub-user account will handle the sending of a particular message created a new and interesting problem to solve. How could we allow our application to instruct Postfix which sub-user account to use without building a Postfix cluster for each sub-user account? Moreover, how could we make that process invisible to our end recipient?
Don’t Clog the Tubes!
The majority of our email traffic is created by various Storm topologies crunching through our data. Storm provides the ability to parallelize each step in the process, resulting in fairly rapid generation of email traffic. We utilize our F5 load balancers in front of a pool of Postfix servers to make our mail transport layer both fault-tolerant and scalable. During our larger sends, we prefer messages to be sent out with minimal queueing. We’ve found after tuning that we can sustain roughly 7000 messages per second through a single Postfix server before messages begin to queue. We can easily scale out to additional Postfix servers behind the load balancer to increase our total throughput.
Pick a Tube
Postfix provides the SASL Password Map mechanism to look up SMTP credentials based on remote hostname or domain. When coupled with Sender-dependent Authentication, that lookup can be performed based on the sender address. We leveraged this combination of options along with plus-sign subaddressing to encode the sub-user account in the message’s source address, so an email from
firstname.lastname@example.org would actually be sent from
We utilize a regular expression map for the password selection that matches the subaddress portion of the sender address and returns the appropriate sub-user account credentials to postfix, with a default for messages that come through without a subaddress.
1 2 3
Keep Your Tubes Straight
While our solution works great for allowing our applications to properly route messages to the correct sub-user account, it doesn’t necessarily provide the best customer facing appearance. Our customers don’t care what ESP we use, how we perform our sub-user account selection, or which sub-user account sourced their email. Furthermore, a sudden change in source email address could cause our messages to be filtered incorrectly on the recipient side. Perhaps a customer has a filter in place to always drop our messages into a specific folder for them to read later. Maybe they have a strict policy stating that only mail from known addresses will end up in their inbox. We periodically have to adjust how our outbound email is processed and we have to make those changes as transparent as possible for our customers. To that end, we are also utilizing Postfix’s address rewriting capabilities to ensure that our email source addresses remain consistent.
Postfix provides several opportunities and methods to transform email envelope information for a variety of purposes. Our requirement was to transform messages sent from
email@example.com so that the customer sees the message sourced from
firstname.lastname@example.org. Sender canonical maps initially seemed like the ideal solution to this problem. It worked perfectly to transform the sender address as desired however, the transformation occurred so early in the process that addresses were being rewritten before the subaccount selection was performed. We finally settled on SMTP generic maps as the correct solution since it performs its transformation when mail leaves the machine via SMTP, after all other processing has taken place. We again use a regular expression to strip the subaccount information from source addresses.
Pipes or Tubes
Pulling it all together with the recommended Postfix config from SendGrid, results in
1 2 3 4 5 6 7
Find this post interesting? Join the discussion over on Hacker News.