From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.117.16 with SMTP id p16cs613713agc;
        Thu, 15 Oct 2009 06:59:12 -0700 (PDT)
Received: by 10.224.101.206 with SMTP id d14mr46494qao.238.1255615151860;
        Thu, 15 Oct 2009 06:59:11 -0700 (PDT)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 42si430604qyk.98.2009.10.15.06.59.11;
        Thu, 15 Oct 2009 06:59:11 -0700 (PDT)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 8D28013C8978;
	Thu, 15 Oct 2009 09:59:11 -0400 (EDT)
Received: from twice-irc.de (mx2.twice-irc.de [79.140.35.195])
	by rubyforge.org (Postfix) with ESMTP id DC3BB197827D
	for <sup-talk@rubyforge.org>; Thu, 15 Oct 2009 09:59:02 -0400 (EDT)
Received: from midna.zekjur.net (midna.zekjur.net
	[IPv6:2001:4d88:1008:4242:21c:c0ff:fe7e:4776])
	by twice-irc.de (Postfix) with ESMTPSA id DB2B21665C5
	for <sup-talk@rubyforge.org>; Thu, 15 Oct 2009 15:59:01 +0200 (CEST)
Received: by midna.zekjur.net (Postfix, from userid 101)
	id 32A5597A1E1; Thu, 15 Oct 2009 15:59:01 +0200 (CEST)
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <1255614431-sup-5910@masanjin.net>
References: <1255603625-sup-2558@midna.zekjur.net>
	<1255614431-sup-5910@masanjin.net>
Date: Thu, 15 Oct 2009 15:59:01 +0200
Message-Id: <1255615018-sup-5653@midna.zekjur.net>
User-Agent: Sup/git
Subject: Re: [sup-talk] About faking message IDs
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org

Hi William,

Excerpts from William Morgan's message of Thu Oct 15 15:47:36 +0200 2009:
> Doesn't the header include the date?
No, in my case it did not. The reason for that is calling "deliver" directly,
that is without talking SMTP to a mailserver. Thus, no headers are getting
added. Surely this is a corner case, but I think it will cause headache for
system administrators running into this one, if they notice it all (overwriting
messages is quite dangerous).

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk