Spam reports not sending

Robert H. · Jan 16, 2023

Hey there,

we just realized that since the last update we do not receive any spam reports no more.
when manually triggering: "pmgqm send --receiver email@domain.com"

the spam report we do receive following lines in mail.log:

Jan 16 10:53:54 mta01 postfix/smtpd[1133]: connect from localhost.localdomain[127.0.0.1]
Jan 16 10:53:54 mta01 postfix/smtpd[1133]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 16 10:53:54 mta01 postfix/smtpd[1133]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2

Our setup is following: we use a licenced dual node system where the 'node' is sender for the spam reports.

We did already some tests like changing the sending server, changing the "Spamreport Style", ...
When sending with "pmgqm send --debug 1" we do get the right content dumped into the CLI
We checked the old log files, for us the main difference is the lost con, and the mail=1 as well as commands. (for us it looks the server itself is not allowed to send out the spam reports not more?!?)

Any ideas on how to fix or trace that issue?
Is it only us who got that bug?

br,

Stoiko Ivanov · Jan 16, 2023

Robert H. said:
Our setup is following: we use a licenced dual node system where the 'node' is sender for the spam reports.

The PMG clusterstack usually only sends out the reports from the master node ... - how did you configure this?

Robert H. said:
the spam report we do receive following lines in mail.log:

Jan 16 10:53:54 mta01 postfix/smtpd[1133]: connect from localhost.localdomain[127.0.0.1]
Jan 16 10:53:54 mta01 postfix/smtpd[1133]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 16 10:53:54 mta01 postfix/smtpd[1133]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2

There should be more in the logs - and in it's default configuration the spamreports are sent out at 00:05

please provide more of the logs (anonymize what you must in a consistent manner)

Thanks!

Robert H. · Jan 16, 2023

Thank you for your quick reply,

Stoiko Ivanov said:
The PMG clusterstack usually only sends out the reports from the master node ... - how did you configure this?

we defined in Configuration -> Spam Detector -> Quarantine: Quarantine host the url of the node

Stoiko Ivanov said:
There should be more in the logs - and in it's default configuration the spamreports are sent out at 00:05

these logs from mail.log were created due to the manual triggering of the "pmgqm send --receiver email@domain.com"

These are the logs from the midnight job:

Code:

Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: connect from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: connect from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: connect from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: connect from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2
Jan 15 00:05:05 mta01 postfix/smtpd[1974430]: connect from localhost.localdomain[127.0.0.1]
...

do you need more / other logs than mail.log? when I triggered the manual sending i only saw content in mail.log

Stoiko Ivanov · Jan 16, 2023

Robert H. said:
we defined in Configuration -> Spam Detector -> Quarantine: Quarantine host the url of the node

This is just what is used for the links in the report usually sending the report still happens from the master-node...

Robert H. said:
do you need more / other logs than mail.log? when I triggered the manual sending i only saw content in mail.log

Is there anything in the journal? (this contains the whole system's log) - just let `journalctl -f` run in one shell and try sending the report with pmgqm in another

EDIT: also paste any output from pmgqm

Robert H. · Jan 16, 2023

Code:

journalctl -f
Jan 16 13:05:50 mta01 postfix/smtpd[26147]: connect from localhost.localdomain[127.0.0.1]
Jan 16 13:05:50 mta01 pmgqm[27114]: smtp error - got: 555 5.5.4 Unsupported option: SMTPUTF8
Jan 16 13:05:50 mta01 postfix/smtpd[26147]: lost connection after MAIL from localhost.localdomain[127.0.0.1]
Jan 16 13:05:50 mta01 postfix/smtpd[26147]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=0/1 commands=1/2
Jan 16 13:05:50 mta01 pmgqm[27114]: smtp from: ERROR at /usr/share/perl5/PMG/Utils.pm line 275.

pmgqm does not have any output

that sounds for me we do have an error with SMTP UTF8 strange...

Stoiko Ivanov · Jan 16, 2023

Please share the output of `pmgversion -v` - there was an issue with the spam-reports, but that was fixed in the latest version

Do you have disabled smtputf8 in your postfix config in PMG?

Robert H. · Jan 16, 2023

Stoiko Ivanov said:
Do you have disabled smtputf8 in your postfix config in PMG?

Not that I'm aware of. Where would I do that?

Code:

pmgversion -v
proxmox-mailgateway: 7.2-1 (API: 7.2-2/fe97dfd3, running kernel: 5.15.74-1-pve)
pmg-api: 7.2-2
pmg-gui: 3.2-2
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-1-pve: 5.13.19-3
clamav-daemon: 0.103.7+dfsg-0+deb11u1
ifupdown: 0.8.36+pve2
libarchive-perl: 3.4.0-1
libjs-extjs: 7.0.0-1
libjs-framework7: 4.4.7-1
libproxmox-acme-perl: 1.4.2
libproxmox-acme-plugins: 1.4.2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-http-server-perl: 4.1-5
libxdgmime-perl: 1.0-1
lvm2: 2.03.11-2.1
pmg-docs: 7.2-1
pmg-i18n: 2.8-1
pmg-log-tracker: 2.3.2-1
postgresql-13: 13.9-0+deb11u1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-spamassassin: 3.4.6-5
proxmox-widget-toolkit: 3.5.3
pve-firmware: 3.5-6
pve-xtermjs: 4.16.0-1
zfsutils-linux: 2.1.6-pve1

Stoiko Ivanov · Jan 16, 2023

Robert H. said:
pmg-api: 7.2-2

yes - that's most likely the issue - the fix is included in pmg-api 7.2-3 - try upgrading your packages to the latest version and reboot

I hope this helps!

Robert H. · Jan 16, 2023

Code:

Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Your System is up-to-date

starting shell

well, according to the server there is no update?

Robert H. · Jan 16, 2023

Code:

apt-cache policy pmg-api
pmg-api:
  Installed: 7.2-2
  Candidate: 7.2-2
  Version table:
 *** 7.2-2 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
        100 /var/lib/dpkg/status
     7.1-11 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-10 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-9 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-8 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-7 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-4 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-3 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-2 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.1-1 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.0-8 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.0-7 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages
     7.0-6 500
        500 https://enterprise.proxmox.com/debian/pmg bullseye/pmg-enterprise amd64 Packages

Stoiko Ivanov · Jan 16, 2023

Robert H. said:
well, according to the server there is no update?

It seems the version with the fix has not yet made it to the pmg-enterprise repository (I assume you're using this repo)

I'd suggest to shortly enable the pmg-no-subscription repository (GUI->Adminstration->Repositories(on top)) and install pmg-api from there

jdsysadmin · Jan 17, 2023

Hello

I'm also facing this problem of not being able to send reports.
Also updates show no new updates.

Is there a way to update the pmg-api to 7.2-3?

Thank you

Stoiko Ivanov · Jan 17, 2023

jdsysadmin said:
Is there a way to update the pmg-api to 7.2-3?

Yes as said above - enable the pmg-no-subscription repository and install the upgrades from there.

jdsysadmin · Jan 17, 2023

I did not realised that it was the "pmg-no-subscription" repo.

Thank you, it worked.
Have a nice day

Netzblicker · Jan 25, 2023

Hm, I have a subscription, but 7.2.2 is the last for me, also when I update the repo. Why?

Stoiko Ivanov · Jan 25, 2023

Netzblicker said:
Hm, I have a subscription, but 7.2.2 is the last for me, also when I update the repo. Why?

please share the output of `apt update` and `apt full-upgrade`

jdsysadmin · Jan 25, 2023

You need to add the "pmg-no-subscription" repo.
That did it for me.
-> Administration
-> Repositories
-> Button "Add"
-> Select "No Subscription" from the dropdown

Netzblicker · Jan 25, 2023

root@filter:~# apt-get update
OK:1 http://security.debian.org/debian-security bullseye-security InRelease
OK:2 http://ftp.debian.org/debian bullseye InRelease
Holen:3 http://ftp.debian.org/debian bullseye-updates InRelease [44,1 kB]
OK:4 http://download.proxmox.com/debian/ceph-pacific bullseye InRelease
OK:5 http://download.proxmox.com/debian/pve bullseye InRelease
OK:6 https://enterprise.proxmox.com/debian/pmg bullseye InRelease
Es wurden 44,1 kB in 1 s geholt (37,1 kB/s).
Paketlisten werden gelesen… Fertig

and

root@filter:~# apt-get full-upgrade
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Paketaktualisierung (Upgrade) wird berechnet… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
bsdmainutils libbind9-161 libdns1104 libdns1110 libhavege1 libicu63 libirs161 libisc1100 libisc1105
libisccc161 libisccfg163 liblwres161 libmpdec2 libpython3.7-minimal libpython3.7-stdlib libreadline5
libreadline7 python3-asn1crypto python3.7 python3.7-minimal usb.ids
Verwenden Sie »apt autoremove«, um sie zu entfernen.
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

Netzblicker · Jan 25, 2023

jdsysadmin said:
You need to add the "pmg-no-subscription" repo.
That did it for me.
-> Administration
-> Repositories
-> Button "Add"
-> Select "No Subscription" from the dropdown

you are damned right - now I see the update:
pmg-api 7.2.2 to 7.2.3

Spam reports not sending

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Member

Proxmox Staff Member

Member

Member

Member