I completely agree, Matt.  Most delays on our server end up being
failures to connect to the MX of the destination (we use the skip list
in imail).  

Like you, I do start by checking the spool and have a canned "Email
isn't always real-time and delays should be expected occasionally, we've
tuned our server to try and minimize all delays on our end."

Unfortunately I still sometimes have to document those delays for my
boss (or his boss).

-Scott


> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Matthew Bramble
> Sent: Friday, November 21, 2003 11:36 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Declude.JunkMail] Log parsing program to show 
> flow of a message
> 
> 
> Time stamps in message headers?  But I don't have any delays on my 
> server of the processing variety.  Any delays on my server are almost 
> always caused by external mail servers or Internet traffic 
> which might 
> keep the first SMTP attempt from connecting.  If a customer 
> asks about 
> this, I check my spool, and tell them that E-mail delivery is 
> imperfect 
> and it doesn't always work in real-time.  Sometimes I might uncover a 
> different problem though, like someone screwing up their mail client 
> config.  That's definitely more common than my server causing a delay 
> (as is probably the case with most around here I would think).
> 
> Matt
> 
> 
> McCool, Scott wrote:
> 
> >I'm interested to know whether anyone has used or developed 
> a program 
> >to follow the lifecycle of a message through imail & declude.
> >
> >We host some aliases for users here, and occasionally get complaints 
> >about unreasonable delays in getting email.  When they complain long 
> >enough (grin), I trudge through the log files searching for the 
> >particular recipient, note the queue filename & imail log hash code 
> >(SMTP-(04281E10), or whatever), and extract everything for that 
> >message; if it gets requeued I look for the queue filename 
> and find the 
> >next log code when it's processed again.  It's a fairly 
> tedious/manual 
> >process, and is complicated by the fact that I also need to 
> check that 
> >queue filename in the declude logs...
> >
> >What are other people doing for this sort of "investigation"?
> >
> >Thanks!
> >
> >-Scott
> >
> >
> >
> >
> >-------------------------------------------------------------
> ---------
> >Scott McCool
> >Systems Administrator
> >Darden Information Services
> >-------------------------------------------------------------
> ---------
> >  
> >
> 
> 
> ---
> [This E-mail was scanned for viruses by Declude Virus 
(http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type
"unsubscribe Declude.JunkMail".  The archives can be found at
http://www.mail-archive.com.
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]

---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.

Reply via email to