From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs613090agc; Thu, 15 Oct 2009 06:48:43 -0700 (PDT) Received: by 10.224.66.211 with SMTP id o19mr26362qai.342.1255614523112; Thu, 15 Oct 2009 06:48:43 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 33si210644qyk.94.2009.10.15.06.48.43; Thu, 15 Oct 2009 06:48:43 -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 B42201218265; Thu, 15 Oct 2009 09:48:42 -0400 (EDT) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 9D91C1858283 for ; Thu, 15 Oct 2009 09:47:36 -0400 (EDT) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1MyQg4-0001CP-GW for sup-talk@rubyforge.org; Thu, 15 Oct 2009 06:47:36 -0700 From: William Morgan To: sup-talk In-reply-to: <1255603625-sup-2558@midna.zekjur.net> References: <1255603625-sup-2558@midna.zekjur.net> Date: Thu, 15 Oct 2009 06:47:36 -0700 Message-Id: <1255614431-sup-5910@masanjin.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Reformatted excerpts from Michael Stapelberg's message of 2009-10-15: > I just noticed that the lack of emails from my backup program seems to be > because of the missing message ids in the mail script I use. In case of > no message id inside the header, sup uses the md5sum of the whole header > (see lib/sup/message.rb:74). This effectively means that messages having > the same md5sum of their header (which happened, since the header was also > generated completely by the script and the values did not change) will > "overwrite" the old message. Doesn't the header include the date? -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk