• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

spamd

P

phrank

Guest
Hola,

spamd has the following as one of its startup options:

--virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin

I am facing problems because %d and %l have no content and due to this the virtual-config-dir resolves to /var/qmail/mainames///.spamassassin.

That leads to log entries like the follwing:

/var/log/warn:Dec 27 23:09:32 myhost spamd[14141]: mkdir /var/qmail/mailnames///.spamassassin: Permission denied at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin.pm line 1536

/var/log/warn:Dec 27 23:09:35 myhost spamd[14141]: locker: safe_lock: cannot create tmp lockfile /var/qmail/mailnames///.spamassassin/auto-whitelist.lock.myhost.mydomain.net.14141 for /var/qmail/mailnames///.spamassassin/auto-whitelist.lock: No such file or directory

/var/log/warn:Dec 27 23:09:35 myhost spamd[14141]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile

/var/qmail/mailnames///.spamassassin/auto-whitelist.lock.myhost.mydomain.net.14141 for /var/qmail/mailnames///.spamassassin/auto-whitelist.lock: No such file or directory

Actually I have no clue why they have no content? Any suggestions?

Saludo,

franco
 
Back
Top