On Thu, 20 Aug 2015 19:01:48 +0200, Mark Martinec stated: > Michael Ströder wrote: > > Does anybody here have experience with current usage of SMTPUTF8? > > I have a discussion whether that's already used in the wild or not. > > Google does support SMTPUTF8 : > > > $ host -t mx gmail.com > gmail.com mail is handled by 20 alt2.gmail-smtp-in.l.google.com. > gmail.com mail is handled by 5 gmail-smtp-in.l.google.com. > gmail.com mail is handled by 10 alt1.gmail-smtp-in.l.google.com. > gmail.com mail is handled by 40 alt4.gmail-smtp-in.l.google.com. > gmail.com mail is handled by 30 alt3.gmail-smtp-in.l.google.com. > > $ telnet gmail-smtp-in.l.google.com 25 > Trying 2a00:1450:400c:c04::1a... > Connected to gmail-smtp-in.l.google.com. > Escape character is '^]'. > 220 mx.google.com ESMTP gk19si9434995wjc.187 - gsmtp > ehlo test > 250-mx.google.com at your service, [...] > 250-SIZE 35882577 > 250-8BITMIME > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-PIPELINING > 250-CHUNKING > 250 SMTPUTF8 > quit
"outlook.com" has no support. 250-BLU436-SMTP191.smtp.hotmail.com Hello [174.109.28.112] 250-TURN 250-SIZE 41943040 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-TLS 250-STARTTLS 250 OK -- Jerry
