From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs602537agc; Thu, 15 Oct 2009 03:54:51 -0700 (PDT) Received: by 10.224.78.22 with SMTP id i22mr8019908qak.280.1255604090688; Thu, 15 Oct 2009 03:54:50 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 6si22299qyk.71.2009.10.15.03.54.50; Thu, 15 Oct 2009 03:54:50 -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 0009818582CC; Thu, 15 Oct 2009 06:54:49 -0400 (EDT) Received: from twice-irc.de (mx2.twice-irc.de [79.140.35.195]) by rubyforge.org (Postfix) with ESMTP id 5163A18582AC for ; Thu, 15 Oct 2009 06:50:15 -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 610FE1665C9 for ; Thu, 15 Oct 2009 12:50:14 +0200 (CEST) Received: by midna.zekjur.net (Postfix, from userid 101) id 9326B97A1E1; Thu, 15 Oct 2009 12:50:13 +0200 (CEST) From: Michael Stapelberg To: sup-talk Date: Thu, 15 Oct 2009 12:50:13 +0200 Message-Id: <1255603625-sup-2558@midna.zekjur.net> User-Agent: Sup/git Subject: [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 Hi, 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. As a workaround, I now added the current time to my script, so that every header will have a different md5 sum. But maybe we can think of a more clever way to generate faked message ids? Maybe also hash the body of the message? Best regards, Michael _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk