Re: toward a 1.5.22 release

2012-12-18 Thread Phil Pennock
On 2012-12-18 at 14:06 -0800, Michael Elkins wrote: > My current plan is to ensure that all the bugfixes that are > applied to the mutt packages in various OS distributions have been > rolled into the hg repo, then push out a 1.5.22 release. > > I've found the patches from some distros here: >

Re: Possible bug in 6229 (was: heads up regarding tip)

2012-12-18 Thread Michael Elkins
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.

Re: [Mutt] #3571: User should be able to disable TLSv1.1 and TLSv1.2

2012-12-18 Thread Mutt
#3571: User should be able to disable TLSv1.1 and TLSv1.2 -+-- Reporter: hncaldwell | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: 1.6 Component: m

Re: [Mutt] #3571: User should be able to disable TLSv1.1 and TLSv1.2

2012-12-18 Thread Mutt
#3571: User should be able to disable TLSv1.1 and TLSv1.2 +--- Reporter: hncaldwell | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: 1.6 Component: mutt

Re: [Mutt] #3571: User should be able to disable TLSv1.1 and TLSv1.2

2012-12-18 Thread Mutt
#3571: User should be able to disable TLSv1.1 and TLSv1.2 +--- Reporter: hncaldwell | Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: 1.6 Component: mutt

Re: Possible bug in 6229 (was: heads up regarding tip)

2012-12-18 Thread David J. Weller-Fahy
* 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

Re: Possible bug in 6229 (was: heads up regarding tip)

2012-12-18 Thread Michael Elkins
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:

Re: Possible bug in 6229 (was: heads up regarding tip)

2012-12-18 Thread David J. Weller-Fahy
* 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

Possible bug in 6229 (was: heads up regarding tip)

2012-12-18 Thread David J. Weller-Fahy
* 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

Re: heads up regarding tip

2012-12-18 Thread Michael[tm] Smith
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

Re: heads up regarding tip

2012-12-18 Thread David J. Weller-Fahy
* 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

Re: [Mutt] #3590: Apparently valid email address not accepted in mutt > 1.5.21

2012-12-18 Thread Mutt
#3590: Apparently valid email address not accepted in mutt > 1.5.21 -+-- Reporter: william | Owner: me Type: defect | Status: accepted Priority: minor| Milestone: 1.6 Component: mutt

toward a 1.5.22 release

2012-12-18 Thread Michael Elkins
My current plan is to ensure that all the bugfixes that are applied to the mutt packages in various OS distributions have been rolled into the hg repo, then push out a 1.5.22 release. I've found the patches from some distros here: Fedora: http://pkgs.fedoraproject.org/cgit/mutt.git/tree/?h=f18

Re: [Mutt] #3608: Character Š wrong in index and status on Mac OS X

2012-12-18 Thread Mutt
#3608: Character Š wrong in index and status on Mac OS X -+-- Reporter: kolcon | Owner: me Type: defect | Status: new Priority: minor | Milestone: 1.6 Component: mutt| Versio

Re: [Mutt] #3608: Character Š wrong in index and status on Mac OS X

2012-12-18 Thread Mutt
#3608: Character Š wrong in index and status on Mac OS X -+-- Reporter: kolcon | Owner: me Type: defect | Status: closed Priority: minor | Milestone: 1.6 Component: mutt| Versio

heads up regarding tip

2012-12-18 Thread Michael Elkins
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

Re: [Mutt] #3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: "

2012-12-18 Thread Mutt
#3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: " --+- Reporter: vinc17| Owner: mutt-dev Type: defect| Status: new Priority: critical | Miles

Re: [Mutt] #3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: "

2012-12-18 Thread Mutt
#3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: " --+- Reporter: vinc17| Owner: mutt-dev Type: defect| Status: new Priority: critical | Miles

Re: [Mutt] #3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: "

2012-12-18 Thread Mutt
#3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: " ---+ Reporter: vinc17| Owner: mutt-dev Type: defect| Status: closed Priority: critical | Mi

Re: [Mutt] #3506: failure to check server certificate in SMTP TLS connection

2012-12-18 Thread Mutt
#3506: failure to check server certificate in SMTP TLS connection -+-- Reporter: db | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: mutt

Re: [Mutt] #3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: "

2012-12-18 Thread Mutt
#3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: " --+- Reporter: vinc17| Owner: mutt-dev Type: defect| Status: new Priority: critical | Miles

[Mutt] #3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: "

2012-12-18 Thread Mutt
#3609: Crash (segmentation fault) in mutt_substrdup when viewing a message with an empty "Cc: " --+- Reporter: vinc17| Owner: mutt-dev Type: defect| Status: new Priority: critical | Miles

mutt: 5 new changesets

2012-12-18 Thread Brendan Cully
5 new changesets in mutt: http://dev.mutt.org/hg/mutt/rev/722c47f6ede9 changeset: 6232:722c47f6ede9 branch: HEAD tag: tip user:Vincent Lefevre date:Mon Dec 17 20:42:30 2012 -0800 summary: updated fr.po http://dev.mutt.org/hg/mutt/rev/ca4747442189 changeset: 6