Also note that because of a change in how (upcoming) v2.0.8 checks if imap/pop3/lmtp has been started from command line, version_ignore=yes is effectively always enabled for them when older master process is running.

On Thu, 2010-11-18 at 19:48 +0000, interfaSys sàrl wrote:

I'll check ASAP. Thank you.

On 18/11/2010 19:03, Timo Sirainen wrote:

...

On Thu, 2010-11-11 at 17:30 +0000, interfaSys sàrl wrote:

...

Hello, When upgrading Dovecot, I get this: Dovecot version mismatch: Master is v2.0.6, imap-login is v2.0.7 (if you don't care, set version_ignore=yes)

This should not occur as version_ignore=yes is in dovecot.conf, at the top.

Should be fixed by http://hg.dovecot.org/dovecot-2.0/rev/656da7e0d6b9

On Thu, 2010-11-18 at 14:27 -0600, Mike Abbott wrote:

...

Also note that because of a change in how (upcoming) v2.0.8 checks if imap/pop3/lmtp has been started from command line, version_ignore=yes is effectively always enabled for them when older master process is running.

I don't understand this. Can you please elaborate? Thanks.

In <= v2.0.7 imap, pop3 and lmtp does getenv("GENERATION") at startup. If that's NULL, they assume that they're running standalone and don't do any version checks.

But this environment could already be set, because Java uses it also. So I changed >= v2.0.8 to do getenv("DOVECOT_CHILD_PROCESS") != NULL check instead.

Now the problem is that if you have v2.0.7 dovecot master running, it doesn't set DOVECOT_CHILD_PROCESS environment. Then if you upgrade imap executable to v2.0.8 it thinks that it's running standalone because that environment isn't set. It'll probably fail with:

Nov 18 20:40:57 imap: Error: Fatal: USER environment missing