Re: [Patch] use glib for digest calculations (was: Re: Sv: Balsa release?)

[Jack <ostroffjh users sourceforge net>]

Hi Peter,

On 2017.01.03 22:49, Peter Bloomfield wrote:
> On 01/03/2017 08:02:48 PM Tue, Jack wrote:
> > On 2016.12.29 13:27, Albrecht Dreß wrote:
> > > Am 29.12.16 19:12 schrieb(en) Jack:

> > > > > openssl s_client -starttls imap -connect your.provider.com:143
> > > >
> > > > I get a timeout for yahoo, at&t, and gmail.  (AT&T email is  
> > > > actually run by Yahoo, although it's an att.net server.)  As far  
> > > > as I can tell, all three should support this.  (I mainly use POP3  
> > > > with balsa on my main desktop PC, but I use IMAP on my laptop,  
> > > > tablet, and phone.)  I'm using openssl 1.0.2j.  Is this likely a  
> > > > configuration issue on my part, or are there known problems with  
> > > > any of those providers?
> > >
> > > Maybe they don't support IMAP w/ STARTTLS over port 143, but only  
> > > IMAPS (port 993)?  I.e. you have to say
> > >
> > > openssl s_client -connect your.provider.com:993
> > >
> > > as to negotiate the ssl connection *before* starting the protocol.   
> > > At least for yahoo, this works:
> > You got the same result I did for yahoo.  inbound.att.net didn't  
> > respond at all.  imap.gmail.com gives a lengthy response, but  
> > doesn't respond to "0001 CAPABILITY" and I can't tell what they are  
> > expecting.  It looks like they are talking a different language,  
> > which doesn't surprise me much.
>
> With an IMAP connection to Gmail, I get this:
>
> IMAP S: * OK Gimap ready for requests from (address omitted)
> IMAP C: 1 CAPABILITY
> IMAP S: * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST  
> CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN  
> AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH
> 1 OK Thats all she wrote! k95mb720037192iod
>
> FWIW!

odd, not for me:
$openssl s_client -connect imap.gmail.com:993

[lots of output trimmed]

* OK Gimap ready for requests from (address omitted)
1 CAPABILITY

and no response at all to that.  just sits there until I kill it.  Note  
the OK was the last response from gmail, I typed the next line, then  
nothing.


Actually - I'm a bit surprised to see the XOAUTH as I thought gmail  
supported OAUTH2 not the original, although I don't claim to fully  
understand either of them.

Jack