1. What is an SMTP server?

SMTP are the acronyms of Simple Mail Transfer Protocol. Basically, it is the protocol used to send emails over the Internet. Think of it as the “digital postman” that collects your emails and delivers them to the destination mailbox.

When your App sends emails (such as notifications, passwords, newsletters, etc.), it needs an SMTP server to manage and distribute those messages.

2. Advantages of using your own SMTP server

1. Greater credibility and trust
   When using your own email, recipients will see an email that matches the customer's domain (for example, notifications@yourdomain.com) instead of a generic address. This projects a professional and trustworthy image.

2. Better delivery rate (deliverability)
   Setting up SMTP with a verified and well-configured domain helps prevent emails from falling into the spam folder as easily, because email providers (Gmail, Outlook, etc.) recognize that the email comes from a legitimate source.

3. Full control over email settings
   Each customer can choose the sending frequency, email limits, security and authentication policies, and other aspects that can improve the performance and security of their communication.

4. Customizing the Reply Address
   By having your own SMTP, it is also possible to configure a response address (Reply-To) that redirects incoming emails to a specific mailbox, facilitating interaction with App users.
   
   

3. How to configure your own SMTP

4. How to fill out the SMTP configuration fields

Example: If we were configuring SMTP for the Scoreapps App, the fields would be completed as follows:

• Here you choose the type of encryption or security protocol to send the emails.
• SSL and TLS They protect communication between your server and the destination server, preventing others from reading or modifying emails in transit.
• If nothing is configured (or “insecure” is chosen), the traffic is not encrypted, which is not recommended in most cases.

• The port determines where the mail data travels. The most common are:
  • 587 (with TLS)
  • 465 (with SSL)
  • 25 (without encryption or with STARTTLS encryption, although it is used less and less).
• The email provider usually specifies which one to use.
  
  

5. Where is the information for each field obtained from?

• Server (hostname) and port:
  It is usually given by the email provider. In Gmail, for example, it is smtp.gmail.com and the port is usually 465 (SSL) or 587 (TLS). On your hosting, it can be mail.yourdomain.com or something similar.

• Username and password:
  It is the email and password with which you log in to your email account. Be careful with providers like Google, if you use two-step verification, you will have to create a specific application password from the Google account.

• Security type (SSL/TLS):
  It is also something that your email provider will tell you. In Gmail and Outlook, it is common to use TLS (port 587) or SSL (port 465).

6. Additional Tips

• Proof of shipping: After configuring SMTP, it is very useful to send a test email from the platform to check that everything is working correctly.
• Verify your domain: If you use your own domain, consider setting up SPF, DKIM, and DMARC records. This helps emails reach your inbox and not be marked as spam.
• Strong passwords: Make sure you use strong passwords and, if your provider allows it, enable two-step authentication.