Hm. I have the same Vultr setup as @MathiasFoster and @jryans here, and I ran into the same (Net::OpenTimeout) issue. ufw allow https got my incoming email working. But now the site won’t send any mail. Before setting up incoming email, outgoing email had been working fine. I don’t have anything f…

@Simon_Manning & @pfaffman – thank you again for the input and pointers, it got me on the right track. I decided to try MailerSend , as their current free plan is pretty generous. It should suit our nonprofit effort for some time. Things are up and running well so far :grin:

The mail receiver is independent of Discourse and email sending, it just acts as a simple email server configured only to receive emails, using the Discourse API to push those emails in to Discourse. The only thing I can think of in setting it up that might affect sending is setting reply by email …

[immagine] ToddZ: But now the site won’t send any mail. Before setting up incoming email, outgoing email had been working fine. What happens if you try sending a test email to an address you get from https://www.mail-tester.com/ ? I can’t see how changing ufw allow https could affect incoming…

[immagine] Jay Pfaffman: I can’t see how changing ufw allow https could affect incoming mail. I believe Vultr (or maybe just installing Docker when ufw is present) have some rules that prevent containers talking to each other, meaning mail receiver can’t connect to Discourse. ufw allow https …

But docker bypasses ufw, isn’t it?

On the default network, only if a container connects directly to another container by local IP address, that is the local IP address of the container itself. When mail receiver looks up your Discourse domain name, it won’t get that local IP so it has to leave its Docker network and will pass throug…

I was thinking this topic, where you were participating too: [immagine] Will UFW limit Discourse too? installation How can Discourse bypass UFW? I had enabled only port 22 so all other ports should be closed then. But a forum worked anyway. How’s that possible? DigitalOc…

That’s a separate situation, albeit related. That’s connections coming in from the outside and Docker adds rules to allow exposed ports through. [immagine] Will UFW limit Discourse too? Chain DOCKER (2 references) pkts bytes target prot opt in out source destination …

@Simon_Manning @pfaffman – EDIT: see end of message Thanks for the responses! I’ve had to be away for a bit, but am digging back into this… [immagine] Simon Manning: Just to confirm, it sounds like you have these (among the rest) in app.yml: DISCOURSE_SMTP_USER_NAME: admin@tasat.org DISCOURS…

[immagine] ToddZ: So I guess all the troubleshooting is out the window and I have to look for a new email host that doesn’t impose that requirement. It’s certainly not exhaustive but there are some sending service recommendations in the install documentation along with some basic information …

[immagine] ToddZ: So I guess all the troubleshooting is out the window and I have to look for a new email host that doesn’t impose that requirement. Right. You can switch to mailgun flex, though they make it hard to figure out. About once a month I email them asking about why it’s so hard to…

Configurato mail-receiver, ma ora il sito non invia più email?

Supporto Installazione

Jagster (Jakke Flemming) 26 Settembre 2023, 3:14pm 7

Stavo pensando a questo argomento, a cui hai partecipato anche tu:

Argomento		Risposte	Visualizzazioni
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	400	Gennaio 26, 2023
Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver Self-Hosting email , how-to , advanced-setup , mail-receiver	78	48797	Marzo 27, 2026
Email receive issue Bug mail-receiver , fixed	30	455	Aprile 13, 2026
Mail-receiver relay access denied Self-hosting mail-receiver	21	1874	Gennaio 26, 2025
Able to receive e-mail in mail-receiver but NOT in Discourse? Self-hosting	9	1821	Dicembre 25, 2020

Configurato mail-receiver, ma ora il sito non invia più email?

Argomenti correlati