On Thu, 12 Jun 2008, Joel Reicher wrote:
What was probably happening is that imapd was interpreting "~/INBOX" as
a custom mailbox name rather than the special name "INBOX", and so the
snarfing wasn't triggered.
Yes, this was indeed my problem. The special name INBOX looses its magic
behavior if prefixed by "~/". At least for uw-imapd, "INBOX" means by default
spool inbox AND non-spool home directory-based inboxes, as you already
mentioned. The imapd server recognizes them both, if present, and messages
are snarfed automagically. It is an easily overlooked subtlety, so it is
worth outlining it here, as it is maybe not obvious from the documentation.
I take it the snarfing is now happening since you fixed this?
It works like a charm, out of the box.
By the way, I'm pretty sure all you need is "{imap.server}" since "INBOX"
should be the default mailbox.
Indeed, default names work pretty well with uw-imapd. but it might not be true
for other IMAP servers. A somewhat more complex .pinerc file is prone to
mistakes and fixing it is a matter of trial and error, where client-side
idiosyncrasies add to IMAP server peculiarities. A little out of topic, I
found that having an uw-imap server listening on both ports 993 and 143 with
TLS negotiation enabled, I am able to access the mailboxes from a pine 4.64
client with both the {imap.server/tls} and {imap.server/ssl} configuration
options, while the remote address book is only accessible if prefixed with
{imap.server/ssl}. In alpine, {imap.server/tls} also works for the remote
address book.
Regards,
Marius
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
