Re: dovecot cram-md5 setting break sending emails

[Dominic Raferd]

On 23/02/2017 09:06, Poliman - Serwis wrote: I also turned on verbose log in dovecot and below is output in mail.log: Feb 23 10:03:51 vps342401 postfix/smtps/smtpd[3640]: xsasl_dovecot_server_connect: auth reply: DONE Feb 23 10:03:51 vps342401 postfix/smtps/smtpd[3640]: xsasl_dovecot_server_mech_filter: skip mechanism: PLAIN Feb 23 10:03:51 vps342401 postfix/smtps/smtpd[3640]: xsasl_dovecot_server_mech_filter: skip mechanism: LOGIN Feb 23 10:03:51 vps342401 postfix/smtps/smtpd[3640]: fatal: no SASL authentication mechanisms Feb 23 10:03:52 vps342401 postfix/master[25124]: warning: process /usr/lib/postfix/smtpd pid 3640 exit status 1 Feb 23 10:03:52 vps342401 postfix/master[25124]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling Feb 23 10:04:12 vps342401 postfix/anvil[3328]: statistics: max connection rate 27/60s for (submission:54.175.125.239) at Feb 23 09:58:20 Feb 23 10:04:12 vps342401 postfix/anvil[3328]: statistics: max connection count 1 for (submission:54.175.125.239) at Feb 23 09:58:08 Feb 23 10:04:12 vps342401 postfix/anvil[3328]: statistics: max message rate 1/60s for (smtps:93.X.X.31) at Feb 23 10:00:37 Feb 23 10:04:12 vps342401 postfix/anvil[3328]: statistics: max cache size 3 at Feb 23 09:58:21 These seem to be from postfix, not from dovecot. You can get more info from dovecot by enabling debug_log_path = path/to/debug/log and by ensuring that the changes you've made to the configuration are actually seen by dovecot. The easiest way to verify what dovecot is actually using at runtime is the doveconf command, dovecot -a will show you these values. Are you using fail2ban? (suggestions cribbed from http://serverfault.com/questions/588391/how-to-get-doveconf-to-reload-its-config-or-read-from-etc-dovecot)