Look at the times in the header. The hop from 66.34.129.19 to  
ams009.ftl.affinity.com took about 90 minutes.
The mail transport logs on the servers 66.34.129.19 and   
ams009.ftl.affinity.com need to be reviewed. In
the example you provided, look for ID S618181AbWDLSmK to see what  
turns up or just look through the
log entries in that time frame if you have access to those systems'  
logs. If not, you need to find out who does
have access and have them do the detective work.

On Apr 12, 2006, at 3:09 PM — 4/12/06, Sheila Fredrickson wrote:

> A bit more explanation ...
>
> It seems that most messages are getting to us slowly; occasionally,  
> mail
> flow seems to speed up, but then it gets slow again.  We have also  
> tried
> stopping Listserv and starting it again ... Sometimes it seems to  
> help,
> sometimes it makes no difference.
>
> The messages are posting to the archives when they are received,  
> and the
> spool empties so it looks as though they have been sent out.  But  
> they must
> be getting stopped somewhere between the point they leave Listserv  
> and their
> actual receipt.
>
> Here is a header from one of the "delayed" messages: I hope this  
> one is
> clean enough ...
>
> Received: from cust_req_fwding ([log in to unmask] --> [log in to unmask])
> 	by ams009.ftl.affinity.com id S618273AbWDLSmL;
> 	Wed, 12 Apr 2006 14:42:11 -0400
> Received: from [66.34.129.19] ([66.34.129.19]:43282 "EHLO XXX.COM")
> 	by ams009.ftl.affinity.com with ESMTP id S618181AbWDLSmK;
> 	Wed, 12 Apr 2006 14:42:10 -0400
> Received: from XXXXX ([66.34.129.19]) by XXX.COM with Microsoft
> SMTPSVC(5.0.2195.6713);
> 	 Wed, 12 Apr 2006 13:27:53 -0500
> Received: by XXX.COM (LISTSERV-TCP/IP release 14.4) with spool id 0082
>           for [log in to unmask]; Wed, 12 Apr 2006 13:27:53 -0500
> Received: from 206.46.252.46 by XXX.COM (SMTPL release 1.0m) with TCP;
>           Wed, 12 Apr 2006 13:27:53 -0500
> Received: from SDesktop ([71.112.9.160]) by vms046.mailsrvcs.net  
> (Sun Java
>           System Messaging Server 6.2-4.02 (built Sep 9 2005)) with  
> ESMTPA
> id
>           <[log in to unmask]> for
>           XXX.com; Wed, 12 Apr 2006 13:27:42 -0500 (CDT)
> MIME-version: 1.0
> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
> X-Mailer: Microsoft Office Outlook 11
> Content-type: multipart/alternative;
>               boundary="----=_NextPart_000_0009_01C65E24.1A6DB9B0"
> Thread-index: AcZeXsZJXxtOkX3STSWAzCT5yDbnFw==
> Message-ID:  <000801c65e5e$c6cc91b0$6501a8c0@SDesktop>
> Date:	      Wed, 12 Apr 2006 11:27:37 -0700
> Reply-To:     XXX XXXXX <[log in to unmask]>
> Sender:	      XXX <[log in to unmask]>
> From:	      XXX XXXXX <[log in to unmask]>
> Subject: !@#$%^
> To:	      [log in to unmask]
> Precedence: list
> List-Help: <http://XXX.com/scripts/wa.exe?LIST=XXX>,
>            <mailto:[log in to unmask]>
> List-Unsubscribe: <mailto:[log in to unmask]>
> List-Subscribe:	<mailto:[log in to unmask]>
> List-Owner: <mailto:[log in to unmask]>
> List-Archive: <http://XXX.com/scripts/wa.exe?LIST=XXX>
> X-OriginalArrivalTime: 12 Apr 2006 18:27:53.0882 (UTC)
> FILETIME=[D0276FA0:01C65E5E]
>
> Thanks for any additional thoughts anyone has ...
>
> Sheila Fredrickson
> NESDA/ISCET
>
>
> -----Original Message-----
> From: LISTSERV site administrators' forum
> [mailto:[log in to unmask]] On Behalf Of Bill Brown
> Sent: Wednesday, April 12, 2006 12:23 PM
> To: [log in to unmask]
> Subject: Re: Strange mail behavior
>
> "LISTSERV site administrators' forum" <LSTSRV- 
> [log in to unmask]> wrote
> on 04/12/2006 01:43:06 PM:
>
>> We had already checked the Spool folder and there was nothing in it.
>>
>> I'm afraid looking at the headers on mail from me may not help  
>> because
> it's
>> coming from a different domain on another server. :-)
>
> Looking at headers is always useful.  It will tell you when it passed
> through each point along the path.  If there's a delay, the headers  
> will
> help you narrow it down.  try posting them and let us take a look  
> (sanitize
> them by only obscuring list and user names)
>
>> We did look at mail headers but could not see anything readily that
> might be
>> the cause.
>>
>> The other possibility might be a Microsoft update. :-)
>
> But the patches were pushed out yesterday, not 2 weeks ago when you  
> said the
> problem started.
>
>> The other thing I failed to mention is that mail from Listserv is not
> just
>> slow for us here at this location, it seems to be slow for many of  
>> our
>> recipients, located all over the country on many different e-mail
> systems.
>> I do not know that ALL of them are receiving mail slowly, but we have
> heard
>> from several so we know it is not just us.
>
> Earlier you made it sound like the delay was in it getting to the  
> listserv
> box.  That would make it slow for all subscribers.  Do some of them  
> get the
> messages in a timely manner and not others??
>
>> Last time something like this happened, it turned out to be that a
>> mail relay somewhere out on the Internet was down.  It didn't affect
> everyone;
>> maybe half.
>
> Yep, that'll do it.

--
Stan Horwitz
[log in to unmask]