Does anyone find it tricky setting up Pine to work with Cyrus-IMAP? I just set up pine-4.33 with cyrus-imapd-2.0.16. The folder/collections behavior is confusing. The inbox path was easy enough: I set it to "{imaphost/user=myuserid}inbox". At this point, Pine would show the inbox, but none of the other folders. So I tried to set up a folder collection with the imap host as the host and a path of "inbox.". At this point, the setup screen complained "mailbox already exists" and refuse to save. If I leave the path blank, Pine would not show the folder list (apart from INBOX). Ultimately, I had to quit Pine and edit .pinerc by hand, setting the line:
folder-collections="My Alias" {imaphost}inbox.[] Right now, Pine seems happy. But if I try to change to a different folder by hitting TAB to autocomplete the folder name, Pine appends a dot ("foldername."), and this fouls up the folder selection. Why is Pine interacting so strangely with Cyrus-IMAP? Pine has had IMAP support since 1992, and should be one of the most IMAP-savvy email clients out there. I have not seen any Pine/Cyrus howto that documents how to make the two play nicely together. Chris