On Thu, Mar 02, 2023 at 04:38:16PM -0700, Alex Burch via mailop wrote:
> I am using unicode in the From: not the MAIL FROM. Do you have to specify
> it SMTPUTF8 in the MAIL FROM to use it in the From header? I don't see
> anything about that here: https://www.rfc-editor.org/rfc/rfc6531
Without
It's the from address they're talking about, it means they can't use an EAI
from address for these cases, they would need to either not send or have a
fallback non-EAI address for the messages.
Brandon
On Fri, Mar 3, 2023 at 12:37 PM Ángel via mailop wrote:
> On 2023-03-03 at 09:37 -0700, Alex
On 2023-03-03 at 09:37 -0700, Alex Burch via mailop wrote:
> We are an ESP and we have a lot of customers who send with characters
> like ü or á, usually in the local part but occasionally in the
> domain. I think if we converted all from addresses to pure ascii
> punycode, we'd solve our problems
It occurs to me that if you only have a handful of addresses with accented
Latin characters, they are probably typos, not real addresses.
Unless you're sending mail to south or southeast Asia, just get rid of
them.
On Fri, 3 Mar 2023, Alex Burch wrote:
Thanks everyone. Is there any reason
We are an ESP and we have a lot of customers who send with characters like
ü or á, usually in the local part but occasionally in the domain. I think
if we converted all from addresses to pure ascii punycode, we'd solve our
problems rather than trying to keep them unicode and rely on SMTPUTF8
Alex Burch via mailop skrev den 2023-03-03 17:22:
If John Jetmore is here, please merge that sucker!
as in posting to public maillist with big html signature ?
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
We are an ESP and we have a lot of customers who send with characters like
ü or á, usually in the local part but occasionally in the domain. I think
if we converted all from addresses to pure ascii punycode, we'd solve our
problems rather than trying to keep them unicode and rely on SMTPUTF8
Thanks everyone. Is there any reason not to just always use punycode for
the domain and keep it pure ascii? Seems safer that way. Are there any
known risks to doing that?
"Always" in what context? The whole point of IDNs and EAI is so that
people who don't speak English can use mail addresses
Thanks everyone. Is there any reason not to just always use punycode for
the domain and keep it pure ascii? Seems safer that way. Are there any
known risks to doing that?
About swaks, there is an open MR to add SMTPUTF8 support:
https://github.com/jetmore
If John Jetmore is here, please merge
It appears that Alex Burch via mailop said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>I am using unicode in the From: not the MAIL FROM. Do you have to specify
>it SMTPUTF8 in the MAIL FROM to use it in the From header? I don't see
>anything about that here: https://www.rfc-editor.org/rfc/rfc6531
See section
Alex Burch via mailop skrev den 2023-03-03 00:38:
I am using unicode in the From: not the MAIL FROM. Do you have to
specify it SMTPUTF8 in the MAIL FROM to use it in the From header? I
don't see anything about that here:
https://www.rfc-editor.org/rfc/rfc6531
I was under the impression that if
https://www.rfc-editor.org/rfc/rfc6532#section-3
> Also note that messages in this format require the use of the
> SMTPUTF8 extension [RFC6531] to be transferred via SMTP.
On Thu, Mar 2, 2023 at 3:38 PM Alex Burch wrote:
> I am using unicode in the From: not the MAIL FROM. Do you have to
I am using unicode in the From: not the MAIL FROM. Do you have to specify
it SMTPUTF8 in the MAIL FROM to use it in the From header? I don't see
anything about that here: https://www.rfc-editor.org/rfc/rfc6531
I was under the impression that if the client offered SMTPUTF8 extension
then you could
Did you specify SMTPUTF8 on the MAIL FROM command? Is swaks that smart?
doesn't look like it.
https://github.com/jetmore/swaks/blob/6bc61708489dc9789246e8fe58d32a0ff4fec8f4/swaks#L1055
Our validation cares, though it uses the same error message in either case,
so I guess it should say RFC6532
RFC 6532 indicates that you can use unicode characters like an umlaut ü
(U+00FC) if the receiving MTA supports SMTPUTF8 extension:
https://www.rfc-editor.org/rfc/rfc6532
But when I test this to Gmail its rejected:
swaks -p 25 -f 't...@acems1.com' --h-From: '"Alex" ' --to '
15 matches
Mail list logo
