• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Where to change plesk_saslauthd log level?

Baxil

New Pleskian
Plesk 12.0.18 Update #70, Ubuntu 14.04.3 LTS.

Our postfix mail log file is filled with millions of lines like the following:

Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: activity on 1 channel(s)
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: new client (fd=10) registered
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: main cycle iteration
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: activity on 1 channel(s)
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: some read activity on client 10
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 2)=2
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=0]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 7)=7
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=1]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 2)=2
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=2]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 8)=8
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=3]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 2)=2
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=4]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 4)=4
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=5]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 2)=2
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=6]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: read(10, &buf, 15)=15
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: processing client data chunk [state=7]
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: failed mail authenticatication attempt for user 'xxxxxxxxxxxxxxx' (password len=9)
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: main cycle iteration
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: activity on 1 channel(s)
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: some write activity on client 10
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: attempt to write(10, &buf, 4)
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: client 10 processed
Oct 28 17:00:42 cloud8 plesk_saslauthd[17698]: main cycle iteration
Oct 28 17:00:42 cloud8 postfix/smtpd[17706]: warning: unknown[x.x.x.x]: SASL LOGIN authentication failed: authentication failure​

This is causing the log file to grow to unmanageable sizes.

I have tried decreasing the log_level in /etc/postfix/sasl/smtpd.conf from 4 to 1 with no change.
http://kb.odin.com/en/113866 suggests changing it at
/usr/lib64/sasl2/smtpd.conf but that file does not exist (nor in /usr/lib/sasl2).
http://kb.odin.com/en/125625 suggests adding "sql_verbose: no", but that has no effect either.
In both cases I reloaded postfix after the changes.

Where is the log level for plesk_saslauthd set, and what log level removes all of the debugging information except for the "failed mail authentication" line?
 
Back
Top