SpamAssassin errors being show

stickypt

New Member
Apr 26, 2023
3
0
1
Hello there,
Just looking around syslog and found these errors. What they mean?

Code:
Apr 26 11:50:04 mail pmg-smtp-filter[1558]: WARNING: async: query 38423/IN/NS/gmail.com completed, callback NS/gmail.com failed: ***  FATAL PROGRAM ERROR!!    Unknown instance method "mname"
***  which the program has attempted to call for the object:
***
gmail.com.    613    IN    NS    ns4.google.com.
***
***  THIS IS A BUG IN THE CALLING SOFTWARE, which incorrectly assumes
***  that the object would be of a particular type.  The type of an
***  object should be checked before calling any of its methods.
***
Net::DNS::RR::NS 1814 at /usr/share/perl5/Mail/SpamAssassin/Plugin/DNSEval.pm line 583.
    Mail::SpamAssassin::Plugin::DNSEval::complete_ns_lookup(Mail::SpamAssassin::Plugin::DNSEval=HASH(0x562e0f1522d0), Mail::SpamAssassin::PerMsgStatus=HASH(0x562e162e9048), HASH(0x562e17cbab58), Net::DNS::Packet=HASH(0x562e17cba870), "gmail.com") called at /usr/share/perl5/Mail/SpamAssassin/Plugin/DNSEval.pm line 559
    Mail::SpamAssassin::Plugin::DNSEval::__ANON__(HASH(0x562e17cbab58), Net::DNS::Packet=HASH(0x562e17cba870)) called at /usr/share/perl5/Mail/SpamAssassin/AsyncLoop.pm line 364
    eval {...} called at /usr/share/perl5/Mail/SpamAssassin/AsyncLoop.pm line 365
    Mail::SpamAssassin::AsyncLoop::__ANON__(Net::DNS::Packet=HASH(0x562e17cba870), "38423/IN/NS/gmail.com", 1682506204.30077) called at /usr/share/perl5/Mail/SpamAssassin/DnsResolver.pm line 873
    Mail::SpamAssassin::DnsResolver::poll_responses(Mail::SpamAssassin::DnsResolver=HASH(0x562e114a0d00), 1) called at /usr/share/perl5/Mail/SpamAssassin/DnsResolver.pm line 996
 
can you post the output of 'pmgversion -v' ?
 
Code:
proxmox-mailgateway: 7.3-1 (API: 7.3-3/a3d66da0, running kernel: 5.15.102-1-pve)
pmg-api: 7.3-3
pmg-gui: 3.3-2
pve-kernel-helper: 7.3-8
pve-kernel-5.15: 7.3-3
pve-kernel-5.15.102-1-pve: 5.15.102-1
clamav-daemon: 0.103.8+dfsg-0+deb11u1
ifupdown2: 3.1.0-1+pmx3
libarchive-perl: 3.4.0-1
libjs-extjs: 7.0.0-1
libjs-framework7: 4.4.7-1
libproxmox-acme-perl: 1.4.4
libproxmox-acme-plugins: 1.4.4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-4
libpve-http-server-perl: 4.2-1
libxdgmime-perl: 1.0-1
lvm2: 2.03.11-2.1
pmg-docs: 7.3-2
pmg-i18n: 2.12-1
pmg-log-tracker: 2.3.2-1
postgresql-13: 13.9-0+deb11u1
proxmox-mini-journalreader: 1.3-1
proxmox-spamassassin: 4.0.0-2
proxmox-widget-toolkit: 3.6.4
pve-firmware: 3.6-4
pve-xtermjs: 4.16.0-1
zfsutils-linux: 2.1.9-pve1
 
ok the versions look correct, how often do you see those errors? we have multiple systems here and did not encounter such errors ourselves, so it's not a general problem
do you have any special spamassassin config?
 
The only thing I did was installed Spamhaus DQS:

Code:
git clone https://github.com/spamhaus/spamassassin-dqs
cd spamassassin-dqs
sed -i -e 's/your_DQS_key/OMMITED/g' sh.cf
cp sh.cf /etc/mail/spamassassin
cp sh_scores.cf /etc/mail/spamassassin
reboot

But removed everything and the error keeps going on.
I think will reinstall everything and start again.... And try to see if the problem shows from the beginning.
 

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!