Subject: /notls not being paid attention to?

From: Matt Ackeret <[email-masked]>
Date: Thu, 15 Apr 2004 15:32:10 -0700 (PDT)

I have tried both:
inbox-path                    = {mail.apple.com/notls}INBOX

and

inbox-path                    = {mail.apple.com/user=mattack/notls}INBOX

and I seem to get fewer SSL errors with the former.. Though I suspect that's
just what I'm noticing.

Anyway, in both cases, since I *am* still getting SSL errors, it seems
like the "/notls" is not actually being adhered to.

Is there any way I can confirm that pine is truly "seeing" the /notls and
adhering to it?

Basically, this error and the "auth warning" I get (which I know I can
comment out and may end up doing) are the two big impediments to using pine.

-- 
top-posting: It's just a bad idea.
-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Mark Crispin <[email-masked]>
Date: Tue, 20 Apr 2004 15:24:24 -0700 (Pacific Daylight Time)

> and I seem to get fewer SSL errors with the former.. Though I suspect that's

These two inbox-path setting are identical, unless the logged-in user is 
something other than "mattack".  The only thing that "/user=" does is set 
the userid for IMAP login (which otherwise default to the logged-in 
userid).

> like the "/notls" is not actually being adhered to.

What, precisely, are these "SSL errors" that you are getting?

> Is there any way I can confirm that pine is truly "seeing" the /notls and

I can confirm that if you use /notls Pine will not negotiate TLS with the 
IMAP server.

> comment out and may end up doing) are the two big impediments to using pine.

What, precisely, is the "auth warning" that you are refer to?

If this is the "SECURITY PROBLEM: insecure server advertised AUTH=PLAIN" 
warning, then I can assure you that you are *not* using SSL or TLS. 
What's more, every time that you log in to the server any hacker can 
easily steal your password.  It is not a good idea to comment out that 
warning.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

---

From: Matt Ackeret <[email-masked]>
Date: Tue, 20 Apr 2004 17:08:10 -0700 (PDT)

>What, precisely, are these "SSL errors" that you are getting?

When trying to move to other mailboxes, or trying to compose a new message
when there is a postponed message (in which mail itself is "moving to other
mailboxes" AFAIK), I get:

          [SSL/TLS failure for mail.apple.com: SSL negotiation failed]

*EVEN WITH* the /notls at the end of my inbox-path.  But after living with
the first setting above for several days, the SSL errors are much much
less frequent.  I still get one near the start of my session, but not
very often, like I do with the second form.  (But again, to be clear, I
should not get ANY with either form.. right?)

I presume the first instance of that same warning is when I get this:

There was an SSL/TLS failure for the server

                                mail.apple.com

The reason for the failure was

                            SSL negotiation failed
...and so on..

>I can confirm that if you use /notls Pine will not negotiate TLS with the

Then why am I getting the SSL failures?

>easily steal your password.  It is not a good idea to comment out that

Then these seem to be at odds.  I am getting the SSL *AND* SECURITY PROBLEM
warnings very often.

The mail server is behind a firewall.  Is there some way I can get these
AUTH=PLAIN warnings to stop happening then?  Obviously I can't change the
company's mail server.

Thanks for your reply though.. I have sent various questions/rants about these
two problems several times, and this is the first time I've gotten a good
reply (others have just said they comment out the latter warning!)

---

From: Steve Hubert <[email-masked]>
Date: Fri, 23 Apr 2004 08:59:57 -0700 (PDT)

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.

Steve