Cannot connect with TSL/SSL

[nebulon]

@testdesk hm so also not really more information from FreeScout on the error.
Freescout does not have the Cloudron mail addon enabled, since a common use-case is to use external mailboxes as well. This is why it is correct to use the regular mailserver domain in this case my.example.com

@girish can correct me if I am wrong here, but I don't think the mail server even allows non secure transfer anyways, so if encyption set to "no" it is fine as well.

Still I have to see if I can reproduce this with a new FreeScout instance against the Cloudron mail server later today.

[girish]

@testdesk Setting encryption to NONE is correct setting when FreeScout is installed on the same server as Cloudron mail. When FreeScout is installed in another server, then you have to use TLS.

The reason is a bit esoteric. Internally, Cloudron uses containers and the mail container is called 'mail'. Many apps don't work properly if you try to connect with the hostname as 'mail' but the TLS certificate says 'my.domain.com' (because of hostname mismatch). So, for historic reasons, we do not enable TLS for connection within the server itself. In this case, FreeScout is in same server as mail server and thus TLS option is not available. This is totally safe because the full connection is within the server. If you move your freescout to another server, then remember to put it to TLS.

[girish]

I have put a doc note here - https://docs.cloudron.io/apps/freescout/#cloudron-mailbox

[ianhyzy]

@girish I've copied the info from the screenshot here (Freescout and cloudron are on the same machine; mailgun is configured as the outbound SMTP provider in Cloudron settings; there are two mail-enabled domains) but I'm getting an error about the port being closed:

Could this be my firewall/ISP or did I misconfigure something?

[micmc]

@ianhyzy Try PORT 2525 with TLS/SSL encryption

Andy

[ianhyzy]

@micmc Got the same port blocked error with that:

[micmc]

@ianhyzy Try NO encryption?

[ianhyzy]

@micmc same error

[micmc]

@ianhyzy I'm guessing your 'mail' mx is the cloudron one and that ALL email settings are enabled and GREEN for the domain you use for your FreshScout?

[ianhyzy]

@micmc Yup, green light and works with other apps

[micmc]

@ianhyzy I meant the status like this for the specific domain

[ianhyzy]

@micmc yup, all good:

[girish]

@ianhyzy said in Cannot connect with TSL/SSL:

Could this be my firewall/ISP or did I misconfigure something?

Yes, most likely. Is port 587 open in your firewall ? Also, if this server is at home, do you have loopback NAT working on your router?

[micmc]

@ianhyzy Your SMTP outbound is set as RELAY not as DIRECT this is something I was wondering because normally Cloudron should sety this automatically at installation time if your SMTP status is set. It seems to me that it might means you've set an outbound SMTP service on this domain and you now try to use the direct settings.

[ianhyzy]

@micmc yeah I have mailgun set as the outbound SMTP server, but I get similar errors when I try to use mailgun directly. I would screenshot the error but it's a stack trace that takes up the whole screen

[ianhyzy]

@girish I have 587 port forwarded and no, I need to look into NAT loopback

[micmc]

@ianhyzy Yeah, that's what I thought. Try to use default SMTP (no mailgun) on the domain and then use the same settings on the app. OR the contrary on both as well. The same SMTP for the domain and the app.

[ianhyzy]

@girish I use a Unifi UDM-PRO at home and from what I can tell hairpin / NAT Loopback is enabled by default, and I don't recall ever disabling it

[micmc]

@girish He'd set mailgun as his default SMTP relay on the outbound mail for the domain, but apparently the app installed with default SMTP assumption?

Will apps install with the SMTP relay set on domain's outbound mail, or it will they still assume the default settings, even if a relay is set before apps installation?

[ianhyzy]

@ianhyzy of course I tried Mailgun again and it seems to have worked - I must have had something off earlier. It seems to be taking the inbox a little longer than I thought to receive messages but they are coming in.