IETF Logo Mail Archive

Re: drums2?

Tony Hansen <tony@att.com> Thu, 22 August 2002 22:10 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7MMAlJ28402 for ietf-822-bks; Thu, 22 Aug 2002 15:10:47 -0700 (PDT)
Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7MMAj228398 for <ietf-822@imc.org>; Thu, 22 Aug 2002 15:10:45 -0700 (PDT)
Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id g7MMAgEx005233 for <ietf-822@imc.org>; Thu, 22 Aug 2002 17:10:42 -0500 (CDT)
Received: from att.com (<unknown.domain>[135.210.32.47]) by maillennium.att.com (mailgw1) with SMTP id <20020822221040gw100fmclbe> (Authid: tony); Thu, 22 Aug 2002 22:10:40 +0000
Message-ID: <3D65411F.2090701@att.com>
Date: Thu, 22 Aug 2002 15:53:03 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1
X-Accept-Language: en-us, en
MIME-Version: 1.0
CC: ietf-822@imc.org
Subject: Re: drums2?
References: <200208221754.g7MHsw021711@astro.cs.utk.edu>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

Me too. Fortunately, my mail provider lets me use either "=" or "+" as a 
subaddress character. It's when BOTH of those don't work that I get 
really upset.

I've successfully gotten some web sites to fix their ages so that they 
handle the + addresses okay.

By the way, some spammers appear to be becoming aware of subaddresses, 
stripping them off before sending their email. :-(

	Tony Hansen
	tony@att.com

Keith Moore wrote:
> for what it's worth, I've run into several web forms that cannot deal
> with addresses containing +  either because they forbid it explicitly
> (either in javascript or on the server side) or because they don't 
> translate + into %2B when encoding it in a URL that gets sent back to the
> client.

v2.23.0 | Report a Bug | By Email