Hmmm...this is the header for one of the messages. Why are there so many Received lines? Can someone explain how this header could be the reason the newsletter went out multiple times? Received: from echo.cgim.com (localhost [127.0.0.1]) by io.cgim.com (8.11.6/8.11.6) with ESMTP id hA6AnfX11860; Thu, 6 Nov 2003 05:49:41 -0500 (EST) X-Authentication-Warning: io.cgim.com: iscan owned process doing -bs Received: from echo.cgim.com (echo.cgim.com [216.27.152.230]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA6A6rh07133; Thu, 6 Nov 2003 05:06:54 -0500 (EST) Received: from LISTS.CGIM.COM by LISTS.CGIM.COM (LISTSERV-TCP/IP release 1.8d) with spool id 741408 for [log in to unmask]; Thu, 6 Nov 2003 05:00:34 -0500 Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA6A0Jh06799 for <[log in to unmask]>; Thu, 6 Nov 2003 05:00:19 -0500 (EST) Received: from fwd07.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1AHheJ-00065k-0M; Thu, 06 Nov 2003 11:45:59 +0100 Received: from target01.target-soft.com (JT5fvBZ6gekbuVfexZx3ZJSpLV7mpWdRvK7BdqXZhnL4+O+Uvo9nYq@[80.131.155.14]) by fmrl07.sul.t-online.com with esmtp id 1AHheA-2Bomgq0; Thu, 6 Nov 2003 11:45:50 +0100 Received: from target01.target-soft.com (target01 [10.0.0.2]) by target01.target-soft.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VV0F7WC9; Thu, 6 Nov 2003 11:45:50 +0100 Received: by target01.target-soft.com (Microsoft Exchange Connector for POP3 Mailboxes 4.50.2113) with SMTP (Global POP3 Download) id [log in to unmask]; Thu, 6 Nov 2003 11:45:40 +0100 Delivered-To: [log in to unmask] Received: (qmail 15588 invoked by uid 110); 6 Nov 2003 10:35:49 -0000 Delivered-To: [log in to unmask] Received: (qmail 15584 invoked from network); 6 Nov 2003 10:35:49 -0000 Received: from echo.cgim.com (HELO fw01.cc-net.de) (216.27.152.230) by gamma.cc-net.de with SMTP; 6 Nov 2003 10:35:49 -0000 Received: from echo.cgim.com ([216.27.152.230]) by fw01.cc-net.de via smtpd (for gamma.cc-net.de [213.183.80.20]) with ESMTP; Thu, 6 Nov 2003 11:53:14 +0100 Received: from echo.cgim.com (echo.cgim.com [216.27.152.230]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA69mSh06089; Thu, 6 Nov 2003 04:48:29 -0500 (EST) Received: from LISTS.CGIM.COM by LISTS.CGIM.COM (LISTSERV-TCP/IP release 1.8d) with spool id 741195 for [log in to unmask]; Thu, 6 Nov 2003 03:59:31 -0500 Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA63gvh18595 for <[log in to unmask]>; Wed, 5 Nov 2003 22:42:57 -0500 (EST) Received: from fwd09.aul.t-online.de by mailout04.sul.t-online.com with smtp id 1AHbl5-0001Cw-00; Thu, 06 Nov 2003 05:28:35 +0100 Received: from gerstl1.gerstl-haustechnik.de (E2I-F6ZGgeAd9qt9MMdlm51uz7kEjPKSszL5PCAPVXFBBJAarKg96M@[217.228.219.48]) by fmrl09.sul.t-online.com with esmtp id 1AHbl3-1L32n20; Thu, 6 Nov 2003 05:28:33 +0100 thread-index: AcOkHm9XTGi2FHQ1QI61LfeHht3O0g== Received: from mail pickup service by gerstl1.gerstl-haustechnik.de with Microsoft SMTPSVC; Thu, 6 Nov 2003 05:28:31 +0100 Received: from echo.cgim.com (echo.cgim.com [216.27.152.230]) by r1-w1.1st-design.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id hA64NNel032739 for <[log in to unmask]>; Thu, 6 Nov 2003 05:23:24 +0100 Received: from echo.cgim.com (echo.cgim.com [216.27.152.230]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA63Gsh17684; Wed, 5 Nov 2003 22:16:55 -0500 (EST) Received: from LISTS.CGIM.COM by LISTS.CGIM.COM (LISTSERV-TCP/IP release 1.8d) with spool id 738696 for [log in to unmask]; Wed, 5 Nov 2003 22:00:12 -0500 Content-Class: urn:content-classes:message Priority: normal Received: from mail.speakeasy.net (mail8.speakeasy.net [216.254.0.208]) by echo.cgim.com (8.11.6/8.11.6) with ESMTP id hA62pFh17097 for <[log in to unmask]>; Wed, 5 Nov 2003 21:51:15 -0500 (EST) Received: (qmail 22864 invoked from network); 6 Nov 2003 03:36:54 -0000 Received: from unknown (HELO NELLY) ([216.27.152.253]) (envelope-sender <[log in to unmask]>) by mail8.speakeasy.net (qmail-ldap-1.03) with SMTP for <[log in to unmask]>; 6 Nov 2003 03:36:54 -0000 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-MS-TNEF-Correlator: <[log in to unmask]> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Approved-By: Femina Cybrarian <[log in to unmask]> X-UIDL: FFl!!_K1"!ROp"!6SG"! MIME-Version: 1.0 X-OriginalArrivalTime: 06 Nov 2003 04:28:31.0748 (UTC) FILETIME=[6F29A440:01C3A41E] X-Seen: false Approved-By: Feminamail List <[log in to unmask]> X-Seen: false X-ID: [log in to unmask] Approved-By: Feminamail List <[log in to unmask]> Message-ID: <[log in to unmask]> Date: Wed, 5 Nov 2003 22:37:38 -0500 Reply-To: Femina Cybrarian <[log in to unmask]> Sender: Feminamail List <[log in to unmask]> From: Femina Cybrarian <[log in to unmask]> Subject: News is happening fast...Femina is the place to find it To: [log in to unmask] Content-Length: 10000 Status: -----Original Message----- From: LISTSERV give-and-take forum [mailto:[log in to unmask]]On Behalf Of Valdis Kletnieks Sent: Thursday, November 06, 2003 11:53 AM To: [log in to unmask] Subject: Re: Same email going out 4 times On Thu, 06 Nov 2003 11:47:04 EST, Nelly Yusupova <[log in to unmask]> said: > We sent out a newsletter to our users yesterday and it went out 4 times! > Does anyone know why this happened and how to fix it? Get at least 2 of the notes, and start comparing headers (particularly the Received: lines). You will likely find that the first few (at the *bottom*, they get added newest-on-top) are identical, and at some point they diverge. That's where the problem lies. The problem could be any number of places - you may even find that the very first Received: is different. This means that the PC or whatever is creating the mail actually posted it several times. One common cause for multiple postings is if one machine sends the mail to the next hop on the path, the receiving machine does in fact get the mail OK, but for whatever reason (timeout, network burp, whatever) the sending machine never actually receives the "I got it" acknowledgement, so it retries the mail later.