Loose end :

"Beartooth" <beartooth-iVX72re7JJ/[email protected]> 24 Jun 2006 15:29:04 -0500
Newsgroups gmane.org.infiniteink
Message-ID <[email protected]>
Here's a problem that arose during the long discussion on merging pines,
or roaming pine (a name I like much), or masterpine (which I also like) --
or whatever we're going to call the process and set-up of controlling
multiple email accounts from one IMAP login in one place. 

I just realized I lost track of it, so it's still my move (with apologies
to those coming into this in medias res)

Newsgroups:   comp.mail.pine
Date:         Tue, 20 Jun 2006 20:24:01 +0100

> Sur 2006-06-20, Beartooth skribis:
>>
>> --- [ Normally hidden configuration options ] ---
>>
>> VA         VA
>> bblx       bblx
>> ACFG       ACFG
>> ARTEMIS    ARTEMIS
>> VCDL       VCDL
>> Adel-inbox {mail.adelphia.net/pop3/u...
>> bbgA       {titan.lserv.com/novalidate-cer...
>> novalug    novalug
>> FM-inbox   {mail.messagingengine.com/s...


> Beartooth, the problem you are having with TAB not working in 
> your incoming-folders collection is because some of these, e.g., 
> VA, are now underspecified. To fix this, you need to edit them so 
> that they *explicitly* include the server specification. I.e., 
> you need to edit each of them so that they are in this form.

>     nickname  {server}foldername

> For example, instead of:

>     VA VA

> It needs to be:

>     VA {titan.lserv.com/novalidate-cert/user=karhunhammas}VA

> Since I am not sure of the syntax for lserv, please try this 
> first with only one, e.g., with VA. You will need to edit this in 
> the MSC (Main > Setup > Config) screen in the 'hidden 
> configuration options' section.

> My advice:

>    Do this for one incoming-folder, e.g., VA.

VA is a bad one to start with. It's my little virus-alert list, kept to
the utmost in low traffic : CERT warnings, and seldom much else. So I
tried it, under ssh to titan, on novalug, which wasn't working right
anyway. (I assume we're talking Pine's "[ Normally hidden configuration
options ]" since it says that above, and those lists in the
incoming-folders list near the top of MSC have a more complex form.)

>    Quit & Restart Pine.

Done.

>    See if it works.

Well, it said "Checking of folder novalug failed. Continue ?" -- which is
an improvement, since afaict it wasn't even trying before. So I told it Y,
whereupon it checked the FM-inbox among titan's IMAP incoming folders.
(There was nothing in that, either; it happens that, being unable to get
to novalug since an experiment of my own yesterday, I had just subscribed
my FM account to novalug. (No confirmation in the web interface yet,
either.))

>    If it does, do it for the others.

I'll try one more in case novalug is a messed-up case?

> If there are problems, we can revert to an old pinerc, thanks to 
> your remote-abook-history (which you should increase to 100 
> before doing this!)

I did do that on the 20th; it was just the main part I forgot. <sheepish
grin>

> Let us know how it goes. If anyone has any advice or suggestions, 
> please post!

> Note that you should be able to access all these folders via the 
> other folder collections so even though incoming-folders are not
> working at the moment, you should still be able to deal with all 
> your email.

That seems to be true of the others (and was of novalug till yesterday --
I had renamed the old novalug folders, made sure everything left
containing that name was empty, and deleted the empty folders) -- with a
problem I *think* I've seen the light on. When I tabbed out of an incoming
folder, it asked me whether to save the read messages into the FM-folder
collection -- without noticing the new command at the bottom to let me
tell it where else to save them. So I have a small wad of FM-folders that
need to have their contents moved and be deleted.

-- 
Beartooth Staffwright, Wordcrafty Squirreler
FC5; Pine 4.64, Pan 0.14.2.91; Privoxy 3.0.3; CXO 5.0.1
Dillo 0.8.5, Opera 9.0, Firefox 1.5, Galeon 2.0.1
Remember I have little idea what I am talking about.