• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

spamassassin ignores required hits, is scoring spam to low, MAPS not working

P

perler

Guest
hi,

system: debian 3.1, spamassassin 3.03

my whole spamassassin/MAPS config looks broken somehow:

1) although i changed alle hits_required entries in the psa db, table sa_conf to 5 the hits_required entry in mail headers stays at 7

2) definite spam mails are scored at around 2-3 - on my old server with a by hand spamassassin installation they've been well above 5. i had the rules_du_jour package installed - is this advisable/neccessary and how to do this best on a plesk server?

3) i entred sbl-xbl.spamhaus.org into the maps config but the testmails from spamhaus are getting thru.

as i see it, debian handles all these things a bit different then the stock RH? installs - so i'm interrested in reports from debian users especially if they have all these things working before i contact the plesk support,

PAT
 
Have you checked your logfiles? Does your maillog seem to be correct? No errors or suspect entries about SpamAssassin?

Is your inetd/xinetd configuration updated correct with the MAPS settings?
 
Originally posted by Whistler
Have you checked your logfiles? Does your maillog seem to be correct? No errors or suspect entries about SpamAssassin?
nothing unusual, spamassassin kicks in and scans the messages - but the score is to low for effective spamfiltering
Originally posted by Whistler

Is your inetd/xinetd configuration updated correct with the MAPS settings?
this is hard to answer for me because i can't really see where MAPS filtering should be in the chain (remeber it's a debian system, not RH). i have in /etc/inetd.conf:

smtp stream tcp nowait root /var/qmail/bin/tcp-env tcp-env /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

problem is, my old qmail installation (self made follwoing life with qmail) used tcpserver so i'm a bit lost how plesk is chaining the mail transfer process. any insights?

PAT
 
Back
Top