On 2018-04-10 23:52:59 (+0800), John Levine wrote:
In article <20180410083903.gi86...@rincewind.trouble.is> you write:
I've been tasked with finding out what the general consensus is on
the support in email headers for International characters such as
UTF-8 ...
Accented characters in real na
On Tue, 10 Apr 2018, Brandon Long wrote:
I meant interpreting addresses in mail to my own mailboxes, the
generalized version of case folding and subaddresses. Maybe you're right
that undotted i's won't work in a lot of places, but I'd be surprised if
they didn't work in Turkey.
Aren't there st
On this topic, Office 365 EAI support got very positive adoption
https://blogs.technet.microsoft.com/exchange/2017/12/27/eai-support-announcement/
It seems non-ASCII emails and domain names will get more and more popular
___
mailop mailing list
mailo
On Tue, Apr 10, 2018 at 11:32 AM John R Levine wrote:
> >> The Gmail and Hotmail support handles other people's UTF-8 addresses
> >> in mail but they still don't provide UTF-8 addresses on their own
> >> systems.
> >
> > From what I can tell, Gmail and outlook.com's support is basically
> "just s
And yet Google (and Microsoft and many others) do seem to assume that if
the headers are badly formatted (in various ways) it needs rejection or
adds to the score tending towards classification as SPAM. The body is a
different mess, indeed, and one where a more relaxed scanner seems to be
used
On Tue, Apr 10, 2018 at 1:04 AM Vittorio Bertola <
vittorio.bert...@open-xchange.com> wrote:
>
> > Il 10 aprile 2018 alle 2.15 Brandon Long via mailop
> ha scritto:
> >
> >
> > Google does not yet trust third party ARC signatures, yes. We're open
> to manually
> > adding some as they become avai
The Gmail and Hotmail support handles other people's UTF-8 addresses
in mail but they still don't provide UTF-8 addresses on their own
systems.
From what I can tell, Gmail and outlook.com's support is basically "just send
UTF-8", that is, it will send EAI messages without the server offering the
Mail has never been clean, if you've been using such a simple easy
rejection rule,
you are likely a majority English provider who doesn't get much else.
It used to be very common to get mail in koi8-r or koi8-u, or in
iso-2022-jp or sjis,
for example, or even in iso-8859-1 or others around Europe.
> In article
>
> you write:
> >-=-=-=-=-=-
> >-=-=-=-=-=-
> >-=-=-=-=-=-
> >
> >Hello folks
> >
> >I've been tasked with finding out what the general consensus is on the
> >support in email headers for International characters such as UTF-8
> >Charcacters and including things like accented char
But that's the From: comment and Subject: text where they're expected
and already have a way to provide for encoded UTF-8 (or whatever), where
SMTPUTF8 means we will likely begin seeing raw UTF-8 in the From:
mailbox name, and anywhere in Received: and other headers.
This will make MUAs and thu
In article <20180410083903.gi86...@rincewind.trouble.is> you write:
>>>I've been tasked with finding out what the general consensus is on the
>>>support in email headers for International characters such as UTF-8 ...
>Accented characters in real names are pretty universally accepted
>though. E
On 2018-04-09 12:16:08 (+0100), Jeremy Harris wrote:
On 09/04/18 11:22, Annalivia Ford wrote:
I've been tasked with finding out what the general consensus is on the
support in email headers for International characters such as UTF-8
Charcacters and including things like accented characters lik
> Il 10 aprile 2018 alle 2.15 Brandon Long via mailop ha
> scritto:
>
>
> Google does not yet trust third party ARC signatures, yes. We're open to
> manually
> adding some as they become available, but overall, it's a chicken and egg
> thing
> so far, there aren't enough of them yet for us
13 matches
Mail list logo
