Deliverability
Remember relay races in school? Just as runners pass along a baton, an SMTP relay passes along an email from one server to another. Sinch Mailgun’s free SMTP relay service helps you win the race for both transactional email and email marketing campaign delivery.
Looking to increase email delivery rates? Read on to see if SMTP relay is the answer.
Even though it may seem that emails are sent and received instantaneously, email communication actually involves a number of steps. Components – including the client, server, and mail agents – all have to work together for the system to run smoothly.
SMTP stands for “Simple Mail Transfer Protocol”. It’s all about outgoing email. Well-known email clients such as Gmail, Outlook, Yahoo, and Apple Mail all rely on this protocol to move messages from an email client to an SMTP server. This server then ferries emails to a receiving email server before the message reaches its final recipient.
By setting the rules between servers and computer networks, SMTP plays an important role in this ubiquitous communication channel. When you send an email, the email client (such as Gmail) “talks with” the SMTP server of your email provider. The SMTP server then pushes the email to the recipient’s SMTP server, allowing their email client to retrieve it from there.
While SMTP and SMTP relay are obviously closely related, it’s important to understand the difference between them. SMTP is the protocol for transferring outbound mail while SMTP relay is the process of transferring outgoing mail. SMTP relay may also be referred to as an email relay or a mail relay.
An SMTP relay is required if the recipient’s SMTP server is on a different domain, which is signified by the portion of an email address that comes after the @ symbol. For example, an email sent from one Gmail.com address to another Gmail address happens on the same domain name while an email sent from a Gmail address to a Yahoo address must cross over to a different domain.
By using SMTP relay, you can transmit emails between SMTP servers hosted on different domains without modifying the messages in any way. All headings, formatting, and content stays intact during the transfer. SMTP servers also use SSL or TLS security protocols to encrypt email communication to ensure security during the emails’ journey.
An email communication system that uses clients, servers, protocols, and relays operates like the virtual post office of the internet.
Think about the traditional, physical postal service – or if you want to make it more fun, the old school pony express. When you want to send mail to a friend, you place a letter in an envelope, and put the envelope in a box. A postal worker then picks up that letter and brings it to a central location. A truck or plane (or a horse) then delivers the letter from your central location to your friend’s central location, where a local postal worker picks up the letter and brings it to your friend’s mailbox.
When you want to send an email to your friend instead, your email is placed in a virtual envelope and sent to an SMTP server on your domain, which is like your central location. If your friend’s domain or central location is different, SMTP relay operates like the plane or truck in the snail mail example, transporting your email between SMTP servers on different domains.
Learn more about SMTP and how SMPT ports help direct and manage message delivery in our post on which SMTP port to choose and why.
The two main types of SMTP relay services are open relay and closed relay.
An open relay is also known as a public SMTP relay. It’s a mail server that allows anyone on the internet to use it. In the early days of email, open relays were more common and relays were often set to “open” by default.
Today, however, open relays are considered a security risk, and most organizations see open relays as improperly configured SMTP servers. Since no authorization is required on open relays, spammers, bad actors, phishing scammers, and malware distributors can easily conduct their cyberattacks.
You can test your SMTP relay server using a few different methods. All of them are fairly simple and can confirm whether or not your system is configured properly and if it’s secure.
The first general way to test your SMTP relay is to simply send an email, watch its journey, and confirm that it’s properly delivered. Here are the steps:
Many free tools are available online that offer functionality to test your SMTP server or relay. We offer a great one that’s built to help you scale.
Here are a few other options:
If you prefer to conduct a manual test from the command prompt, you can make a ping request to the IP address of the SMTP server you want to test. If the SMTP server responds, you know it passes the test. If the ping request does not respond, it’s possible that the SMTP fails the test. However, some servers block ping requests, so you may want to telnet the SMTP server to confirm.
Finally, if you want to conduct an open relay test, telnet to the server and use commands to send a test email to another domain. A 250 response code with no request for authentication indicates an open SMTP relay.
In most cases, organizations will want to close the SMTP relay for security purposes. Contact the administrator of your email system, whether that be an internal IT professional or a third-party provider, and request that the email server is reconfigured to allow only authorized IPs and domains to send emails. Additional authentication and security protocols are often used with SMTP and SMTP relay services.
While both options strive to keep email delivery rates high, the key difference between SMTP and API is in their approach. As we’ve discussed, SMTP is the set of communication rules that allow you to send an email across servers. In some cases, you can also use an email API, which is a window used to communicate code between different applications or platforms. Making the choice for your organization will depend on your resources and needs.
Although using an email API can speed up the process, decrease potential failures, and boost security, it does require development skills and resources to manage frequent updates and modifications.
SMTP, on the other hand, is more broadly used and doesn’t require any coding. However, it can require significant server communication and tasks such as mail merging can be complicated and time-consuming.
In general, an API is a good choice if you have resources and want the ability to do a great deal of customizations, automations, and tracking for your email campaigns. It also offers improved performance if you send a large volume of promotional emails. On the other hand, if you’re looking for a simple solution that’s a universal standard, SMTP fits the bill. Since SMTP is platform-independent, it can also seamlessly connect to popular solutions like CRM platforms and migrate easier for future growth and scalability.
If you don’t have the internal IT resources to manage SMTP relay, you may want to consider SMTP relay services. A third-party provider can help you significantly reduce your technical overhead when it comes to SMTP relay tasks, which frees your team up for mission-critical work.
When you use a third-party SMTP relay provider, an SMTP relay carries your outgoing email messages to an SMTP relay server that’s managed by an email service provider (ESP). At this point, the SMTP delivers email messages to the recipients’ mailbox providers.
So when exactly should you opt for an SMTP relay service?
If you’re ready to improve the way your email is sent, it’s time to consider Mailgun’s free SMTP relay service. Our cloud-based SMTP relay service provides:
At Sinch Mailgun we try hard to provide the tools and knowledge sources you need to be a great sender with strong deliverability. But topics like SMTP prove how complex that actually is. Sometimes it helps to have some smart email geeks guide your way. Check out our Free SMTP relay service and reach out to our team to help you navigate the email realm.
