On Tue, 15 Jul 2003, Adrian Urquhart wrote:
>I've got it fired up, albeit with executables twice the size you mention
>above. I generally don't use ports ar they're often one or two versions
>behind the current, and often intall things where I don't expect them
>to.
I guess the compiler version may also play a role here, but I can't say
I've checked the binary size with different compilers. :/
>I did a reconfigure and set CXXGLAGS="-O2" but are there any other knobs
>I can turn?
Not that I know of..
>When using Pine as the client, I can only see the INBOX, and not any of
>the existing folders created by Courier (the same is true in KMail). How
>can I "upgrade" the folders to allow Binc to see them - is it Ok to just
>add them to the bincimap-subscribed file? Can I leave -uidvalidity and
>-cache missing? I need to do this programmatically, not helped by the
>system being 500 miles away...
You are safe to delete bincimap-uidvalidity and bincimap-cache at any
point, even when the server is running.
You can transform the subscription file from Courier to Binc to allow most
clients to see their subscribed folders[*], but Pine doesn't respect IMAP
subscriptions.
Pine doesn't FWIK support LIST, LSUB, SUBSCRIBE and UNSUBSCRIBE, so the
only way I know to add folders is to edit them in by going to
setup->config and enabling "hidden config", then adding folders to the
"incoming folders" section. The format is the same as that of INBOX.
Also, when Pine creates mailboxes, these are not added to the IMAP
subscription list. Still it's the reference IMAP client. (?)
Andy
[*] Conversion scripts like this are very interesting to the community
of this project. If you make any scripts, you're welcome to post
them to this list. :-) I'll add them to the contributions page.
--
Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg
Author of Binc IMAP | "It is better not to do something
| than to do it poorly."
