IETF Logo Mail Archive

Re: [EAI] Fw: How to deal with EAI

Franck Martin <fmartin@linkedin.com> Wed, 19 October 2016 02:47 UTC

Return-Path: <fmartin@linkedin.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6331296C0 for <ima@ietfa.amsl.com>; Tue, 18 Oct 2016 19:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.752
X-Spam-Level:
X-Spam-Status: No, score=-4.752 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=linkedin.com header.b=yiQXcnob; dkim=pass (1024-bit key) header.d=linkedin.com header.b=bS+/iI5M
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ht7MVJ-Oeoka for <ima@ietfa.amsl.com>; Tue, 18 Oct 2016 19:47:39 -0700 (PDT)
Received: from mail522.linkedin.com (mail522.linkedin.com [108.174.6.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3473E1296A7 for <ima@ietf.org>; Tue, 18 Oct 2016 19:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1476845247; bh=9SKsJp3d/i+TZxcn/CjauSdALcIwxp8hiBIaF5S7aZo=; h=MIME-Version:From:Date:Subject:To:Content-Type; b=yiQXcnobEEc+d54nd1CFdTVso7mmhDylvwFK3YtWmAJbSeyf40nH9wdzSB4+UlY3+ 9yQcO5Uix16LtR/CvHkAKkOF/DNxkO3ae1KTGYZRT1agVp7FtpFzlc0wSnWJRU82ji lyN7v0OjH6VESjTS67y9tHuifRv0VoIb25LU9oec=
Authentication-Results: mail522.prod.linkedin.com x-tls.subject="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com"; auth=pass (cipher=ECDHE-RSA-AES128-GCM-SHA256)
Authentication-Results: mail522.prod.linkedin.com; iprev=pass policy.iprev="2607:f8b0:400c:c05::248"; spf=softfail smtp.mailfrom="fmartin@linkedin.com" smtp.helo="mail-vk0-x248.google.com"; dkim=pass header.d=linkedin.com; tls=pass (verified) key.ciphersuite="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256" key.length="128" tls.v="tlsv1.2" cert.client="C=US,ST=California,L=Mountain View,O=Google Inc,CN=smtp.gmail.com" cert.clientissuer="C=US,O=Google Inc,CN=Google Internet Authority G2"
Received: from [2607:f8b0:400c:c05::248] ([2607:f8b0:400c:c05::248.35556] helo=mail-vk0-x248.google.com) by mail522.prod.linkedin.com (envelope-from <fmartin@linkedin.com>) (ecelerity 3.6.21.53563 r(Core:3.6.21.0)) with ESMTPS (cipher=ECDHE-RSA-AES128-GCM-SHA256 subject="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com") id 34/DE-11653-FBED6085; Wed, 19 Oct 2016 02:47:27 +0000
Received: by mail-vk0-x248.google.com with SMTP id 2so12019076vkb.2 for <ima@ietf.org>; Tue, 18 Oct 2016 19:47:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9SKsJp3d/i+TZxcn/CjauSdALcIwxp8hiBIaF5S7aZo=; b=bS+/iI5MJO7hFpceG647zT/caSxp+mdn+VhdyZkAXJJRJMDqkhmCm/zeli+V0lva1O l4UQkJp1RMZ2ZWq/4ZNlgLcp5oUDuGdbTM1cUrfTTYlzbchmuF/+s/57Ig1Bm0V0FuJ+ QYeFDIILNL1N2jX/OF40yV75ekpsKH5W/txKo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9SKsJp3d/i+TZxcn/CjauSdALcIwxp8hiBIaF5S7aZo=; b=QPsxBEAcFUYEcofsuHZZ1Zd0zNjWQiLXDEnoHDz3wfzoIkJJzpOE8OceqN8mjsbQVi Tz2PUCfY0bl1COCvgZTRX/t/SBSgEHXogUB5pUvsmnI9BxHHCAy16qYEjMJPh+Fx6C2r W6Rdfamfj03t3Oxa0NaoFqF9+5LW73Gi7DTr8rGxVjq6qv6lFKvJWAui0PV0b72+IN+Z ZuVRyHVeHKXSBlOTq9ZsjtF74zEp+V4LYpDCNXFufODuWfTCBxtX3Hx0MYGcbtXa9o1e /bW452bBBH84FMrz9Rs6pv8kidhyAaAlwLEg3E/v5wts3G1N+i/w+SSLFM5E+bTZDX7M 1F6w==
X-Gm-Message-State: AA6/9RlVV54t8/GBXuW1gefvkofUcFiKARPYFOIWyo9iCYUjION9jzTibIKjS0v3l0J5clHWiW/4whluFKL8Zl9KqXBM+/GIu6ou+b2MeGlZgy3N9oqWGIcKk42mNHPYOiLaVs8CIpNtR+YovwwievOiDQ==
X-Received: by 10.176.69.195 with SMTP id u61mr707384uau.37.1476845246884; Tue, 18 Oct 2016 19:47:26 -0700 (PDT)
X-Received: by 10.176.69.195 with SMTP id u61mr707363uau.37.1476845246445; Tue, 18 Oct 2016 19:47:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.49.22 with HTTP; Tue, 18 Oct 2016 19:47:05 -0700 (PDT)
In-Reply-To: <1054227051.941475.1476842578566@mail.yahoo.com>
References: <6bd33b71.8f.157c41e784a.Coremail.___@___.__> <1054227051.941475.1476842578566@mail.yahoo.com>
From: Franck Martin <fmartin@linkedin.com>
Date: Tue, 18 Oct 2016 19:47:05 -0700
Message-ID: <CANyRh99GvNXPM5d8EALjsCBGhMUDPmSGsebVJCHO7xUkhLyYHg@mail.gmail.com>
To: Nalini Elkins <nalini.elkins@insidethestack.com>
Content-Type: multipart/alternative; boundary="94eb2c11be5c4da22a053f2ed435"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/Ub0HFF94mR_aPvRc1JFfwsFSvQU>
Cc: "ima@ietf.org" <ima@ietf.org>
Subject: Re: [EAI] Fw: How to deal with EAI
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2016 02:47:42 -0000

The coremail system uses an aliasing mechanism to transform the local part
into puny code. There is no rule about what can be an alias of an email
address, so it is not against the rules, but cannot be a standard and
should not be a standard. It works for them because the character set
(Chinese one) is restricted to one that can be puny coded.

I'm curious why you could not reply to all?

On Tue, Oct 18, 2016 at 7:02 PM, <nalini.elkins@insidethestack.com> wrote:

> Franck,
>
> I actually got your email in my REGULAR email & not spam!
>
> But, the local part of your email address is showing in punycode.  I
> believe that is "against the rules".   Am I wrong on that?
>
> BTW, I was not able to do a REPLYALL, so I am forwarding the email.
>
> Thanks,
>
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>
>
>
> ----- Forwarded Message -----
> *From:* Franck Martin <xn--74q5c021c@互联网.公司>
> *To:* ima@ietf.org
> *Sent:* Friday, October 14, 2016 9:55 AM
> *Subject:* [EAI] How to deal with EAI
>
> This email is likely to end up in the moderator queue, but if I cannot
> subscribe, may be I can post?
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>
>
>
> _______________________________________________
> IMA mailing list
> IMA@ietf.org
> https://www.ietf.org/mailman/listinfo/ima
>
>

v2.23.0 | Report a Bug | By Email