Re: [Mutt] #3018: integer overflow in curs_lib.c if time_inc is used

#3018: integer overflow in curs_lib.c if time_inc is used Changes (by vinc17): * status: new => closed * resolution: => fixed Comment: (In [fb0df4ae0836]) Clamp timeval math to unsigned int to match progress timestamps. This is fine since only relative differences matter. Closes #3018.

Re: [Mutt] #2995: Mutt is folding subject line folds using a tab,

#2995: Mutt is folding subject line folds using a tab, which appears to be against RFC 2822 Changes (by brendan): * priority: major => minor Comment: That subroutine is horrifying, but I believe the line in question is near the bottom of mutt_write_one_header: {{{ cp = &cp[n];

Re: [Mutt] #2966: Crash when opening encrypted message

#2966: Crash when opening encrypted message Comment (by brendan): I can't see anything in the backtrace that indicates a mutt bug. It appears to have died somewhere within libssl. Can you reproduce with an update system (mutt and perhaps also openssl)? Can you also try with gnutls? I have n

Re: [Mutt] #2913: no locale for gpgme context set

#2913: no locale for gpgme context set Changes (by brendan): * status: new => closed * resolution: => fixed Comment: (In [f9af0501d2dd]) Set GPGME locale on first attempt to create context. Closes #2913. -- Ticket URL:

Re: [Mutt] #2930: PGP related key bindings do not work when mutt is

#2930: PGP related key bindings do not work when mutt is compiled with GPGME. Changes (by brendan): * status: new => closed * resolution: => worksforme Comment: No response; unreproducible. -- Ticket URL:

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Comment (by jaymzh): Will do. I can usually get it to happen within a day (it's fairly unpredictable, hence I usually get it unattended) - Phil -- Ticket URL:

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Comment (by brendan): Yes, that doesn't sound like a NAT problem. I think it would be helpful to attach GDB to the mutt process when it becomes wedged and get a backtrace. -- Ticket URL:

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Old description: > On many occasions, I find that an unattended mutt (1.5.17+20080114-1+b1 > from Debian) will hang indefinitely. Never having time to debug it, I > usually kill it and restart it, but today I let it run in strace until it > happend. Here's what the

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Comment (by jaymzh): I find that unlikely for the following reasons: 1. It always happens while active (half way through fetching message headers 99% of the time) 2. It often happens during interactive use (hit '$', it fetches messages, gets, say 5 into 20 n

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Comment (by Brendan Cully): {{{ On Tuesday, 01 July 2008 at 20:39, Mutt wrote: > #3074: Mutt hangs indefinitely > > Comment (by jaymzh): > > Ping. Anyone have a chance to look at this? Is there any extra data I can > provide? My guess about ERESTARTSYS

Re: [Mutt] #3086: Add NNTP support

#3086: Add NNTP support Comment (by llucax): Yes, wrong patch, sorry about that! Thanks for the correction. -- Ticket URL:

Re: [Mutt] #3074: Mutt hangs indefinitely

#3074: Mutt hangs indefinitely Comment (by jaymzh): Ping. Anyone have a chance to look at this? Is there any extra data I can provide? -- Ticket URL:

Re: [Mutt] #2684: crash on s/mime verification

#2684: crash on s/mime verification Changes (by brendan): * status: new => closed * resolution: => fixed Comment: (In [17525e17fa7b]) Bail out of copy if decryption is requested but the desired engine is missing. This closes #2684, but handling of mixed crypto in a single message need

Re: [Mutt] #3087: No server hostname validation in SSL certificate

#3087: No server hostname validation in SSL certificate processing Changes (by gkloepfer): * cc: [EMAIL PROTECTED] (removed) -- Ticket URL:

Re: [Mutt] #3087: No server hostname validation in SSL certificate

#3087: No server hostname validation in SSL certificate processing Changes (by gkloepfer): * version: => 1.5.16 -- Ticket URL:

[Mutt] #3087: No server hostname validation in SSL certificate processing

#3087: No server hostname validation in SSL certificate processing The SSL X509 certificate handling in mutt does not check the CN= against the FQDN that the user entered, and as such there is no indication that the certificate that mutt receives from a SSL-based server actually belongs to the

Re: [Mutt] #3086: Add NNTP support

#3086: Add NNTP support Comment (by brendan): That patch is ancient. I think the one people use these days is here: http://mutt.org.ua/download/. -- Ticket URL:

[Mutt] #3086: Add NNTP support

#3086: Add NNTP support All newsreaders sucks, mutt could just suck less if it had NNTP support =) Here is a widely used patch for it: http://www.fiction.net/blong/programs/mutt/#nntp It would be great if you merge it to upstream. Thank you! -- Ticket URL:

Re: [Mutt] #2951: mutt-1.5.16: smtp error 550 causes blocking

#2951: mutt-1.5.16: smtp error 550 causes blocking Changes (by brendan): * owner: mutt-dev => brendan * status: new => assigned * component: mutt => SMTP * milestone: => 1.6 -- Ticket URL:

Re: [Mutt] #3084: mutt 1.5.6i: Segmentation fault when trying to

#3084: mutt 1.5.6i: Segmentation fault when trying to write mailbox (as non-root) Comment (by brendan): Can you please reproduce with 1.5.18? I can't reproduce this and suspect it's a build or environment problem, otherwise I'm sure we would have gotten many more reports. -- Ticket URL:

Re: [Mutt] #3015: Segmentation Fault on redirection operator

#3015: Segmentation Fault on redirection operator Changes (by brendan): * status: new => closed * resolution: => fixed * component: mutt => SMTP Comment: Fixed in [a2e8f6fab8d3]. -- Ticket URL:

Re: [Mutt] #3085: mailbox corruption when deleting some attachment

#3085: mailbox corruption when deleting some attachment Changes (by brendan): * priority: critical => major * version: => 1.5.18 * milestone: => 1.6 Comment: Patch applied, thanks. -- Ticket URL:

Re: [Mutt] #3085: mailbox corruption when deleting some attachment

#3085: mailbox corruption when deleting some attachment Changes (by rtc): * status: new => closed * resolution: => fixed Comment: (In [49fe0292b503]) When deleting attachments, always print newline separating header from body. Closes #3085. -- Ticket URL: