The initial problem I was seeing after upgrade from 2.0beta5 to
2.0beta6 was error messages from my Android phone K9 client that
dovecot was reporting -1 messages in various mailboxes. These
mailboxes do have the special "Mail System Internal Data" message in
them.
In trying to get more information for debugging, I tried toenable
rawlog using the same configuration I used successfully with 2.0beta5,
namely:
service imap {
executable = imap imap-postlogin
}
service imap-postlogin {
executable = script rawlog
unix_listener imap-postlogin {
}
}
(full dovecot -n below), but instead of successful rawlog writes, I got
the following log messages:
Jun 16 19:46:36 sbh16 dovecot: script: Fatal: Client not compatible
with this binary (connecting to wrong socket?)
Jun 16 19:46:36 sbh16 dovecot: imap: Error:
fd_read(/usr/local/var/run/dovecot/imap-postlogin) failed: disconnected
So the first question is how do I configure rawlog for 2.0beta6?
And the next question is why the "-1 messages".
Here's dovecot -n
# dovecot -n
# 2.0.beta6: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final)
auth_mechanisms = plain apop login
auth_worker_max_count = 5
mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u
mail_privileged_group = mail
mbox_write_locks = fcntl dotlock
passdb {
args = /usr/local/etc/dovecot.passwd
driver = passwd-file
}
passdb {
driver = pam
}
protocols = imap pop3
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service imap-postlogin {
executable = script rawlog
}
service imap {
executable = imap imap-postlogin
}
ssl_cert = </etc/postfix/sbh16-cert.pem
ssl_key = </etc/postfix/sbh16-key.pem
userdb {
driver = passwd
}
protocol imap {
mail_max_userip_connections = 30
}
--
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
On 06/17/2010 05:36 AM Mark Sapiro wrote:> So the first question is how do I configure rawlog for 2.0beta6?Sorry for stripping all the stuff, and not digging deeper into it. There were two changes between beta5 and beta6: * http://hg.dovecot.org/dovecot-2.0/rev/addb2c6c1dfb * http://hg.dovecot.org/dovecot-2.0/rev/19c661891964 Also mentioned in the beta releae announcement: * http://dovecot.org/list/dovecot-news/2010-June/000156.html How to configure post-login scripts: * http://wiki2.dovecot.org/PostLoginScripting Regards, Pascal -- The trapper recommends today: 5e1f1e55.1016805 at localdomain.org
On 06/17/2010 05:36 AM Mark Sapiro wrote:> So the first question is how do I configure rawlog for 2.0beta6?Pascal Volk wrote:> On 06/17/2010 05:36 AM Mark Sapiro wrote: >> So the first question is how do I configure rawlog for 2.0beta6? > > Also mentioned in the beta releae announcement: > * http://dovecot.org/list/dovecot-news/2010-June/000156.html > > How to configure post-login scripts: > * http://wiki2.dovecot.org/PostLoginScriptingThank you. That solves it. Sorry for not reading the beta6 announcement more carefully. -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:> The initial problem I was seeing after upgrade from 2.0beta5 to > 2.0beta6 was error messages from my Android phone K9 client that > dovecot was reporting -1 messages in various mailboxes. These > mailboxes do have the special "Mail System Internal Data" message in > them.Just to follow up on this original issue, it appears the client sends an "examine" for the folder and gets back a perfectly appropriate response including 0 EXISTS 0 RECENT and then proceeds to log an error about -1 Messages. Thus, this appears to be strictly a client issue, possibly caused by a client software update about the same time as the dovecot update. -- Mark Sapiro <mark at msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan