Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
On 18.2.2010, at 21.31, Wilko Bulte wrote: >> Mutt 1.5.20 (2009-06-14) does NOT work with first.initial.last mboxes > > raw logging gives me: > > Oa0003 CAPABILITY > a0004 LIST "" "" > a0005 STATUS "mail/postponed" (MESSAGES) > a0006 SELECT "INBOX" > a0007 FETCH 1:41 (UID FLAGS INTERNALDATE RFC822.SIZE BODY.PEEK[HEADER.FIELDS > (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPT > ION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)]) > a0008 CLOSE > a0009 STATUS "mail/postponed" (MESSAGES) > a0010 SELECT "mail/foo/bar/baz" > a0011 LOGOUT > > If I understand this correctly the newer mutt version is explicitely asking > for a / seperated hierarchical mailbox? Right. Looks like a bug, or possibly a wrongly cached separator.
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
Quoting Wilko Bulte, who wrote on Thu, Feb 18, 2010 at 08:14:55PM +0100 .. > Quoting Wilko Bulte, who wrote on Thu, Feb 18, 2010 at 05:53:10PM +0100 .. > > Quoting Timo Sirainen, who wrote on Thu, Feb 18, 2010 at 05:26:54PM +0200 .. > > > On Mon, 2010-02-15 at 19:13 +0100, Wilko Bulte wrote: > > > > > > - On my new system I have dovecot v 1.2.8 which refuses to handle > > > > > > these > > > > > > dot-seperated files. I get the somewhat familiar > > > > > > "Mailbox doesn't allow inferior mailboxes". > > > > > > > > > I have attached the dovecot -n from my dovecot 1.2.8 which does not > > > > want to > > > > accept firstname.initial.lastname. This is the dovecot128.conf file. > > > > > > I don't see anything obviously wrong. Try talking IMAP protocol > > > directly, maybe your client is doing something wrong. > > > > > > http://wiki.dovecot.org/TestInstallation > > > > > > After login try something like: > > > > > > a create foo.bar.baz > > > b select foo.bar.baz > > > > > > If that succeeds, it's probably client issue. Recreating the account > > > > Looks like this is working just fine: > > > > a login wb foo > > a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT > > SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE > > CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC > > ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in > > a create foo.bar.baz > > a OK Create completed. > > b select foo.bar.baz > > * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) > > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags > > permitted. > > * 0 EXISTS > > * 0 RECENT > > * OK [UIDVALIDITY 1266511425] UIDs valid > > * OK [UIDNEXT 1] Predicted next UID > > * OK [HIGHESTMODSEQ 1] Highest > > b OK [READ-WRITE] Select completed. > > > > as it resulted in the creation of foo.bar.baz like so: > > > > -rw--- 1 wb wb 0 Feb 18 17:43 foo.bar.baz > > > > Hm... fascinating.. > > > > I'll investigate further, thanks for your kind help sofar! > > While talking to the same dovecot 1.2.8 server: > > Mutt 1.5.18 (2008-05-17) works OK with first.initial.last mboxes raw logging gives me: a0003 CAPABILITY a0004 LIST "" "" a0005 STATUS "postponed" (MESSAGES) a0006 SELECT "INBOX" a0007 FETCH 1:41 (UID FLAGS INTERNALDATE RFC822.SIZE BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPT ION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)]) a0008 CLOSE a0009 STATUS "postponed" (MESSAGES) a0010 SELECT "foo.bar.baz" a0011 FETCH 1:1 (UID FLAGS INTERNALDATE RFC822.SIZE BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPTI ON IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)]) a0012 CLOSE a0013 LOGOUT > and > > Mutt 1.5.20 (2009-06-14) does NOT work with first.initial.last mboxes raw logging gives me: Oa0003 CAPABILITY a0004 LIST "" "" a0005 STATUS "mail/postponed" (MESSAGES) a0006 SELECT "INBOX" a0007 FETCH 1:41 (UID FLAGS INTERNALDATE RFC822.SIZE BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE CONTENT-DESCRIPT ION IN-REPLY-TO REPLY-TO LINES LIST-POST X-LABEL)]) a0008 CLOSE a0009 STATUS "mail/postponed" (MESSAGES) a0010 SELECT "mail/foo/bar/baz" a0011 LOGOUT If I understand this correctly the newer mutt version is explicitely asking for a / seperated hierarchical mailbox? thanks, Wilko
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
Quoting Wilko Bulte, who wrote on Thu, Feb 18, 2010 at 05:53:10PM +0100 .. > Quoting Timo Sirainen, who wrote on Thu, Feb 18, 2010 at 05:26:54PM +0200 .. > > On Mon, 2010-02-15 at 19:13 +0100, Wilko Bulte wrote: > > > > > - On my new system I have dovecot v 1.2.8 which refuses to handle > > > > > these > > > > > dot-seperated files. I get the somewhat familiar > > > > > "Mailbox doesn't allow inferior mailboxes". > > > > > > > I have attached the dovecot -n from my dovecot 1.2.8 which does not want > > > to > > > accept firstname.initial.lastname. This is the dovecot128.conf file. > > > > I don't see anything obviously wrong. Try talking IMAP protocol > > directly, maybe your client is doing something wrong. > > > > http://wiki.dovecot.org/TestInstallation > > > > After login try something like: > > > > a create foo.bar.baz > > b select foo.bar.baz > > > > If that succeeds, it's probably client issue. Recreating the account > > Looks like this is working just fine: > > a login wb foo > a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT > SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE > CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC > ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in > a create foo.bar.baz > a OK Create completed. > b select foo.bar.baz > * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags > permitted. > * 0 EXISTS > * 0 RECENT > * OK [UIDVALIDITY 1266511425] UIDs valid > * OK [UIDNEXT 1] Predicted next UID > * OK [HIGHESTMODSEQ 1] Highest > b OK [READ-WRITE] Select completed. > > as it resulted in the creation of foo.bar.baz like so: > > -rw--- 1 wb wb 0 Feb 18 17:43 foo.bar.baz > > Hm... fascinating.. > > I'll investigate further, thanks for your kind help sofar! While talking to the same dovecot 1.2.8 server: Mutt 1.5.18 (2008-05-17) works OK with first.initial.last mboxes and Mutt 1.5.20 (2009-06-14) does NOT work with first.initial.last mboxes So it looks like I was totally offtrack in assuming dovecot was at fault. My apologies. I'll see if I can find out more Wilko
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
Quoting Timo Sirainen, who wrote on Thu, Feb 18, 2010 at 05:26:54PM +0200 .. > On Mon, 2010-02-15 at 19:13 +0100, Wilko Bulte wrote: > > > > - On my new system I have dovecot v 1.2.8 which refuses to handle these > > > > dot-seperated files. I get the somewhat familiar > > > > "Mailbox doesn't allow inferior mailboxes". > > > > > I have attached the dovecot -n from my dovecot 1.2.8 which does not want to > > accept firstname.initial.lastname. This is the dovecot128.conf file. > > I don't see anything obviously wrong. Try talking IMAP protocol > directly, maybe your client is doing something wrong. > > http://wiki.dovecot.org/TestInstallation > > After login try something like: > > a create foo.bar.baz > b select foo.bar.baz > > If that succeeds, it's probably client issue. Recreating the account Looks like this is working just fine: a login wb foo a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in a create foo.bar.baz a OK Create completed. b select foo.bar.baz * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1266511425] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest b OK [READ-WRITE] Select completed. as it resulted in the creation of foo.bar.baz like so: -rw--- 1 wb wb 0 Feb 18 17:43 foo.bar.baz Hm... fascinating.. I'll investigate further, thanks for your kind help sofar! Wilko
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
On Mon, 2010-02-15 at 19:13 +0100, Wilko Bulte wrote: > > > - On my new system I have dovecot v 1.2.8 which refuses to handle these > > > dot-seperated files. I get the somewhat familiar > > > "Mailbox doesn't allow inferior mailboxes". > > > I have attached the dovecot -n from my dovecot 1.2.8 which does not want to > accept firstname.initial.lastname. This is the dovecot128.conf file. I don't see anything obviously wrong. Try talking IMAP protocol directly, maybe your client is doing something wrong. http://wiki.dovecot.org/TestInstallation After login try something like: a create foo.bar.baz b select foo.bar.baz If that succeeds, it's probably client issue. Recreating the account might help. Or look at what the actual IMAP traffic is that it sends to Dovecot (http://wiki.dovecot.org/Debugging/Rawlog). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
Quoting Timo Sirainen, who wrote on Mon, Feb 15, 2010 at 03:23:09PM +0200 .. > On 10.2.2010, at 21.36, Wilko Bulte wrote: Hello Timo, > > - On my new system I have dovecot v 1.2.8 which refuses to handle these > > dot-seperated files. I get the somewhat familiar > > "Mailbox doesn't allow inferior mailboxes". > > mbox hierarchy separator is typically '/'. The above error message sounds > like you've changed the separator to be '.'. Is that intentional? I have attached the dovecot -n from my dovecot 1.2.8 which does not want to accept firstname.initial.lastname. This is the dovecot128.conf file. I have also attached the dovecot -n from my dovecot 1.1.7 (running on another system) which works OK with firstname.initial.lastname Both versions work OK as long as there are no . in the name of the mbox file to be created/written. Only 1.1.7 works with . in the filename of the mbox file. > > On a not-previously-existing mbox dovecot 1.2.8 produces the directory > > hierarchy thing: firstname -> initial -> lastname > > You mean this is also how it was in 1.1.7?.. If so, it probably worked back > then only because of lack of error detection. No, on 1.1.7 I never used/saw firstname -> inital -> lastname inboxes. I only saw firstname.initial.lastname mbox files, no directory hierarchy was created. Appreciate your insight! Thanks! Wilko # 1.1.7: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-STABLE i386 protocols: imaps imap ssl_key_file: /etc/ssl/private/dovecot.prkey ssl_parameters_regenerate: 10 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 2 login_max_processes_count: 3 max_mail_processes: 32 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_process_size: 64 imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: passdb: driver: pam userdb: driver: passwd # 1.2.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.0-STABLE amd64 protocols: imaps imap ssl_cert_file: /etc/ssl/private/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.prkey login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 2 login_max_processes_count: 3 max_mail_processes: 32 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_location: mbox:%h/mail:INBOX=/var/mail/%u mail_process_size: 64 imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmas...@example.com sendmail_path: /usr/sbin/sendmail auth default: passdb: driver: pam userdb: driver: passwd
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
On 10.2.2010, at 21.36, Wilko Bulte wrote: > - On my new system I have dovecot v 1.2.8 which refuses to handle these > dot-seperated files. I get the somewhat familiar > "Mailbox doesn't allow inferior mailboxes". mbox hierarchy separator is typically '/'. The above error message sounds like you've changed the separator to be '.'. Is that intentional? > On a not-previously-existing mbox dovecot 1.2.8 produces the directory > hierarchy thing: firstname -> initial -> lastname You mean this is also how it was in 1.1.7?.. If so, it probably worked back then only because of lack of error detection.
Re: [Dovecot] dovecot and firstname.initial.lastname mbox format archive
Quoting Wilko Bulte, who wrote on Wed, Feb 10, 2010 at 08:36:33PM +0100 .. > hi > > Today I have been in a puzzling fight with 2 dovecot versions that I would > like to ask some comments on. > > The situation is this: > > - I have a considerable mail archive in mbox format (yes, I know, but that > is what I have..). > - My mail reader is mutt 1.5.20 by the way. > - Some of these mbox files have names like firstname.initial.lastname > Note the . seperating the parts of the email-ers name. > - On my old system I have dovecot v 1.1.7 which has always worked flawless > - On my new system I have dovecot v 1.2.8 which refuses to handle these > dot-seperated files. I get the somewhat familiar >"Mailbox doesn't allow inferior mailboxes". > On a not-previously-existing mbox dovecot 1.2.8 produces the directory > hierarchy thing: firstname -> initial -> lastname > - I am using the same dovecot.conf on v.1.1.7 and v.1.2.8 > > Can anyone tell me if v1.2.8 no longer is able to do what v1.1.7 did? And > what I dearly would like to get working :-( And if it can, what should I > put in dovecot.conf to make that happen? Really nobody who has any idea? I admit, my Googling did not help either but still :-) I would have imagined someone else on this list might have encountered the issue? Wilko