Subject: Re: /notls not being paid attention to?

From: Matt Ackeret <[email-masked]>
Date: Wed, 2 Jun 2004 18:30:33 -0700 (PDT)

On Fri, 23 Apr 2004, Steve Hubert wrote:
> If you run pine with "-d verbose=9,imap=4" you may be able to look at the debug
> file and figure out the where and why of the message.

I have a debug file when this happened, but what should I look for?

This looks relevant, I think:

IMAP DEBUG 18:25:54 6/2: 00000000 CAPABILITY
IMAP DEBUG 18:25:54 6/2: * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=PLAIN STARTTLS
IMAP DEBUG 18:25:54 6/2: 00000000 OK CAPABILITY completed
imap_cmd({mail.apple.com}sent-mail, STARTTLS, 0x0)
IMAP DEBUG 18:25:54 6/2: 00000001 STARTTLS
IMAP DEBUG 18:25:54 6/2: 00000001 OK STARTTLS completed
sslfailure: host=mail.apple.com reason=SSL negotiation failed

Here's my current config:
inbox-path                     = {mail.apple.com/user=mattack/notls}INBOX       

So unless there's some user error I'm missing, it seems to not be working
as expected.

---

From: Matt Ackeret <[email-masked]>
Date: Wed, 2 Jun 2004 18:37:33 -0700 (PDT)

>sslfailure: host=mail.apple.com reason=SSL negotiation failed

Though also, does this mean that my IMAP server is saying the wrong thing?
If it's saying STARTTLS but STARTTLS is not actually working.. that sounds 
bad..  (but it should still be overridden by my /notls thing)

---

From: Steve Hubert <[email-masked]>
Date: Thu, 3 Jun 2004 08:52:45 -0700 (PDT)

The first thing I'd want to look at is the whole debug file, if possible, 
to make sure that this particular STARTTLS happens for your inbox. It is 
possible that some other mailbox is being opened. Probably not, but that's 
the first thing I'd look for.

Steve

---

From: Matt Ackeret <[email-masked]>
Date: Thu, 3 Jun 2004 11:39:08 -0700 (PDT)

On Thu, 3 Jun 2004, Steve Hubert wrote:
> The first thing I'd want to look at is the whole debug file, if possible, to
> make sure that this particular STARTTLS happens for your inbox. It is possible
> that some other mailbox is being opened. Probably not, but that's the first
> thing I'd look for.

Is there anything "secret" in the debug file? 

Also, I had to run for quite a while before getting this to happen.
My biggest .pine-debug file, which is I think the one this happened on,
is 9 megs.

Is there any way I could get the debug output to just spew out issues relevant
to this problem?

Basically, I'll do whatever I can to provide more info, this issue drives
me nuts.

I do think that "some other mailbox is being opened", because it happens
infrequently, but most reproducibly, when I'm trying to compose a message when
there's already a postponed message -- so it can't open the postponed-msgs
folder.  (I think I explained this in an original mail way back.)

---

From: Steve Hubert <[email-masked]>
Date: Thu, 3 Jun 2004 11:58:19 -0700 (PDT)

> Is there anything "secret" in the debug file?

I don't think so, but some people consider their address secret, so it is 
in the eye of the beholder.

> Is there any way I could get the debug output to just spew out issues relevant

Nope.

> folder.  (I think I explained this in an original mail way back.)

You can try to fix it by making sure that /notls appears everywhere it 
needs to appear in the config file. Most places where there is a hostname 
will have to have /notls, or at least the ones that go to the defective 
host.

For example, if you have any collections defined on an IMAP server, go to 
the Setup Collections screen and add the /notls to the server name there. 
If you have a fully-qualified mailbox name for postponed-folder add the 
/notls there, too. If the smtp server gives you errors, you need it there, 
too. If not, you don't want it because it removes the encryption. My guess 
would be that you have a collection and the server name in that collection 
does not have /notls after it.

Steve

---

From: Matt Ackeret <[email-masked]>
Date: Thu, 3 Jun 2004 18:14:20 -0700 (PDT)

On Thu, 3 Jun 2004, Steve Hubert wrote:
> My guess would be that you have a collection and the server name in that
> collection does not have /notls after it.

Ok, I do have a collection that was just called "Mail on mail.apple.com" 
with the server.

I added /notls to that one.  I'm not actually using collections as far
as I remember, so maybe I should just delete it.

But I'll live with this for a while and see if that error goes away..
if not, I'll check around if I have the server name in other places in
my config file.

Thanks..

If this _does_ fix it, then that just leads to another admittedly wide-
ranging enhancement request -- if pine had noticed I added /notls to
one instance of "mail.apple.com", it would have made sense for it to
mention that I had other instances of the server WITHOUT /notls.

Even if it couldn't/wouldn't automatically change all of them, if it just
said "you should update the server in the collectionList <and other
locations as appropriate>", that would have clued me in.

---

From: Matt Ackeret <[email-masked]>
Date: Mon, 14 Jun 2004 18:35:29 -0700 (PDT)

>if not, I'll check around if I have the server name in other places in

I now haven't had the SSL error in a while.

>locations as appropriate>", that would have clued me in.

This still applies.  As friendly as pine usually is, server setup and
making sure the various settings are consistent among the different places
one can enter is is one of the things that's not very intuitive in pine.

(in general, pine is my example that a text-based app can be JUST as 
simple/easy to use as any GUI program.. in fact, out of the box, I wouldn't
use pine..  It's only because I can change the editor and configure other
stuff that makes it great to me.)

Now the only lingering warning I get is that AUTH=PLAIN one.  If I can
quiet that one without commenting out a line in the source & recompiling,
great.