• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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