Kevin J. McCarthy writes:
* First, my understanding is the rfc653x series is not incompatible with
IDNA2008. The introduction to rfc6530 mentions rfc5890 for domain
encoding, and in fact rfc6531 section 3.2 even says
It MAY transmit the domain parts of mailbox names within SMTP
I wrote:
Matter of opinion. Mine is that SMTPUTF8 is enough. Mutt
doesn't carry out a server compliance test, it just sends mail,
so it should check the extension it wants to use. Checking other
extensions that are/may be implicitly used is a digression.
Let me elaborate on that.
Mutt uses a
#3775: Heap-use-after-free when trying save mailbox changes after moving file
+-
Reporter: Lekensteyn | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone:
Component: IMAP|Version:
Keyword
Hi Arnt,
Thanks for the reply. This email is really helpful!
On Fri, Sep 04, 2015 at 10:44:50AM +0100, Arnt Gulbrandsen wrote:
> Kevin J. McCarthy writes:
> >* First, my understanding is the rfc653x series is not incompatible with
> > IDNA2008. The introduction to rfc6530 mentions rfc5890 for
#3775: Heap-use-after-free when trying save mailbox changes after moving file
-+-
Reporter: Lekensteyn | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone:
Component: IMAP|Version:
Res
I've uploaded this to the ticket, but wanted to mail it to the list too
in case anyone has comments.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
http://www.8t8.us/configs/gpg-key-transition-statement.txt
# HG changeset patch
# User Kevin McCarthy
# Da
#3775: Heap-use-after-free when trying save mailbox changes after moving file
-+-
Reporter: Lekensteyn | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone:
Component: IMAP|Version:
Res
