Proxmox New installation but no answer in port 25

Jun 18, 2019
12
0
21
49
Hi

I want test Proxmox Mail Gateway, i have installed au my proxmox cluster one VM.

All installed but when i test a telnet access from internet to the port 25, i don't have answer.
(only localhost telnet works)

there are some things to do to activate the production release ?
firewall issue ? but i don't see firewall rules

regards
jerome
 
* How did you install the Mail Gateway?

* does running `pmgconfig sync --restart` change the situation?

* do you see anything problematic in the logs?

I hope this helps!
 
* How did you install the Mail Gateway?

* does running `pmgconfig sync --restart` change the situation?

* do you see anything problematic in the logs?

I hope this helps!

I'm having the same issue.

PMG is installed as a VM under Proxmox/KVM
Running pmgconfig sync --restart changed nothing
Logs look fine

Gerald
 
PMG is installed as a VM under Proxmox/KVM
Firewall on the PVE node maybe?
else please check the output of `ss -tlnp` if something is listening on port 25
 
No firewall on the PVE node.

root@pmg:~# ss -tlnp
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 100 127.0.0.1:10025 0.0.0.0:* users:(("master",pid=722,fd=123))
LISTEN 0 128 0.0.0.0:111 0.0.0.0:* users:(("rpcbind",pid=479,fd=4),("systemd",pid=1,fd=47))
LISTEN 0 128 127.0.0.1:85 0.0.0.0:* users:(("pmgdaemon worke",pid=947,fd=6),("pmgdaemon worke",pid=946,fd=6),("pmgdaemon worke",pid=945,fd=6),("pmgdaemon",pid=944,fd=6))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=535,fd=3))
LISTEN 0 128 127.0.0.1:5432 0.0.0.0:* users:(("postgres",pid=610,fd=3))
LISTEN 0 100 127.0.0.1:25 0.0.0.0:* users:(("master",pid=722,fd=13))
LISTEN 0 100 127.0.0.1:26 0.0.0.0:* users:(("master",pid=722,fd=116))
LISTEN 0 128 0.0.0.0:8006 0.0.0.0:* users:(("pmgproxy worker",pid=957,fd=6),("pmgproxy worker",pid=956,fd=6),("pmgproxy worker",pid=955,fd=6),("pmgproxy",pid=954,fd=6))
LISTEN 0 128 127.0.0.1:10022 0.0.0.0:* users:(("pmgpolicy child",pid=7141,fd=6),("pmgpolicy child",pid=7140,fd=6),("pmgpolicy child",pid=7139,fd=6),("pmgpolicy child",pid=7138,fd=6),("pmgpolicy child",pid=7137,fd=6),("pmgpolicy",pid=924,fd=6))
LISTEN 0 128 127.0.0.1:10023 0.0.0.0:* users:(("pmg-smtp-filter",pid=5769,fd=5),("pmg-smtp-filter",pid=5768,fd=5),("pmg-smtp-filter",pid=5752,fd=5))
LISTEN 0 128 127.0.0.1:10024 0.0.0.0:* users:(("pmg-smtp-filter",pid=5769,fd=7),("pmg-smtp-filter",pid=5768,fd=7),("pmg-smtp-filter",pid=5752,fd=7))
LISTEN 0 128 [::]:111 [::]:* users:(("rpcbind",pid=479,fd=6),("systemd",pid=1,fd=49))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=535,fd=4))
LISTEN 0 100 [::1]:25 [::]:* users:(("master",pid=722,fd=14))
LISTEN 0 100 [::1]:26 [::]:* users:(("master",pid=722,fd=117))
 
could you please post the (anonymized) output of:
* `pmgconfig dump`?
* PMG needs a static IP, and the hostname set in PMG needs to resolve to that ip
 
root@pmg:~# pmgconfig dump
could not change directory to "/root": Permission denied
composed.wl_bounce_relays = pmg.mydomain.com
dns.domain = mydomain.com
dns.hostname = pmg
ipconfig.int_ip = 192.168.100.41
pmg.admin.advfilter = 1
pmg.admin.avast = 0
pmg.admin.clamav = 1
pmg.admin.custom_check = 0
pmg.admin.custom_check_path = /usr/local/bin/pmg-custom-check
pmg.admin.dailyreport = 1
pmg.admin.demo = 0
pmg.admin.email = itservices@mydomain.com
pmg.admin.http_proxy =
pmg.admin.statlifetime = 7
pmg.clamav.archiveblockencrypted = 0
pmg.clamav.archivemaxfiles = 1000
pmg.clamav.archivemaxrec = 5
pmg.clamav.archivemaxsize = 25000000
pmg.clamav.dbmirror = database.clamav.net
pmg.clamav.maxcccount = 0
pmg.clamav.maxscansize = 100000000
pmg.clamav.safebrowsing = 1
pmg.mail.banner = ESMTP Proxmox
pmg.mail.conn_count_limit = 50
pmg.mail.conn_rate_limit = 0
pmg.mail.dnsbl_sites =
pmg.mail.dnsbl_threshold = 1
pmg.mail.dwarning = 4
pmg.mail.ext_port = 25
pmg.mail.greylist = 1
pmg.mail.helotests = 0
pmg.mail.hide_received = 0
pmg.mail.int_port = 26
pmg.mail.max_filters = 15
pmg.mail.max_policy = 5
pmg.mail.max_smtpd_in = 98
pmg.mail.max_smtpd_out = 98
pmg.mail.maxsize = 20485760
pmg.mail.message_rate_limit = 0
pmg.mail.rejectunknown = 0
pmg.mail.rejectunknownsender = 0
pmg.mail.relay = 192.168.100.5
pmg.mail.relaynomx = 0
pmg.mail.relayport = 25
pmg.mail.smarthost =
pmg.mail.smarthostport = 25
pmg.mail.spf = 1
pmg.mail.tls = 0
pmg.mail.tlsheader = 0
pmg.mail.tlslog = 0
pmg.mail.verifyreceivers = 450
pmg.spam.bounce_score = 0
pmg.spam.clamav_heuristic_score = 3
pmg.spam.languages = all
pmg.spam.maxspamsize = 262144
pmg.spam.rbl_checks = 1
pmg.spam.use_awl = 1
pmg.spam.use_bayes = 1
pmg.spam.use_razor = 1
pmg.spam.wl_bounce_relays =
pmg.spamquar.allowhrefs = 1
pmg.spamquar.authmode = ticket
pmg.spamquar.hostname =
pmg.spamquar.lifetime = 7
pmg.spamquar.mailfrom =
pmg.spamquar.port = 8006
pmg.spamquar.protocol = https
pmg.spamquar.reportstyle = verbose
pmg.spamquar.viewimages = 1
pmg.virusquar.allowhrefs = 1
pmg.virusquar.lifetime = 7
pmg.virusquar.viewimages = 1
postfix.dnsbl_threshold = 1
postfix.int_ip = 192.168.100.41
postfix.mynetworks = 127.0.0.0/8 [::1]/128 192.168.100.0/22 192.168.100.0/22 192.168.100.5/32
postfix.transportnets =
postfix.usepolicy = 1
postgres.version = 11
 
hmm - on a hunch :
* please try to restart postfix (pmgconfig sync --restart only reloads it, which is enough for most situations but might not be for the binding to another ip)
* if this does not help - please make sure you don't use customized templates (see https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#_service_configuration_templates) - or if you do that that all relevant lines (lines with the listen definitions in master.cf.in and inet_interfaces in main.cf.in) use the proper ips (or none at all which is the default).

if this does not help - please post your /etc/postfix/main.cf and /etc/postfix/master.cf (anonymized, after you've run `pmgconfig sync`)

I hope this helps!
 
Interestingly, restarting postfix got things working. I'm pretty sure I did a reboot during my testing, which should have started postfix as well.

Thanks for your help!

Gerald
 
  • Like
Reactions: Stoiko Ivanov
i can confirm this issue. i just did a fresh installation of the latest PMG (6.1) and after the installation was done i went into the web interface and configured the mail proxy settings (mainly the default relay and my domain) but port 25 on postfix was only bound to 127.0.0.1.
after manually restarting postfix via the cli it was bound to 0.0.0.0 as it should be.

so i would consider this a bug in the GUI as it seems to only reload intsead of restart postfix during this initial config and postfix seems to need a restart to change the bind-ip

regards
Pascal
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!