#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
--+-
#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
--+-
On 22Nov2016 03:27, vincent lefevre wrote:
On 2016-11-20 18:51:25 +1100, Cameron Simpson wrote:
On 19Nov2016 19:58, Kevin J. McCarthy wrote:
> References: =?utf-8?Q?=3C201611170549=2EQ3WT?=
>=?utf-8?Q?foMB=C3=83=C2=BEngguang=2Ewu=40i?=
>=?utf-8?Q?ntel=2Ecom=3E=20=3C1479410?= =?utf-8?Q
Cameron Simpson writes:
Regarding non-ASCII, we decode to bytes. Valid message-ids only
contain ASCII anyway.
Actually message-ids can contain more than just ASCII, see RFC 6530 and
friends. But never 2047. (And even 6530-cognisant senders do well to keep
message-id to just ASCII.)
My sugg
On 2016-11-22 20:43:12 +1100, Cameron Simpson wrote:
> On 22Nov2016 03:27, vincent lefevre wrote:
> > That's clearly illegal. MIME has been designed so that the main
> > features should still work with software that doesn't support MIME
> > (said otherwise, software that only needs to work with ad
#3900: mutt 1.7.1 and Gmail smtp not works (SSL error)
+-
Reporter: mrdini | Owner: brendan
Type: defect | Status: new
Priority: major | Milestone:
Component: SMTP|Version: 1.7.1
Keywords: |
+-
#3900: mutt 1.7.1 and Gmail smtp not works (SSL error)
--+-
Reporter: mrdini | Owner: brendan
Type: defect | Status: closed
Priority: major| Milestone:
Component: SMTP |Version: 1.7.1
Resolution: invalid | Keywo
