I suspect this is a user agent issue, given that Evolution is flaky in so many areas. When I deliver mail to a subfolder/subbox (e.g. the -m option in the deliver command), and Evolution doesn't know of it, yet, creating it fails, and Evolution still can't get to it. Doing things the other way around (create it in Evolution first, then deliver to it) works fine. Seems to be silliness to me. Just wondered if any Dovecot aspects might be involved ... such as the fact that the case is different (e.g. "INBOX" in the filesystem, but "Inbox" in Evolution). -- sHiFt HaPpEnS!
On Tue, 2010-12-21 at 14:48 -0500, Phil Howard wrote:> I suspect this is a user agent issue, given that Evolution is flaky in > so many areas. When I deliver mail to a subfolder/subbox (e.g. the -m > option in the deliver command), and Evolution doesn't know of it, yet, > creating it fails, and Evolution still can't get to it. Doing thingsCreating the new mail folder is entirely on the IMAP server side. The MUA (Evolution in your stated case) is irrelevant. If the creation of the new folder fails, it is a server side problem. However, once a new folder has been created (server side, mind you), Evolution won't know about that folder until it is restarted. Probably the same with other MUAs, too. In the worst case, restarting Evo twice should show the new folder. (That is assuming you are not limiting your MUA to subscribed folders only, or, as IIRC is the default, deliver auto-subscribes the user to the just created folder.)> the other way around (create it in Evolution first, then deliver to > it) works fine. Seems to be silliness to me. Just wondered if any > Dovecot aspects might be involved ... such as the fact that the case > is different (e.g. "INBOX" in the filesystem, but "Inbox" in > Evolution).-- char *t="\10pse\0r\0dtu\0. at ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
Out of curiosity, are you using the "autosubscribe" feature of Dovecot LDA to automatically subscribe people who whatever new folder the Dovecot LDA automatically creates? It looks like this is the -s flag to LDA binary in 1.1.3+ or lda_mailbox_autosubscribe in 2.0+ (not sure exactly what point release...) I don't have a lot of experience with Evolution but I know Thunderbird can be difficult when it comes to new folders showing up on the server that it didn't create. The best you can do is make sure the client gets automatically subscribed to that new folder and hope that the client checks the list of subscribed folders (the LSUB IMAP command) eventually. I would hope that clicking "check/get new mail" would be enough to trigger that in most clients. On Tue, 21 Dec 2010 14:48:30 -0500, Phil Howard <ttiphil at gmail.com> wrote:> I suspect this is a user agent issue, given that Evolution is flaky > in > so many areas. When I deliver mail to a subfolder/subbox (e.g. the > -m > option in the deliver command), and Evolution doesn't know of it, > yet, > creating it fails, and Evolution still can't get to it. Doing things > the other way around (create it in Evolution first, then deliver to > it) works fine. Seems to be silliness to me. Just wondered if any > Dovecot aspects might be involved ... such as the fact that the case > is different (e.g. "INBOX" in the filesystem, but "Inbox" in > Evolution).