Most of my IMAP access is achieved by 'ssh $mailhost exec dovecot --exec-mail imap'.
I'm testing Dovecot 2.0, and this doesn't seem to work any more — and I can't seem to work out how to make it work. The wiki page at http://wiki2.dovecot.org/Upgrading/2.0 has no mention of it.
I looked through the git history to find the commit that broke it and see if I could find the replacement that way, but it was the commit entitled 'Initial commit for v2.0 master rewrite.', and wasn't particularly edifying.
Once upon a time in the dim and distant past, I believe I used to run /usr/libexec/dovecot/imap directly. But that doesn't set the environment up correctly, so isn't the right way to do it... is it?
-- dwmw2
On 12.11.2010, at 1.47, David Woodhouse wrote:
Most of my IMAP access is achieved by 'ssh $mailhost exec dovecot --exec-mail imap'.
Just run imap binary.
I'm testing Dovecot 2.0, and this doesn't seem to work any more — and I can't seem to work out how to make it work. The wiki page at http://wiki2.dovecot.org/Upgrading/2.0 has no mention of it.
Added.
Once upon a time in the dim and distant past, I believe I used to run /usr/libexec/dovecot/imap directly. But that doesn't set the environment up correctly, so isn't the right way to do it... is it?
Nowadays it does.
On Fri, 2010-11-12 at 01:52 +0000, Timo Sirainen wrote:
Once upon a time in the dim and distant past, I believe I used to run /usr/libexec/dovecot/imap directly. But that doesn't set the environment up correctly, so isn't the right way to do it... is it?
Nowadays it does.
Ah, right.
If I create ~/Maildir/{cur,new,tmp} manually, then running /usr/libexec/dovecot/imap does actually work.
(I did have a ~/Maildir on this test machine, but it only included one mailing list folder which I'd been using as a test case for a QRESYNC bug a few months ago.)
Thanks.
-- dwmw2
participants (2)
-
David Woodhouse
-
Timo Sirainen