dovecot warnings in the mail.log

Submitted by AllanIT on Sun, 12/27/2015 - 02:56

HI Jamie

Background: Some time ago I asked on the forum about the dovecot warnings in the mail.log file and Eric suggested to change them to what is suggested in the warnings. However I am asking for you to look at this issue because I have looked at it several times and they do not make sense to me. EG add auth_ prefix to all settings inside auth {} and remove the auth {} section completely????? What the ????.

Below are the warnings in my logfile. For every 1000 lines in the log files the warnings below represent 792 lines making it very hard to check the logs. Thanks in advance for looking at this issue.

Dec 27 11:44:11 myserver dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
Dec 27 11:44:11 myserver dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: protocol managesieve {} has been replaced by protocol sieve { }
Dec 27 11:44:11 myserver dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:884: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
Dec 27 11:44:11 myserver dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:922: passdb pam {} has been replaced by passdb { driver=pam }
Dec 27 11:44:11 myserver dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1002: userdb passwd {} has been replaced by userdb { driver=passwd }
Dec 27 11:44:11 myserver dovecot: doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1058: auth_user has been replaced by service auth { user }
Dec 27 11:44:11 myserver dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
Dec 27 11:44:11 myserver dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:716: protocol managesieve {} has been replaced by protocol sieve { }
Dec 27 11:44:11 myserver dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:884: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely
Dec 27 11:44:11 myserver dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:922: passdb pam {} has been replaced by passdb { driver=pam }
Dec 27 11:44:11 myserver dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1002: userdb passwd {} has been replaced by userdb { driver=passwd }
Dec 27 11:44:11 myserver dovecot: config: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1058: auth_user has been replaced by service auth { user }
Status: 
Active

Comments

Submitted by andreychek on Sun, 12/27/2015 - 09:15

Howdy -- was this server upgraded from an older Ubuntu version?

If so, it may just be related to having settings from the older Ubuntu version.

Those aren't things that Virtualmin adds though, that's just the standard Dovecot config that comes with Dovecot.

Is this for Virtualmin Pro, or Virtualmin GPL?

Submitted by AllanIT on Wed, 12/30/2015 - 18:28

HI Eric

< Howdy -- was this server upgraded from an older Ubuntu version?

Yes the server has been upgraded from an 12.04 to 14.04 Ubuntu.

< If so, it may just be related to having settings from the older Ubuntu version.

<Those aren't things that Virtualmin adds though, that's just the standard Dovecot config that comes with Dovecot.

Does that mean there are no changes to the dovecot config file and could I do what the warning says eg:get a new clean config file with: doveconf -n dovecot-new.conf

<Is this for Virtualmin Pro, or Virtualmin GPL?

GPL.

Submitted by andreychek on Wed, 12/30/2015 - 18:28

Hmm, I'm not sure what you mean by "dovecot-new.conf".

However, it's typical to see warnings like you're seeing from deprecated options.

Those aren't added by Virtualmin, but they are safe to ignore.

Or, if you want to get rid of them, you'd just need to review the referenced lines of your Dovecot config and either remove the old options, or convert them to the current ones.

Submitted by AllanIT on Wed, 12/30/2015 - 18:44

< Hmm, I'm not sure what you mean by "dovecot-new.conf".

Im not sure what that means either. It is in the warnings produced by dovecot as in the first post of this thread.

Submitted by andreychek on Wed, 12/30/2015 - 18:51

Ah, are you referring to this here:

Dec 27 11:44:11 myserver dovecot: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf

That's explaining how to generate a new config. You could do that as well, though if you go that route you'd have to port over any nonstandard changes from your old config to the new one.