SMTP Configuration & Setup

All website applications should use SMTP to send emails instead of relying on the default PHP mailer on the web server. This will prevent issues with emails being potentially blocked by the receivers email provider or ending up as spam/junk mail.

Wordpress SMTP

To configure SMTP for wordpress applications, Jump Media use the following WordPress plugin which will allow you enter your SMTP credentials for mail sending.

WP Mail SMTP by WPForms

Laravel SMTP

For Laravel applications, it is required that the SMTP credentials are stored from within the applications .env file.

SMTP Testing

For development, it is required that testing SMTP credentials are used to prevent any emails from development being sent.

Jump Media use MailTrap as an SMTP provider for testing email functionality.

It is required that a new account is created on MailTrap using the clients shared mailbox project@wejumphigher.co.uk. The credentials for these should be saved in Jump Media's password manager and added to the project documentation.

MailTrap - https://mailtrap.io

SMTP2GO

Jump Media use SMTP2GO SMTP provider for production applications.

It is required that a new account is created at SMTP2GO using the jump media account at login@wejumphigher.co.uk. The credentials for these should be saved in Jump Media's password manager and SMTP user credentials added to the project documentation.

SMTP2GO - https://www.smtp2go.com/

SMTP2GO Account Setup

  1. Login to account at SMTP2GO.
  2. It is required that the 'Sender Domain' is added to help with the delivery of mail and to verify where mail is sent from. This will help prevent emails being shown as sent 'via smtp2go.com'.
  3. It is required that the domains DNS is updated to add the relevant CNAME records for SMTP2GO. (If DNS is managed through CloudFlare, please ensure the record is not proxied)

alt text

  1. You can find the credentials to connect to the SMTP mailing server by navigating to Settings > User Accounts. It is required that a new SMTP user is created for the project.
  2. Depending on clients MX port settings settings, it may be required to whitelist SMTP2GO IP addresses with their incoming MX server to prevent emails from being blocked or marked as spam. *This is required if sending emails to domains with the same domain as the sender email.