From owner-freebsd-questions@FreeBSD.ORG Tue Sep 11 13:05:48 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EE1B16A41A for ; Tue, 11 Sep 2007 13:05:48 +0000 (UTC) (envelope-from jonathan+freebsd-questions@hst.org.za) Received: from hermes.hst.org.za (onix.hst.org.za [209.203.2.133]) by mx1.freebsd.org (Postfix) with ESMTP id 1BFE913C459 for ; Tue, 11 Sep 2007 13:05:43 +0000 (UTC) (envelope-from jonathan+freebsd-questions@hst.org.za) Received: from sysadmin.hst.org.za (sysadmin.int.dbn.hst.org.za [10.1.1.20]) (authenticated bits=0) by hermes.hst.org.za (8.13.8/8.13.8) with ESMTP id l8BD1RZE047566 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 11 Sep 2007 15:01:29 +0200 (SAST) (envelope-from jonathan+freebsd-questions@hst.org.za) From: Jonathan McKeown Organization: Health Systems Trust To: freebsd-questions@freebsd.org Date: Tue, 11 Sep 2007 15:08:21 +0200 User-Agent: KMail/1.7.2 References: <200709111220.09785.jonathan+freebsd-questions@hst.org.za> In-Reply-To: <200709111220.09785.jonathan+freebsd-questions@hst.org.za> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709111508.21463.jonathan+freebsd-questions@hst.org.za> X-Spam-Score: -3.977 () ALL_TRUSTED,AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.61 on 209.203.2.133 Subject: Re: (off-topic) Outlook 2003 msgids causing odd email problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2007 13:05:48 -0000 Replying to myself, On Tuesday 11 September 2007 12:20, Jonathan McKeown wrote: > After much scratching of head and tearing of hair, I have finally found two > provable instances - one in Cyrus and one in Mailman - of replies to > messages being sent using Microsoft Outlook Service Pack 2, where Outlook > has given the reply the same message-id as the message it is replying to - > in flat violation of RFC{2}822. (In one case the original message, the > read-receipt automatically generated by Outlook, the reply, and the forward > of the reply sent when the reply didn't arrive, all had the same msg-id). After further investigation, it appears that the message-id generated by Outlook 2003 has the originating host name on the RHS (after the @), unless the sending machine is a member of a Server 2003 AD domain in which case the domain name is used which increases the risk of a collision (especially if the LHS is copied!). Jonathan