E-mail wordt niet verzonden na update

AI-generated summary

CryptoRux reported an issue where emails stopped sending after updating their Discourse forum, despite successful SMTP tests outside the container. Configuration used port 587 with STARTTLS and credentials for rux@crypto.ba. After rebuilding the app, emails failed with “connection refused” CryptoRux. Ed_S suggested testing SMTP from inside the container and shared a troubleshooting link. CryptoRux confirmed testing from inside helped, but emails still didn’t arrive despite the UI showing “SENT” CryptoRux. Ed_S recommended tcpdump and noted switching to port 2525 helped in their case. CryptoRux emphasized their iRedMail server had worked for 2 years without issues. After hours of log checks, they still saw “Email Sent” but no delivery CryptoRux. Ed_S suggested discourse-doctor and mail-tester.com for diagnostics. pfaffman clarified that “Email Sent” means Discourse handed off the email — the issue likely lies with the mail server’s spam folder or sender/recipient domain mismatch (e.g., noreply@forum.crypto.ba vs. rux@crypto.ba). CryptoRux resolved the issue by adjusting their iRedMail server settings to allow the sender address to match the authenticated SMTP username, citing the error: “Recipient address rejected: Sender is not same as SMTP authenticate username” — a documented iRedMail issue. Gratitude was expressed to both helpers for guiding the solution.

hello my favorite forum systems :slight_smile:

Im having a problem with sending email from discourse forum.

When i try to test SMTP, everything goes well, as you can see on printscreen

Im using 587 port for SMTP wish STARTTLS

  DISCOURSE_SMTP_ADDRESS: email.crypto.ba
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: rux@crypto.ba
  DISCOURSE_SMTP_PASSWORD: PASSWORD   
  DISCOURSE_SMTP_ENABLE_START_TLS: true

but when i add those parameters to app.yml and rebuild app, it just wont send any mail

Can someone point me to the solution?

What could block discourse to use my smtp :frowning: logs are just showing connection refused

(You might need to wait for the world to turn a bit more to get some help…)

All I know is that there can be a difference between what your host can do and what the processes in your container can do. How did you run your SMTP test - inside the container, or outside?

I also know there’s a checklist somewhere for email trouble… maybe this thread:

I have tested my smtp outside of container, now you gave me idea to try from inside :slight_smile:

Thank you for link, will check now

Well i have managed to get through now, when testing email on /admin/email it says “SENT” but im not getting any email.

weird, i can login to that same email send and recieve

Sorry I’m out of ideas. You can see the packets with for example
tcpdump -c 19 -A -n port 587
but as the traffic is mostly encrypted, it might not help. It might show that no connection is made, or is rejected.

Edit: I found I had to switch to port 2525, but I don’t remember why. It’s a standard alternative, apparently.

Are you still stuck? Now, or 48 hours from now, might be good times to bump this thread with an update.

Sorry i could not send email from discourse, i really dont know why is this such a problem, if i can test and use SMTP server and discourse just wont send through it

im using my own email server, (iredmail), that has been online almost 2years now with no problems.

I trully wonder what could be problem

I spent last 3 hours checking logs from discourse, to find out what could block mail sending its not rocket science, but no luck.

Now im at part where i can send email, after clicking send email, it says “Email Sent” but im not receiving any mail

Have you tried discourse-doctor?

It can send mail, including sending it to a spam-scoring service, which is a good way to see if mail is deliverable to a well-known service or not deliverable just to your service. The doctor says:

For a robust test, get an address from mail-tester.com

If it says “mail sent” then it is fairly certain that discourse delivered the mail to your mail service and you need check your spam folder and the logs at your mail service.

A common problem is that your forum is forum.example.com and the default notfication email is noreply@forum.example.com but your mail service is configured only for xxx@example.com. if that’s the case then you need to change the notification email (or reconfigure your mail server).

forum is on https://forum.crypto.ba

image

I have found solution, its my mail server setup, i needed to add some options!

Now its working

Problem was
" Recipient address rejected: Sender is not same as SMTP authenticate username"

Thank you both, after i read your posts it somehow guided me to solution.