Simple Mail Transfer Protocol (in short, SMTP) is the standard set of rules by which emails are sent, received and relayed over the internet.
All well-known email clients, such Gmail, Yahoo and Outlook, use SMTP to send your message to a mail server. This server then uses SMTP to relay that message to the correct recipient server.
Adding SMTP records
By enabling SMTP on your transactional email service provider, the information below will be automatically generated:
Server (SMTP host)
In the example, you’ll see what this looks like in transactional email service MailerSend.
In the left sidebar in Ycode, you will be required to enter the information above into the email configuration settings. Additionally, you need to provide the type of encryption. This type is always TLS encryption.
Once you’ve added all the information, you’ll be able to set up transaction emails such as password reminders and collect responses from a contact form.
SMTP vs. API
The key difference between SMTP and API is that the SMTP uses multiple back-and-forths between the client and server to communicate. API, on the other hand, receives HTTP requests directly from your app and the email sending is triggered directly from there.
If you don’t have any help from an integration tool like Zapier, you’ll need some coding knowledge to set up API email sending. With SMTP, you don’t need any prior knowledge to send emails.
If you’re a casual email sender, SMTP will probably suit your needs best. App developers and email marketers that often send emails in bulk will benefit more from using email API.