Mixmax with gmail
S: 250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTHĬ: AUTH XOAUTH2 dXNlcj1lbmd0gDN0dXNlcjFAbWl4bWFmNvbQFhdXRoPUJlYXJlciAvliBzZWNyZXQgs8BAQ= The SMTP protocol requires at least ten back-and-forth request-responses to send an email.
#Mixmax with gmail code
Invalid login: 454 4.7.0 Cannot authenticate due to temporary system problemīy comparison, the Gmail API has well-documented error codes that leverage HTTP’s error code structure. Message failed: 451 4.3.0 Mail server temporarily rejected messageĭata command failed: 421 4.3.0 Temporary System Problem Here’s a sample of some of the codes we’ve received: The SMTP error codes could represent anything from a Gmail server issue to the user being rate-limited because they’re sending too much email. Gmail’s SMTP sent us a plethora of ambiguous error codes. Then, Gmail API correctly authenticates and DKIM signs the email.
![mixmax with gmail mixmax with gmail](https://www.mixmax.com/hubfs/Mixmax_May2021/Images/https___www.mixmax.com_assets_sequences.gif)
The Gmail API, on the other hand, allows us to simply set the “From” field to our preferred Google account address. In SMTP, setting the “From” email header to the alias address does nothing more than spoof the sender and direct the email to a nearly certain death by spam filter. Gmail’s SMTP server has no way to use this feature. Sending from AliasesĪs anyone with multiple email addresses can attest, Gmail’s popular alias feature simplifies things by offering a way to send emails from multiple addresses while logged into a single Google account. Benefits of the Gmail APIĪs a higher-level abstraction on top of SMTP, the Gmail API offers several key benefits. Since we couldn’t wait for Google, we began our project to move our email-sending infrastructure to the Gmail API. We needed to act quickly to restore our users’ trust. After circulating this finding within the email community, we learned that Google’s spam classifier had indeed shipped a bug that caused it to unfairly target SMTP-sent emails. The same emails sent using the Gmail API, which we had previously only experimented with, did not show the same higher likelihood. We discovered that emails sent using SMTP-our exclusive method of email delivery at the time-had a higher likelihood of being labeled as spam. We first set up a controlled test environment to isolate possible causes of our emails being sent to spam.
![mixmax with gmail mixmax with gmail](https://d33v4339jhl8k0.cloudfront.net/docs/assets/5727c291c69791092313013f/images/5fda6f8c27288b7f895d62d4/file-BT3zvd656q.png)
Because email deliverability is our number one job, we immediately launched an investigation. MotivationĮarlier this year, we heard reports from our customers that some of their Mixmax emails were going to their recipient’s spam folders. In contrast to SMTP (and its email-fetching cousin IMAP), the Gmail API was recognized as being simpler to integrate with, allowing for more granular access to data using OAuth, and also offering a performance boost.
![mixmax with gmail mixmax with gmail](https://images.wired.it/wp-content/uploads/2015/01/1421659799_mimax-calendar-cover.jpg)
Even today, whether you use Gmail, Outlook, or AOL, they all transfer email externally using the SMTP protocol.įast forward to 2014, when Gmail introduced a REST API as a proprietary layer on top of their email infrastructure. SMTP, or simple mail transfer protocol, was first introduced in 1981 and became the internet standard for sending email. Overviewįirst, let’s discuss a bit of history.
![mixmax with gmail mixmax with gmail](https://www.mixmax.com/hubfs/Mixmax_May2021/Images/https___www.mixmax.com_assets_rules.gif)
In this post, we’ll share about our motivation to migrate and how we overcame challenges presented by the differences between Google’s two methods of email delivery. We recently rolled out a substantial improvement to our email-sending infrastructure by migrating from Google’s SMTP server to Google’s Gmail API.