MailJet SMTP is Not Working

Product Support Self-hosting

AI-generated summary

The user KhoiUSA reported that MailJet SMTP was not working on their Discourse forum, with errors indicating a timeout connecting to in-v3.mailjet.com:587. They were also seeing a warning that outgoing emails were disabled for non-staff users. maiki suggested checking the disable emails setting, which KhoiUSA confirmed resolved the issue. However, further testing showed the server couldn’t connect to MailJet via telnet, indicating a network-level problem. supermathie and pfaffman pointed to firewall or port blocking, with KhoiUSA confirming that port 587 was blocked by their cloud provider (Digital Ocean), which they resolved by contacting support. The issue was ultimately due to a blocked port, not configuration errors.

1

Hello, my forum uses MailJet as the SMTP server for my Discourse Forum. However, it seems as if the email system is not working. Below is an image of my email settings and the App.YML email configuration settings.

image
image820×594 15.5 KB

App.YML File E-Mail Configuration:
image

Also, sending a test e-mail gives me this error message:

image
image832×220 3.5 KB

I am also getting the warning “Outgoing email has been disabled for non-staff users.” when in the forum site.

image
image462×103 2.44 KB

I’m stuck between if I have incorrect SMTP credentials or my server cannot contact the SMTP server, since it says “Timeout to open TCP connection to in-v3.mailjet.com:587 (exceeds 5 seconds)”

If anybody knows the reason or has a solution, please tell me. Thanks!

2

Is this a new site? Did anything change recently, such as migrating to a new server? :thinking:

You might want to check your disable emails setting (https://anomicforum.xyz/admin/site_settings/category/all_results?filter=disable%20emails).

3

First: does it work from the host?

telnet in-v3.mailjet.com 587

5

Thanks, that fixed the issue. Also, this is technically a new “site” since my forum shut down for a few months, then came back and I restored it via a backup.

I ran that command and this was the output:
Looks like it failed to connect.

image

6

Ok, that means we can rule out Discourse, which simplifies things.

Next check your firewall rules, including those that may exist in the DO (looks like your server is hosted at Digital Ocean) control panel.

Also contact DO and if they’re blocking outbound email on 587 from the server. Ask them to remove that block.

7

Thanks, I’ve found out apparently Port 587 is blocked to prevent email spam. I’ve contacted the cloud provider for support. I will update you on this shortly.

8

You can try port 2525 instead.

We also Troubleshoot email on a new Discourse install

9

Yep, it was indeed a blocked port. I have resolved the issue now. Thanks!