Re: [Imap-uw] mbx and the necessity of ~/INBOX

> is it possible to move from mbox to mbx while keeping the old "mbox" > files (/var/mail/$username) _and_ let the users have their IMAP folders > in their home directory (/home/$username/...)? The format of a folder is the format of JUST that folder. A user can have folders of different formats w

Re: [Imap-uw] New messages ignored by imapd?

I can't imagine why anyone would use a signed value for this. Crazy that all three of these clients have the exact same bug, especially since the correct behavior is defined in the RFC. This is supposed to be fixed in the latest version of Thunderbird (2.0.0.9), and indeed I'm no longer g

Re: [Imap-uw] mbx and the necessity of ~/INBOX

Kaljio wrote: I have most (>95%) of the users incoming mail boxes in /var/mail/$username I believe the only way to keep using those files is to have them in unix format. Summed up I'd like to -convert from unix mbox files /var/mail/$username to mbx format -keep the files at /var/mail/$us

Re: [Imap-uw] mbx and the necessity of ~/INBOX

Kaljio wrote: -convert from unix mbox files /var/mail/$username to mbx format Careful with the MTA and other Unix utilities that might expect /var/mail/$username to be in unix format. If any of those programs tries to append a message to the mailbox you would end up with a mess. -keep the fi

Re: [Imap-uw] New messages ignored by imapd?

I believe I've narrowed down the problem further. Alpine using IMAP does show the missing messages, just like Pine locally. Horde IMP and Apple Mail correctly show the number of unread messages via a number beside the folder name, but when you click on the folder, the messages aren't ther

Re: [Imap-uw] mbx and the necessity of ~/INBOX

Thanks for your reply! I was a bit imprecise in the first mail. The problem is that I want to keep the new mbx files in /var/mail and uw-imap - for some reason - does not like that. > > is it possible to move from mbox to mbx while keeping the old "mbox" > > files (/var/mail/$username) _and_ let t

Re: [Imap-uw] mbx and the necessity of ~/INBOX

Jeroen van Aart wrote: Kaljio wrote: Hello, is it possible to move from mbox to mbx while keeping the old "mbox" files (/var/mail/$username) _and_ let the users have their IMAP folders in their home directory (/home/$username/...)? Yes, it's what I did. On debian as user $username: mailutil m

Re: [Imap-uw] mbx and the necessity of ~/INBOX

Kaljio wrote: Hello, is it possible to move from mbox to mbx while keeping the old "mbox" files (/var/mail/$username) _and_ let the users have their IMAP folders in their home directory (/home/$username/...)? Yes, it's what I did. On debian as user $username: mailutil move INBOX "#driver.mbx/I

[Imap-uw] mbx and the necessity of ~/INBOX

Hello, is it possible to move from mbox to mbx while keeping the old "mbox" files (/var/mail/$username) _and_ let the users have their IMAP folders in their home directory (/home/$username/...)? Our current uw-imap setup uses the old unix mbox file located in /var/mail/$username. User- and client

Re: [Imap-uw] New messages ignored by imapd?

What client are you using? When you say "it isn't showing up via IMAP...but [it does] appear in Pine", do you mean local Pine or Pine via IMAP? If local Pine...does it show up in Pine via IMAP? Try that if you haven't. If it does show up in Pine via IMAP, then the problem is likely to be i

[Imap-uw] New messages ignored by imapd?

I'm using the traditional UNIX mbox format, not maildir or mix. About a month ago, I noticed I had a folder full of spam that appeared to be missing several hundred messages. I played around with it, and concluded something in there was causing imapd to ignore a bunch of messages, even tho