[Pine-info] inbox not recognized

[Cornelius C. Noack]

On Sat, 28 Jan 2006, Chris Wilson wrote:


> Hi Patrick,

>

>>>  Thanks for the reply...  Apparently the host company went through my mail

>>> directory this morning and converted all my pervious mail to maildir

>>> format...  Though I still am a bit confused with how pine works with this

>>> format.

>

> According to Thorsten Glaser's post earlier today, there exists a version of

> Pine that can work with maildir files, but I was unaware of this until today.

> And since he says that he doesn't trust it, my answer would be that pine

> doesn't work (properly) with this format.

>

> The best way to access your mail now is probably by IMAP, rather than working

> with the filesystem. If Pine cannot see your inbox when connecting by IMAP,

> try another client, and if that doesn't work either, it seems likely that

> your host has not properly converted your mail folders.

>

>>>  Previously I had it so that at the end of every month, pine would chop up

>>> my read-messages and create a new file with the date..  So I had like:

>>> read-messages-sep-2005 and sent-mail-dec-2005...  Am I still able to do

>>> this with this maildir format?

>

> I'm not sure, but I think not, unless you have Pine download your mail by

> POP3 to your local machine, and create the files there.

>

>>>  originally I had this:

>>>  inbox-path={collinatorstudios.com:143/novalidate-cert/user=collins}inbox

>>>

>>>  and so now I tried changing it to:

>>>  inbox-path={collinatorstudios.com:143/novalidate-cert/user=collins}new

>>>

>>>  but when I run pine, I get "    [Folder does not exist, or must be

>>> subscribed to.]  " -- yet there is a "new" folder within ~/mail.

>

> This looks wrong. The directories "cur" and "new" are not the names of mail

> folders, but part of the internal structure used by the Maildir format. Your

> inbox is probably still called inbox, or if not, your new host should be able

> to tell you what it's called.

>

> Cheers, Chris.

>


I had some (similar?) problems accessing my INBOX after switching
to a new provider --- I am not at all sure these were the same as
yours; but for what it's worth, here is the PINE users' group help I got 
that solved my problem:

=======================

> Since your admin gave you 993 as the IMAP port, I guess your

> server is using IMAP via SSL. If this is so, then you could just

> drop the :993 from the server name (it's the default port) and

> add instead a "/ssl" :



> inbox-parh={mail.itp.uni-bremen.de/ssl/user=noack/novalidate-cert/debug}INBOX

=======================

In other words, you might try

inbox-path={collinatorstudios.com/ssl/novalidate-cert/user=collins}inbox

Trying doesn't cost anything.

ccn.
--

.................................................................

    Prof.Dr. Cornelius C. Noack          Phones:
    Inst. f. Theor. Physik FB 1       office   : +49 (421) 218-2427
    Universit"at Bremen               secretary: -2422
    Otto-Hahn-Allee                   Fax      : -4869
    D - 28334  Bremen                 home     : +49 (421) 34 22 36
                                                     Fax:  346 7872
    E-mail: noack at itp.uni-bremen.de   or  ccnoack at mailaps.org
    WWW-page: www.itp.uni-bremen.de/~noack
.................................................................