Incoming Email: cannot open mailbox

[james]

Hello @phneutre
Where does the 9595 port come from?
Cloudron uses port 995 for pop3 according to https://docs.cloudron.io/email#pop3

[pHneutre]

@james I don't know but it was a bad example, I've got this error for 995 as well:

[james]

Hello @phneutre
Did you setup the wildcard alias according to the docs?
https://docs.cloudron.io/packages/discourse/#incoming-email-setup

For unique addresses per category, setup mail aliases for forum@YourMailDomain.TLD. For a category named offtopic, create a mail alias like forum@YourMailDomain.TLD. Create a wildcard mail alias * to choose any category name freely.

[pHneutre]

@james I didn't realize it was necessary, thanks.
I set it up on the 10th of march at 17:49. From this moment, the Discourse logs hasn't shown any TCP timeout on 995 anymore. But mails remain ineffective.
These errors remain afterwards:

I suspect the SMTPServerBusy reveals a new problem?

[james]

Hello @phneutre

Can you share your Discourse configuration?

[pHneutre]

@james As soon as I understand what you mean by that

[james]

Hello @phneutre
Did you configure anything in discourse for incoming mails?
See: https://meta.discourse.org/t/troubleshoot-reply-by-email/42026

[pHneutre]

@james Ah yes sure.
POP3 polling enabled and :

Note: POP3 polling port was actually 9595 (and wasn't considered modified by discourse (no green dot)), so that explains the 9595 call (but why was there a 995 call too then?). I just changed it to 995 and tried again to send an email (and waited for the 5 min of polling period), but no luck.

[pHneutre]

Bumping this thread in case someone got an idea.

[nebulon]

@phneutre so if you open a webterminal into the app and run env | grep MAIL you should see all the possible connection details. Note that using mail as the email server domain, means the app will connect via the local route and hence does not necessarily need encrypted connection at all, if that helps with the discourse pop3 setup.