Re: [Asrg] seeking comments on new RMX article

waltdnes@waltdnes.org Sat, 10 May 2003 03:43 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 XAA10956 for <asrg-archive@odin.ietf.org>; Fri, 9 May 2003 23:43:52 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4A3s8G08650 for asrg-archive@odin.ietf.org; Fri, 9 May 2003 23:54:08 -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 h4A3s7808647 for <asrg-web-archive@optimus.ietf.org>; Fri, 9 May 2003 23:54:07 -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 XAA10939; Fri, 9 May 2003 23:43:22 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ELIZ-0001a0-00; Fri, 09 May 2003 23:45:23 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ELIZ-0001Zw-00; Fri, 09 May 2003 23:45:23 -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 h4A3qI808520; Fri, 9 May 2003 23:52:18 -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 h4A3pN808481 for <asrg@optimus.ietf.org>; Fri, 9 May 2003 23:51:23 -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 XAA10844 for <asrg@ietf.org>; Fri, 9 May 2003 23:40:37 -0400 (EDT)
From: waltdnes@waltdnes.org
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ELFv-0001Z7-00 for asrg@ietf.org; Fri, 09 May 2003 23:42:39 -0400
Received: from dci.doncaster.on.ca ([66.11.168.194] helo=smtp.istop.com) by ietf-mx with esmtp (Exim 4.12) id 19ELFu-0001Z4-00 for asrg@ietf.org; Fri, 09 May 2003 23:42:38 -0400
Received: from waltdnes.org (ip88-165.tor.istop.com [66.11.165.88]) by smtp.istop.com (Postfix) with SMTP id 37B0E36A5F for <asrg@ietf.org>; Fri, 9 May 2003 23:43:36 -0400 (EDT)
Received: by waltdnes.org (sSMTP sendmail emulation); Fri, 9 May 2003 23:43:20 +4400
To: ASRG list <asrg@ietf.org>
Subject: Re: [Asrg] seeking comments on new RMX article
Message-ID: <20030510034320.GA3998@m1800>
References: <27C4E14288DB344FBA10705D57A9BB043E564F@DF-CHOPPER.platinum.corp.microsoft.com> <IOEPKAPPDKHPENCKFNNGEEPHCDAA.tthomson@neosinteractive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <IOEPKAPPDKHPENCKFNNGEEPHCDAA.tthomson@neosinteractive.com>
User-Agent: Mutt/1.4.1i
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: Fri, 09 May 2003 23:43:20 -0400

On Thu, May 08, 2003 at 12:22:17PM +0100, Tom Thomson wrote

> 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.

  This is where ssh-tunnelling and webmail-over-SSL come in *VERY*
handy.  If a company can afford to send an executive to a faraway city
and pay for a laptop, they can afford to install ssh on his/her laptop.

-- 
Walter Dnes <waltdnes@waltdnes.org>
Email users are divided into two classes;
1) Those who have effective spam-blocking
2) Those who wish they did
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg