RE: [Asrg] seeking comments on new RMX article

"Hallam-Baker, Phillip" <pbaker@verisign.com> Fri, 09 May 2003 04:56 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23034 for <asrg-archive@odin.ietf.org>; Fri, 9 May 2003 00:56:00 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4955lg20166 for asrg-archive@odin.ietf.org; Fri, 9 May 2003 01:05:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4955k820163 for <asrg-web-archive@optimus.ietf.org>; Fri, 9 May 2003 01:05:46 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22982; Fri, 9 May 2003 00:55:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Dzwp-0001G3-00; Fri, 09 May 2003 00:57:31 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Dzwp-0001G0-00; Fri, 09 May 2003 00:57:31 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49541819957; Fri, 9 May 2003 01:04:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48C99805727 for <asrg@optimus.ietf.org>; Thu, 8 May 2003 08:09:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20367 for <asrg@ietf.org>; Thu, 8 May 2003 07:59:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Dk5M-0002QM-00 for asrg@ietf.org; Thu, 08 May 2003 08:01:16 -0400
Received: from peacock.verisign.com ([65.205.251.73]) by ietf-mx with esmtp (Exim 4.12) id 19Dk5L-0002QJ-00 for asrg@ietf.org; Thu, 08 May 2003 08:01:15 -0400
Received: from mou1wnexc02.verisign.com (verisign.com [65.205.251.54]) by peacock.verisign.com (8.12.9/) with ESMTP id h48C28dv001929; Thu, 8 May 2003 05:02:08 -0700 (PDT)
Received: by mou1wnexc02.verisign.com with Internet Mail Service (5.5.2653.19) id <K1JBWL54>; Thu, 8 May 2003 05:02:08 -0700
Message-ID: <CE541259607DE94CA2A23816FB49F4A301AE2463@vhqpostal6.verisign.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: 'Tom Thomson' <tthomson@neosinteractive.com>, Bob Atkinson <bobatk@exchange.microsoft.com>, asrg@ietf.org
Subject: RE: [Asrg] seeking comments on new RMX article
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Thu, 08 May 2003 05:02:06 -0700

There is a solution to this problem, a VPN.

I don't think it is necessary to insist that RMX solve every problem. It is
a quick fix that will buy some time, not a long term solution.

The answer to the problem lies in the filter behavior. You do not have to
bitbucket every message that does not have the proper headers, you just
assign a big spambayes penalty so that the threshold for bitbucketing is
much lower.

Also you can take other behaviors like not bouncing.

		Phill

> -----Original Message-----
> From: Tom Thomson [mailto:tthomson@neosinteractive.com]
> Sent: Thursday, May 08, 2003 7:22 AM
> To: Bob Atkinson; asrg@ietf.org
> Subject: RE: [Asrg] seeking comments on new RMX article
> 
> 
> >> Another common case involves people traveling.  If you 
> plug your laptop
> >> into the network of a hotel or one of your consulting clients, you
> >> might prefer to use an envelope and From header address at 
> your home
> >> systems instead of room1234@losangeles.merriot.com or 
> guest@example.com.
> >
> >I'd like to understand this scenario better, as at present I 
> am confused.
> >
> >Among my confused thoughts are the following questions: What were the
> >steps that led to a mail address and mail server in my hotel 
> room? Which
> >part of the hotel's policy forced me into that? Does any 
> hotel actually
> >do this? In your understanding, which SMTP server is the 
> STMP client on
> >my laptop talking to in order to send it's mail?
> >
> >I would have expected instead that having got IP 
> connectivity, my mail
> >reader on my laptop would have connected back to my normal 
> home (e.g.:
> >pop3.mycompany.com/smtp.mycompany.com) and then sent and 
> received mail
> >through there as usual, resulting in the normal From headers, etc.
> 
> Two separate questions there.
> 
> 1.  Yes, some hotels provide a mailserver and a guest email 
> acount (for
> example hotels using Neos products).  Often these are send 
> only accounts
> (horrible concept, isn't it).  However, the MUA in these 
> cases is a machine
> owned and managed by the hotel (at least in all cases I'm 
> aware of) and not
> the guest's laptop, and both the content From header and the 
> envelope From
> header will be as Vernon described.
> 
> 2.  Yes, hotels provide internet connectivity for guests 
> laptops.  When they
> do so they usually expect the guest to connect to there normal mail
> provider.  This is a problem with providers that don't do 
> authentication of
> some sort, but not the hotel's problem so they've not much 
> incentive to
> solve it. Some do block port 25 so you have to use their 
> outbound MTA, and
> that writes a suitable Received From header identifying the 
> room, but I
> don't think these systems usually rewrite the envelope From address.
> 
> I haven't seen a case where the envelope From would identify 
> the hotel room
> when the sending MUA is the guest's laptop rather than the 
> hotel's machine,
> but I imagine this situation exists as suggested by Vernon.  
> It's just a
> variant of 2 above where the hotel's MTA does rewrite the 
> envelope From.
> 
> Tom
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg