Re: invalid remote specification

Mark Crispin <[email protected]>
Newsgroups gmane.mail.imap.uw.c-client
Message-ID <[email protected]>
The most common cause of this problem is failure to do
 	#include "linkage.c"
early in the main() function of the application (and prior to any c-client 
library calls).

The use of linkage.c is mandatory.  Some programmers omit the linkage 
entirely; others attempt to do the linkage manually.  Either way, they 
come to grief.

If you are certain that you have included linkage.c in your main() 
function, then the only other cause is that the IMAP software was built 
without SSL.

Finally: in your example, neither the ":993", nor the "/imap", nor the 
"INBOX" are necessary although they won't hurt.  "/imap" is the default, 
":993" is implied by "/ssl" for IMAP, and "INBOX" is also the default. 
Hence
 	{imap.gmail.com/ssl}
is exactly equivalent to
 	{imap.gmail.com:993/imap/ssl}INBOX
but is much less typing.

On Wed, 18 Nov 2009, Mike T wrote:
> I am trying to write a simple test program for the c-client library based off 
> of mtest.c. When I am entering the mailbox string (eg. 
> {imap.gmail.com:993/imap/ssl}INBOX) I keep receiving an error saying "Can't 
> open mailbox <mailbox string>: invalid remote specification". What could be 
> the causes to thsi error?

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.