Cant connect SMTP

I have no idea how you’d get that response from testsaslauthd running on the system itself.

Is saslauthd running? (systemctl status saslauthd)

Above you can see they are able to use Usermin no problem because it connects direct.
So all they need to do is open port 25 and 587 to allow for scripts to submission.

systemctl status saslauthd shows its running.

please how do I do this ?
I used firewalld to add those ports today and reloaded it, so I wonder why its still not working

Can you run this command in Webmin terminal to see if you have another firewall running by any chance.

ufw status

Give us the results if any.

the result of
ufw status is inactive.

Now I’ve enabled it. and it shows active

meanwhile, @cyberndt
sudo netstat -ntlp

gives me this

Check your firewalld and see if they show up in terminal for services or ports.

sudo firewall-cmd --list-all

If not, than run the following commands:

sudo firewall-cmd --permanent --add-service=smtp
sudo firewall-cmd --permanent --add-port=587/tcp
sudo firewall-cmd --reload

root@host:~# sudo firewall-cmd --list-all
public
target: default
icmp-block-inversion: no
interfaces:
sources:
services: dhcpv6-client dns dns-over-tls ftp http https imap imaps mdns pop3 pop3s smtp smtp-submission smtps ssh
ports: 20/tcp 2222/tcp 10000-10100/tcp 20000/tcp 49152-65535/tcp
protocols:
forward: yes
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:

Why did you do that? I did not ask you to enable it… Please disable it. Wanted to make sure it wasn’t the cause of your problems with firewalld.

sudo ufw stop
sudo ufw disable
1 Like

done. ufw disabled.

Please continue helping me :cry:

nmap -v herbsofafrica.com
Starting Nmap 7.95 ( https://nmap.org ) at 2024-06-03 17:26 Eastern Daylight Time
Initiating Ping Scan at 17:26
Scanning herbsofafrica.com (104.21.29.153) [4 ports]
Completed Ping Scan at 17:26, 0.03s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 17:26
Completed Parallel DNS resolution of 1 host. at 17:26, 0.01s elapsed
Initiating SYN Stealth Scan at 17:26
Scanning herbsofafrica.com (104.21.29.153) [1000 ports]
Discovered open port 80/tcp on 104.21.29.153
Discovered open port 443/tcp on 104.21.29.153
Discovered open port 8080/tcp on 104.21.29.153
Discovered open port 8443/tcp on 104.21.29.153
Completed SYN Stealth Scan at 17:27, 4.97s elapsed (1000 total ports)
Nmap scan report for herbsofafrica.com (104.21.29.153)
Host is up (0.0041s latency).
Other addresses for herbsofafrica.com (not scanned): 172.67.149.107
Not shown: 996 filtered tcp ports (no-response)
PORT     STATE SERVICE
80/tcp   open  http
443/tcp  open  https
8080/tcp open  http-proxy
8443/tcp open  https-alt

Are we even talking about the same server?

Your firewalld status shows different ports open than your domain name you provided above.
The IP mentioned above is totally different from your domain IP.

1 Like

It’s probably not a local firewall (i.e. it’s not on the system itself). The Virtualmin installation already opened all the ports needed for the services it manages during installation.

The IP on your Linode server shows this results:

nmap -v 176.58.96.72
Starting Nmap 7.95 ( https://nmap.org ) at 2024-06-03 17:37 Eastern Daylight Time
Initiating Ping Scan at 17:37
Scanning 176.58.96.72 [4 ports]
Completed Ping Scan at 17:37, 0.13s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 17:37
Completed Parallel DNS resolution of 1 host. at 17:37, 0.34s elapsed
Initiating SYN Stealth Scan at 17:37
Scanning 176-58-96-72.ip.linodeusercontent.com (176.58.96.72) [1000 ports]
Discovered open port 993/tcp on 176.58.96.72
Discovered open port 22/tcp on 176.58.96.72
Discovered open port 143/tcp on 176.58.96.72
Discovered open port 995/tcp on 176.58.96.72
Discovered open port 443/tcp on 176.58.96.72
Discovered open port 21/tcp on 176.58.96.72
Discovered open port 110/tcp on 176.58.96.72
Discovered open port 53/tcp on 176.58.96.72
Discovered open port 587/tcp on 176.58.96.72
Discovered open port 80/tcp on 176.58.96.72
Discovered open port 465/tcp on 176.58.96.72
Discovered open port 10000/tcp on 176.58.96.72
Discovered open port 2222/tcp on 176.58.96.72
Discovered open port 20000/tcp on 176.58.96.72
Completed SYN Stealth Scan at 17:37, 9.34s elapsed (1000 total ports)
Nmap scan report for 176-58-96-72.ip.linodeusercontent.com (176.58.96.72)
Host is up (0.12s latency).
Not shown: 905 filtered tcp ports (no-response), 15 filtered tcp ports (admin-prohibited), 66 closed tcp ports (reset)
PORT      STATE SERVICE
21/tcp    open  ftp
22/tcp    open  ssh
53/tcp    open  domain
80/tcp    open  http
110/tcp   open  pop3
143/tcp   open  imap
443/tcp   open  https
465/tcp   open  smtps
587/tcp   open  submission
993/tcp   open  imaps
995/tcp   open  pop3s
2222/tcp  open  EtherNetIP-1
10000/tcp open  snet-sensor-mgmt
20000/tcp open  dnp

please what does this mean now? is Linode the problem ?

I mentioned earlier that i’m using cloudflare as proxy.
I basically use it because they provide me with SSL

We can’t use his domain name for trouble shutting because it is proxy through cloudflare. We have to use his actual IP for the server and my last post shows that port 25 inbound is blocked.

So, on that note @reigningking ask Linode to open port 25 so you can use your email server.

I still don’t know how you managed to send out email? unless it is only open outbound.
In that case your scripts will not work until Linode opens the port fully.

@reigningking still follow the instructions above about rDNS/PTR and setting up the script.
Hope all goes well from here!

1 Like

Response from Linode about rDNS/PTR is this. Looks like I might have to set it up by myself.

Follow the instructions they give you and ask if your port 25 is fully open for your email server.
Other than that, you can’t really do anything until that port is open to the public and shows open from our end.

i’ve sent them a message. Awaiting their response.
Meanwhile I found this… just thought it might aid your assistance

Port 25 is for outgoing mail and receiving mail from other servers. It has nothing to do with sending mail using a mail client or an application that uses SASL authentication.

I’d really love it if this thread were about one problem, instead of several. Not your fault, cyberndt, it started out about multiple problems. I think it’s part of why they’re having such a hard time sorting it out, trying to solve two (actually more) unrelated problems at once makes it hard to understand/solve any one of them.