Outgoing not making it past the firewall

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: my inhouse emails send.

It produced this output: servers not inhouse do not receive my emails.

My web server is (include version): mercurymail.

The operating system my web server runs on is (include version): Windows 10pro

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): yes.

I'm using a control panel to manage my site (no, or provide the name and version of the control panell: XAMPP v3.2.4

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Mercury 4.6 ... I need a valid certificate to stop my outgoing mails from being blocked. My firewall is open. Inbound is functional.

This forum is not a general computer help discussion group. If you can't send outgoing mail that likely has nothing to do with Let's Encrypt and more to do with your SMTP configuration.

4 Likes

How does Let's Encrypt fit in to this? There are a whloe bunch of How-To's and information on configuring an email server. Our concern is related to ENCRYPTING the transport of such email(s).
Firewalls, Port forwarding, NAT, are mostly outside the scope of this community.

4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.