Folks,
I'm running into some issues with pine and dovecot. (dovecot is running mbox for now... plan to switch to maildir soon.) At first I thought it was a funky issue with the way I was using pine to access mailboxes. (I use rsh to invoke imap as pre-authenticated so when I switch to maildirs, I don't have to worry about pine being patched to support it.) But after switching over to using authenticated IMAP over port 143, it still had issues.
I'm getting messages like:
Junk in start of group Not an Address Junk at end of envelope Unknown Message property
Thus far, it seems to only occur in pine. (Squirrelmail and evolution appear to be fine) Is it the client? Is it dovecot? is it easily fixable? It feels like some sort of escaping issue or parsing issue or something. I just don't know enough about IMAP to determine exactly what it is.
I'm using dovecot v0.99.8, MAIL=mbox:%h/Mail/:INBOX=%h/.mailbox I've just converted off of wu-imap in hopes of someday migrating to maildirs on that box. (anyone know of a good mbox to maildir conversion tool? I used to have on that worked fine, but I've since found a ton that don't work well for me at all. I have about a gig of email to backup and convert)
d!
David E. Storey wrote:
Folks,
I'm running into some issues with pine and dovecot. (dovecot is running mbox for now... plan to switch to maildir soon.) At first I thought it was a funky issue with the way I was using pine to access mailboxes. (I use rsh to invoke imap as pre-authenticated so when I switch to maildirs, I don't have to worry about pine being patched to support it.) But after switching over to using authenticated IMAP over port 143, it still had issues.
I'm getting messages like:
Junk in start of group Not an Address Junk at end of envelope Unknown Message property
Thus far, it seems to only occur in pine. (Squirrelmail and evolution appear to be fine) Is it the client? Is it dovecot? is it easily fixable? It feels like some sort of escaping issue or parsing issue or something. I just don't know enough about IMAP to determine exactly what it is.
Same here, though the only thing I have observed is that when you get a message with just the e-mail address, i.e. no GCOS field, in the To: field, the address field in the message list is blank. Normally with UW IMAP and Pine reading the spools directly, it will just happily replace that field with just the e-mail address.
Minor thing, but thought I'd bring it up since we are on the topic of Pine and Dovecot since this issue only seems to affect Pine. Though in this case, I do not think that the mailstore format is the issue here. Since I also saw a headers section in the config file, it could be a peculiarity that could be fixed that way.
--Ian.
Ian R. Justman wrote:
Same here, though the only thing I have observed is that when you get a message with just the e-mail address, i.e. no GCOS field, in the To: field, the address field in the message list is blank. Normally with UW IMAP and Pine reading the spools directly, it will just happily replace that field with just the e-mail address.
Actually, my bad, the From: field gets this treatment, though the To: field gets affected when I'm sending something to a mailing list and the mailing list address is the only thing in the To: field on the message coming back.
--Ian.
On Sat, 2003-03-01 at 20:47, Ian R. Justman wrote:
Same here, though the only thing I have observed is that when you get a message with just the e-mail address, i.e. no GCOS field, in the To: field, the address field in the message list is blank. Normally with UW IMAP and Pine reading the spools directly, it will just happily replace that field with just the e-mail address.
Actually, my bad, the From: field gets this treatment, though the To: field gets affected when I'm sending something to a mailing list and the mailing list address is the only thing in the To: field on the message coming back.
I don't think this happens with 0.99.8 anymore since I changed Dovecot to return NIL instead of "" if the name doesn't exist. If you still see it with old mails that's probably because Dovecot has cached them into indexes - deleting them would fix it.
On Sat, 2003-03-01 at 20:10, David E. Storey wrote:
I'm getting messages like:
Junk in start of group Not an Address Junk at end of envelope Unknown Message property
Whops. Looks like I broke it pretty badly in 0.99.8. Several headers containing '"' and maybe '\' characters will break it. Maybe it's time for 0.99.9 earlier than I thought.
participants (3)
-
David E. Storey
-
Ian R. Justman
-
Timo Sirainen