==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.1
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version:  FreeBSD 14.1
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

nc -zv 192.168.2.3 445  (192.168.2.3 = server IP)
Connection to 192.168.2.3 445 port [tcp/microsoft-ds] succeeded!

So on a local network iRedmail works flawless with Samba419.

Via LAN-to-LAN VPN network (from 192.168.10.2 also FreeBSD 14.1)
nc -zv 192.168.2.3 445
nc: connect to 192.168.2.3 port 445 (tcp) failed: Operation timed out

nc -zv 192.168.2.3 80 (Testing port 80 works)
Connection to 192.168.2.3 80 port [tcp/http] succeeded!

root@mx:/usr # nmap -sT 192.168.2.3
Nmap scan report for 192.168.2.3
Host is up (0.000045s latency).
Not shown: 988 closed tcp ports (conn-refused)
PORT    STATE SERVICE
22/tcp  open  ssh
25/tcp  open  smtp
80/tcp  open  http
110/tcp open  pop3
139/tcp open  netbios-ssn
143/tcp open  imap
443/tcp open  https
445/tcp open  microsoft-ds
465/tcp open  smtps
587/tcp open  submission
993/tcp open  imaps
995/tcp open  pop3s

Nmap done: 1 IP address (1 host up) scanned in 6.17 seconds

Any idea what caused the blocking Ports of 445 and 139 for external IP?

Could the /iRedmail-1.7.1/samples/firewall/nftables.conf file be the solution?
How can this be updated?

Thanks in advance!!

Best regards,
Andre

Ps. iRedmail is a great piece of impressive software!!!