On Tue, 2012-08-21 at 17:33 -0700, Gordon Messmer wrote: > Rather than speculate about what may or may not be happening with the > user agent and the MTA, please locate those two messages and send a copy > of *all* of the Received: headers from each. Send them to the list, > unmodified. They should make the situation very clear.
Here they are, my friend. *all* of the received headers, unmodified. If you can find anything enlightening in them that neither I nor the Mailman developers/list admins have found, I'll be forever in your debt :) First set: ---------- Received: from mail.python.org (mail.python.org [::ffff:82.94.164.166]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by shakti.fmp.com with esmtp; Sun, 19 Aug 2012 20:17:11 -0500 id 000000000027586D.0000000050319017.00007186 Received-spf: none (Address does not pass the Sender Policy Framework) SPF=HELO; sender=mail.python.org; remoteip=::ffff:82.94.164.166; remotehost=mail.python.org; helo=mail.python.org; receiver=shakti.fmp.com; Received-spf: pass (Address passes the Sender Policy Framework) SPF=MAILFROM; sender=mailman-users-bounces+fmouse-mailman=fmp....@python.org; remoteip=::ffff:82.94.164.166; remotehost=mail.python.org; helo=mail.python.org; receiver=shakti.fmp.com; Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3X0cYy4Y8HzQCS for <fmouse-mail...@fmp.com>; Mon, 20 Aug 2012 03:17:10 +0200 (CEST) Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1345425430; bh=SE4UwD4ISPf3jV+Q3YQCSAYQHFCFh60pIQB+YnYOazE=; h=From:To:In-Reply-To:References:Date:Message-ID:Mime-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=HaYi6ZYAki+lsgcm4rd643rthkiEslpcywFMRhhMUAemDS7LCWDGibd+8stdHA0ZM V36dC0mdlNnt66BhF/iWn6BP0mlz1ymKYeqRnfpKoH6R1e6SoPCG3txYehD/ea+LWq mtkIHJthDUByfY6gn+wjsEjVrJfSFVt4ht+lMDLs= X-original-to: mailman-us...@python.org Delivered-to: mailman-us...@mail.python.org Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3X0cYw1CRlzQ6g for <mailman-us...@python.org>; Mon, 20 Aug 2012 03:17:08 +0200 (CEST) Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 20 Aug 2012 03:17:08 +0200 Received: from shakti.fmp.com (shakti.fmp.com [208.81.244.105]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for <mailman-us...@python.org>; Mon, 20 Aug 2012 03:17:07 +0200 (CEST) Received: from [192.168.1.17] ([::ffff:10.8.0.4]) by shakti.fmp.com with esmtp; Sun, 19 Aug 2012 20:11:57 -0500 id 000000000027586D.0000000050318EDD.00006F31 Second set: ----------- Received: from mail.python.org (mail.python.org [::ffff:82.94.164.166]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by shakti.fmp.com with esmtp; Sun, 19 Aug 2012 20:13:14 -0500 id 00000000002758BD.0000000050318F2A.00006FC2 Received-spf: none (Address does not pass the Sender Policy Framework) SPF=HELO; sender=mail.python.org; remoteip=::ffff:82.94.164.166; remotehost=mail.python.org; helo=mail.python.org; receiver=shakti.fmp.com; Received-spf: pass (Address passes the Sender Policy Framework) SPF=MAILFROM; sender=mailman-users-bounces+fmouse-mailman=fmp....@python.org; remoteip=::ffff:82.94.164.166; remotehost=mail.python.org; helo=mail.python.org; receiver=shakti.fmp.com; Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3X0cTP0z3tzQQ0 for <fmouse-mail...@fmp.com>; Mon, 20 Aug 2012 03:13:13 +0200 (CEST) Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=python.org; s=200901; t=1345425193; bh=SE4UwD4ISPf3jV+Q3YQCSAYQHFCFh60pIQB+YnYOazE=; h=From:To:In-Reply-To:References:Date:Message-ID:Mime-Version: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=hC3uXpSR8f2B8fLDh4LMu7xdixjEEU3/v+YlJ6QjEkmm6YpgwRKiNZcvOxs0V7Q1B mmpoPCJokMWZ4X4nCupPyY0YLLDmI3jTV9tc0vSh36VARlaYoS90QypSK7/x+Z0X4f tVKs8Li2XFEvTNnpntETbQC9lsY8VAj3cez8v1jI= X-original-to: mailman-us...@python.org Delivered-to: mailman-us...@mail.python.org Received: from albatross.python.org (localhost [127.0.0.1]) by mail.python.org (Postfix) with ESMTP id 3X0cTL2xBFzQM6 for <mailman-us...@python.org>; Mon, 20 Aug 2012 03:13:10 +0200 (CEST) Received: from localhost (HELO mail.python.org) (127.0.0.1) by albatross.python.org with SMTP; 20 Aug 2012 03:13:10 +0200 Received: from shakti.fmp.com (shakti.fmp.com [208.81.244.105]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.python.org (Postfix) with ESMTPS for <mailman-us...@python.org>; Mon, 20 Aug 2012 03:13:09 +0200 (CEST) Received: from [192.168.1.17] ([::ffff:10.8.0.4]) by shakti.fmp.com with esmtp; Sun, 19 Aug 2012 20:13:05 -0500 id 00000000002758BD.0000000050318F21.00006FAC It certainly looks to me as if the MUA sent it twice. WHY it did so is less obvious. The only issue that's absent from these headers is the fact the message 1 was refused by the python.org server for unknown reasons the first time it was sent (450-4.3.2 error). Message 2 was successfully sent a minute later, and message 1 was tried again from the server's queue 5 minutes later and successfully delivered. The timestamps in the Received headers show that the order in which they were received by shakti is the reverse of the order in which they were received by python.org, which is what one would expect in this scenario. The Date header is the same for both, and is accurate: Sun, 19 Aug 2012 20:11:56 -0500 -- Lindsay Haisley | "The difference between a duck is because FMP Computer Services | one leg is both the same" 512-259-1190 | - Anonymous http://www.fmp.com | ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
