On Tue, Dec 18, 2012 at 11:36:17PM -0500, David J. Weller-Fahy wrote:
Sounds good, I'll test it once it's in the repository (although that may
not be tonight, as I need *some* sleep ;).
Changes pushed. Please file a bug, or reopen #3571 if you are
still having problems.
* Michael Elkins [2012-12-18 23:40 -0500]:
> I'm working on http://dev.mutt.org/trac/ticket/3571 which is probably
> affecting you as well. It seems like some TLS servers have problems with
> >TLSv1.0. Will commit shortly (just working on the corresponding GNUTLS
> support).
Sounds good, I'll t
On Tue, Dec 18, 2012 at 11:16:54PM -0500, David J. Weller-Fahy wrote:
* David J. Weller-Fahy [2012-12-18 22:53
-0500]:
However, I'm now getting interesting failures (intermittent) when
using the built-in SMTP capability. Mostly involving the following
failure:
#v+
SSL failed: error:1408F10B:
* David J. Weller-Fahy [2012-12-18 23:16
-0500]:
> Bisection complete. I show the following:
>
> #v+
> The first bad revision is:
> changeset: 6229:e6b271ed1d7f
> branch: HEAD
> user:Michael Elkins
> date:Mon Dec 17 10:39:46 2012 -0800
> files: configure.ac mutt_ss
* David J. Weller-Fahy [2012-12-18 22:53
-0500]:
> However, I'm now getting interesting failures (intermittent) when
> using the built-in SMTP capability. Mostly involving the following
> failure:
>
> #v+
> SSL failed: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
> #v-
>
[s
I built from f251d523ca5a and been running for a bit now and not seen any
obvious problems yet. If I do find any I'll raise a bug with details.
--Mike
Michael Elkins , 2012-12-18 13:52 -0800:
> FYI, I'd appreciate feedback on anyone who rolls forward to tip. I just
> pushed the following chan
* Michael Elkins [2012-12-18 17:02 -0500]:
> FYI, I'd appreciate feedback on anyone who rolls forward to tip. I just
> pushed the following change which affects the email header parsing
> significantly.
Having no problems here... as a matter of fact, I'd rolled back to
6227:ed06326ae8a8 to troub
FYI, I'd appreciate feedback on anyone who rolls forward to tip.
I just pushed the following change which affects the email header
parsing significantly.
changeset: 6235:f251d523ca5a
branch: HEAD
tag: tip
user:Michael Elkins
date:Tue Dec 18 13:50:20 2012 -0800
s
