Larry Rosenman wrote:
> I think I can see why the IMAP complaint (changing levels of "directories"), > but.... * OK dbmail imap (protocol version 4r1) server 2.2 ready to run 1 login testuser1 test 1 OK LOGIN completed 2 create testbox 2 OK CREATE completed 3 rename testbox sub/sub1/sub2/testbox 3 NO new mailbox would invade mailbox structure 4 create sub/sub1/sub2 4 OK CREATE completed 5 rename testbox sub/sub1/sub2/testbox 5 OK RENAME completed So: you need to create the parent for the new target before you can rename to a deeper nested name. >>> Also, is there any particular reason the dbmail_mailboxes.name column >>> is limited to 100 characters? >> >> Not that I'm aware of. That was most likely an adhoc decision way >> back. >> It's also in the code; >> >> dbmailtypes.h:#define IMAP_MAX_MAILBOX_NAMELEN 100 > > I wonder if it should be possibly longer, or just a text field? (just > curious). It could even be a bytea field, but the codebase would have to be fixed to accomodate such a change. Presently, dbmail is highly US-ASCII centric. One of the goals for 2.4 is to make it more UTF-8 oriented. There are more candidates for conversion to BYTEA: dbmail_headervalues.headervalue dbmail_subjectfield.subjectfield dbmail_users.userid dbmail_users.passwd dbmail_mailboxes.name come to mind. Did I miss any? -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
