Re: [Mutt] #3897: Can't compile mutt 1.7.1 on an embedded NAS

#3897: Can't compile mutt 1.7.1 on an embedded NAS -+-- Reporter: mrdini | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: build |Version: 1.7.1 Resolution: | Keywords: --

[Mutt] #3897: Can't compile mutt 1.7.1 on an embedded NAS

#3897: Can't compile mutt 1.7.1 on an embedded NAS +- Reporter: mrdini | Owner: brendan Type: defect | Status: new Priority: major | Milestone: Component: IMAP|Version: 1.7.1 Keywords: | +-

Legal values for a message-id, and references header

On #mutt, andrey_utkin_ reported getting a bounce trying to reply to a linux-kernel mailing list email. When he replied, vger.kernel.org bounced it because of raw utf-8 in a header. He posted a gist at I don't know how long

Re: [Mutt] #3897: Can't compile mutt 1.7.1 on an embedded NAS

#3897: Can't compile mutt 1.7.1 on an embedded NAS -+-- Reporter: mrdini | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: build |Version: 1.7.1 Resolution: | Keywords: --

Re: [Mutt] #3897: Can't compile mutt 1.7.1 on an embedded NAS

#3897: Can't compile mutt 1.7.1 on an embedded NAS -+-- Reporter: mrdini | Owner: mutt-dev Type: defect | Status: closed Priority: major | Milestone: Component: build |Version: 1.7.1 Resolution: fixed | Keywords: ---

Re: Legal values for a message-id, and references header

On 19Nov2016 13:13, Kevin J. McCarthy wrote: On #mutt, andrey_utkin_ reported getting a bounce trying to reply to a linux-kernel mailing list email. When he replied, vger.kernel.org bounced it because of raw utf-8 in a header. He posted a gist at

mutt: Updated French translation.

changeset: 6868:d14ffd58d976 user: Vincent Lefevre date: Sun Nov 20 01:41:49 2016 +0100 link: http://dev.mutt.org/hg/mutt/rev/d14ffd58d976 Updated French translation. diffs (124 lines): diff -r 4bed0172c27b -r d14ffd58d976 po/fr.po --- a/po/fr.po Fri Nov 18 15:54:27 2016 -0800 +

Re: mutt: Adds binding to create "hotkeys" for messages.

On 2016-11-18 09:57:33 -0800, Kevin J. McCarthy wrote: > Answering my own question: no. Inside the pager, the operation > searches for text in the message. I suppose we could have it in > the pager version, but I think that might be more likely to confuse > someone. I agree. And the macro can

Re: [Mutt] #3870: openssl 1.1

#3870: openssl 1.1 --+-- Reporter: tamo | Owner: mutt-dev Type: task | Status: reopened Priority: trivial | Milestone: Component: build|Version: 1.7.0 Resolution: | Keywords: ssl --

mutt: More openssl1.1 fixes: remove uses of X509->name in debugg...

changeset: 6869:695243ba6374 user: Kevin McCarthy date: Sat Nov 19 19:35:07 2016 -0800 link: http://dev.mutt.org/hg/mutt/rev/695243ba6374 More openssl1.1 fixes: remove uses of X509->name in debugging. (closes #3870) X509->name was a shortcut for the longer name = X509_NAME_oneli

Re: [Mutt] #3870: openssl 1.1

#3870: openssl 1.1 --+-- Reporter: tamo | Owner: mutt-dev Type: task | Status: closed Priority: trivial | Milestone: Component: build|Version: 1.7.0 Resolution: fixed| Keywords: ssl --+-

Re: Legal values for a message-id, and references header

On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: > On 19Nov2016 13:13, Kevin J. McCarthy wrote: > > Should mutt be rfc-2047 encoding/decoding the references > > header? > > No. RFC2047 tokens need to be whitespace delimited from the surrounding > text. No whitespace is permitted

Re: Legal values for a message-id, and references header

On 19Nov2016 19:58, Kevin J. McCarthy wrote: On Sun, Nov 20, 2016 at 10:08:13AM +1100, Cameron Simpson wrote: On 19Nov2016 13:13, Kevin J. McCarthy wrote: > Should mutt be rfc-2047 encoding/decoding the references > header? No. RFC2047 tokens need to be whitespace delimited from the surroundi