SMTP/Transactional Emails FAQs

JangoMail provides a platform for broadcast and transactional messages all in one package. From setup to sending, we have you covered. If you don't find the information you need below, feel free to submit a support ticket.

• What are the settings I should use to set up my relay for a desktop client?
• What are the settings I should use to set up my relay for a web application?
• How are bounces handled?
• How are unsubscribes handled?
• Can I use the standard JangoMail unsubscribe link in my email messages sent via the SMTP relay?
• My email client sends emails encoded in base 64 or quoted-printable. Will there be any issues with this?
• What are the costs to use the SMTP relay?
• What happens if I attempt to send more emails through the SMTP relay than my account allows?
• Is my email message delivered to my recipient instantly through the SMTP relay?
• Can click-tracking affect phishing filters?
• What happens if I send email from either an IP address or a From Address that I have not yet authorized under Settings → Transactional Emails → SMTP Relay?
• Is there a max message size I can send?

For a desktop client using the relay...

1. Relay (set the outgoing SMTP server) to express-relay.jangosmtp.net
2. Use port 2525 or 587. Port 25 is often blocked by various ISPs. If you want to use encryption, port 465 provides explicit SSL/TLS access. STARTTLS can be used with any port except 465 and it must be enabled on the client.
3. Authenticate using your account’s username and password. We support PLAIN and LOGIN authentication schemes across all ports and all SSL settings. Please keep in mind that, due to security reasons, our relay service will not respond to the Ping utility when used to test the accessibility of our service.
4. Set tracking options by going to Settings → Transactional Settings → Relay → Tracking

For a web application using the relay...

1. Go to Settings → Transactional Settings → Relay IP Authentication, and enter your web server's IP address to authorize it to send emails.
   1. Alternatively you can use SMTP AUTH authentication with your account username/password.
2. Relay (set the outgoing SMTP server) to express-relay.jangosmtp.net
3. Use port 2525 or 587. Port 25 is often blocked by various ISPs. If you want to use encryption, port 465 provides explicit SSL/TLS access. STARTTLS can be used with any port except 465 and it must be enabled on the client.
4. Set tracking and authentication options by going to Settings →  Transactional Settings  → Relay

If you send an email message to an address that is on your account's Bounce list, then that email message won't be sent, and instead, a notification will be sent back to the sender with this error message:

Web Service Exception BouncedEmailAddressException: Email address is on account's Bounce list. System.Exception: JangoMailNamespace.BouncedEmailAddressException: Web Service Exception BouncedEmailAddressException: Email address is on account's Bounce list.

If you send an email message to an address that is not yet on your account's bounce list, but the recipient address is invalid, then that address will then be added to your account's bounce list. If you wish to receive an email notification of the bounceback, like you would with a "regular" SMTP service, then set the appropriate options in Settings  → Bounce Settings → Bounce Handling. 

If you send an email message to an address on your account's Unsubscribe list, the email message will not be sent and instead an error notification containing the following text will be sent back to the From Address on the email message:

Web Service Exception UnsubscribedEmailAddressException: Email address is on account's Unsubscribe list. System.Exception: Namespace.UnsubscribedEmailAddressException: Web Service Exception UnsubscribedEmailAddressException: Email address is on account's Unsubscribe list.

Yes, you can. The link is based on the tracking domain used with your account. We strongly recommend that you set up a branded, Custom Tracking Domain. If you do not have a custom tracking domain in place, link to:

https://x.jmxded153.net/u.z?***uniqueid****

If you are using a Custom Tracking Domain, replace x.jmxded153.net with the tracking domain specific to your account. Ensure that it has /u.z?***uniqueid**** at the end of the url. 

Everything will work fine. JangoMail's SMTP relay will not only preserve your email client's original encoding scheme, but it will also still be able to add the open-tracking and click-tracking entities to your email message.

If you have a JangoMail account, transactional email are combined with campaigns and count towards your monthly quota. It is based on the number and size of the emails you send per month. Find more information on pricing here. If you are interested in only sending transactional email, then JangoSMTP offers transactional-only service at a lesser price. Find out more at the JangoSMTP website.

If your account is marked as an "overage allowed" account, then you will never encounter a hard limit. If your account does have set limits, as most do unless you've requested otherwise, then when your emails exceed your account limits, the sender will get return notifications indicating that the account is over limit and that the email was not delivered. You may upgrade inside your account and submit a ticket to request that any unsent emails from the last three days be resent. 

Your email message is delivered within 3-5 seconds after it arrives at express-relay.jangosmtp.net. That 3-5 seconds is required for processing, such as adding the open-tracking and click-tracking mechanisms, signing with DomainKeys (and DKIM), and checking against your account's Bounce and Unsubscribe lists.

Yes, depending on the email program that the recipient is using. Since click-tracking alters your original URL, spam filters may detect this as a phishing attempt. The smarter email clients get though, the less of an issue this will become over time. Additionally, if your display text itself isn't a URL, then there won't be an issue. For example:

This is the best web site. (good way to link)

versus

https://www.jangomail.com/ is the best web site. (bad way to link)

It's very important to use your own Custom Tracking Domain. 

An error notification will be sent to the Sender of the email message with the IP and From Address infomation:

Relaying denied for [IP Address] / "Joe Smith"

 The max message size that will be accepted by the relay is 30 MB. Messages should not go over this limit. JangoMail's SMTP relay actually accepts a message size higher than most providers. Gmail, for instance, limits the message to 25 MB. Overall, it's important to keep message size small as this contributes to higher deliverability.