pmg-smtp-filter.service: Main process exited

Pablo_Gomez

Member
Apr 17, 2018
6
0
6
43
hello, I'm starting to implement Proxmox Mail Gateway and I'm having problems with the smtp filter.
the pmg-smtp-filter service stops and therefore stops passing mail through the gateway.

The error shown in the logs is:

Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Killing process 11313 (pmg-smtp-filter) with signal SIGKILL.
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Killing process 12539 (pmg-smtp-filter) with signal SIGKILL.
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Killing process 12541 (pmg-smtp-filter) with signal SIGKILL.
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Killing process 12655 (pmg-smtp-filter) with signal SIGKILL.
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Unit entered failed state.
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Failed with result 'exit-code'.


eventually I'm also seeing a message like:

Apr 17 16:49:00 ubuntu pmg-smtp-filter[768]: Filter daemon (re)started (max. 40 processes)

I'm not sure if they are related.

Can I search in a configuration file for the arguments used?

Thanks, greetings
 
How much RAM do you have?

And post your:

> pmgversion -v
 
Hi,

6144 RAM I could increase it. it is a VM

# pmgversion -v
proxmox-mailgateway: 5.0-9 (API: 5.0-69/0617282d, running kernel: 4.13.16-1-pve)
pmg-api: 5.0-69
pmg-gui: 1.0-36
proxmox-spamassassin: 3.4.1-54
proxmox-widget-toolkit: 1.0-13
pve-kernel-4.13.16-1-pve: 4.13.16-45
pve-kernel-4.13: 5.1-43
pve-kernel-4.13.13-5-pve: 4.13.13-38
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-2
pve-firmware: 2.0-4
libpve-common-perl: 5.0-30
pmg-docs: 5.0-14
pve-xtermjs: 1.0-2
libarchive-perl: 3.2.1-1
libxdgmime-perl: 0.01-3
zfsutils-linux: 0.7.6-pve1~bpo9
libpve-apiclient-perl: 2.0-2




# pmgconfig dump
composed.wl_bounce_relays = ubuntu.*****.**
dns.domain = ******.**
dns.hostname = ubuntu
ipconfig.int_ip = 194.***.***.***
pmg.admin.advfilter = 1
pmg.admin.avast = 0
pmg.admin.clamav = 1
pmg.admin.dailyreport = 1
pmg.admin.demo = 0
pmg.admin.email = sistemas@*******.**
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 = zen.spamhaus.org,blackholes.easynet.nl,dsn.rfc-ignorant.org,bl.spamcop.net,cbl.abuseat.org,ix.dnsbl.manitu.net,rabl.nuclearelephant.com
pmg.mail.dwarning = 4
pmg.mail.ext_port = 25
pmg.mail.greylist = 1
pmg.mail.helotests = 1
pmg.mail.hide_received = 0
pmg.mail.int_port = 26
pmg.mail.max_filters = 38
pmg.mail.max_policy = 5
pmg.mail.max_smtpd_in = 100
pmg.mail.max_smtpd_out = 100
pmg.mail.maxsize = 52428800
pmg.mail.message_rate_limit = 0
pmg.mail.rejectunknown = 0
pmg.mail.rejectunknownsender = 1
pmg.mail.relay = 192.168.11.22
pmg.mail.relaynomx = 1
pmg.mail.relayport = 25
pmg.mail.smarthost =
pmg.mail.spf = 1
pmg.mail.tls = 1
pmg.mail.tlsheader = 1
pmg.mail.tlslog = 1
pmg.mail.verifyreceivers =
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_sites = zen.spamhaus.org,blackholes.easynet.nl,dsn.rfc-ignorant.org,bl.spamcop.net,cbl.abuseat.org,ix.dnsbl.manitu.net,rabl.nuclearelephant.com
postfix.int_ip = 194.***.***.***
postfix.mynetworks = 127.0.0.0/8 [::1]/128 194.179.53.130/32 192.168.96.0/20 192.168.20.0/24 192.168.0.0/20 192.168.11.22/32
postfix.transportnets =
postfix.usepolicy = 1


Best regards
 
Last edited:
Hi,

Yesterday I had to stop using the gateway. The service was stopped several times during the morning and part of the afternoon leaving no email to employees.

pmgpolicy.service is also crashing

# cat /var/log/syslog.1 |grep exited
Apr 17 00:02:20 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 01:51:43 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 04:53:43 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 09:10:50 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 10:49:19 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 13:13:01 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 13:20:24 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 14:08:55 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 14:51:34 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 15:48:53 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 16:41:20 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 17:42:59 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 20:09:07 ubuntu systemd[1]: pmg-smtp-filter.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Apr 17 20:09:11 ubuntu systemd[1]: pmgpolicy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

thanks for your help
 
Maybe an issue with your virtualization host (e.g. the hardware used)?
 
Hi,
is running on proxmox VE 5.1 with other VMs running without problems

What could I check?

Best regards
 
Did you any additional configuration on the PMG? E.g. custom clamav database settings and configs?
 
I have not changed the configuration of ClamAV. It is a clean installation and newly configured from the web environment.

I'm used to configuring spamassassin, clamav, postgrey, etc. In PMG I can not find the configuration files of each filter to check parameters that may be incorrect.

I think everything is done from the services like pmg-smtp-filter. Where is the configuration file?

in / etc / pmg / I see configuration files, but they look like the typical .local and do not contain all the complete configuration.

Thank you very much
 
Hi,

The only strange thing is maybe having 2 domains with punycode configured because they use the letter Ñ

domain g********ña.es I have configured it as punycode xn--g********a-19a.es
domain l***ña.com I have configured it as punycode xn--l***a-rta.com

On the tracking center screen, I can see that I have been sending and receiving emails to those domains correctly.

Best regards
 

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!