Need help decyphering email header information

Factual Questions
1

I send a weekly report to a list of customers, and also to my boss.

The last report was sent Wednesday, but he didn’t get it until Saturday. He uses AOL. I like to think it is just AOL being complete shit, but just in case their shittiness isn’t to blame, is there a way to tell the bottleneck from the message headers? I changed addresses and IP numbers for paranoia’s sake. Just a note, I use fuse.net as the SMTP server.

Return-Path: <ME@MYEMAILADDRESS.COM>
Received: from rly-md01.mx.aol.com (rly-md01.mail.aol.com [172.20.29.XXX]) by air-md06.mail.aol.com (v118.4) with ESMTP id MAILINMD064-8e34687072e245; Sat, 30 Jun 2007 21:45:27 -0400
Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.XXX]) by rly-md01.mx.aol.com (v118.4) with ESMTP id MAILRELAYINMD013-8e34687072e245; Sat, 30 Jun 2007 21:45:19 -0400
Received: from gx4.fuse.net ([216.68.199.XX]) by smtp3.fuse.net
(InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP
id <20070627214952.NCIH6940.smtp3.fuse.net@gx4.fuse.net>
for <AAH2@aol.com>; Wed, 27 Jun 2007 17:49:52 -0400
Received: from MYCOMPUTERNAME ([216.68.199.XX]) by gx4.fuse.net with ESMTP
id <20070627214945.NEQJ7351.gx4.fuse.net@MYCOMPUTERNAME>;
Wed, 27 Jun 2007 17:49:45 -0400
From: “Gilded Lily” <ME@MYEMAILADRESS.COM>
To: “Gilded’s Boss” <GILDED’SBOSS@aol.com>
Subject: Buildfax Vol XIX Issue 12
Date: Wed, 27 Jun 2007 17:49:22 -0400
Message-ID: <002f01c7b905$080a3450$010ba8c0@MYCOMPUTERNAME>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary=“----=_NextPart_000_0030_01C7B8E3.80F89450”
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AcXJ2ZeBH7vf4NC7RWuBNicIt5XbHQK56bKAAsZgKVACv6gBYALDLQIgAr0p/AACx7gz0ALCPxTwAxdn4+ACXxhRsALDnaFAAyd7qJACVKEokALFMvhAAukW9kAClv3fQALF8N6AAxws96ACL0e3oALux/iAAsIvkMACwkV8oAK9EVaABYmshQACtBjI4AK9YaZgAsZMBMAAAdGdYAK8b31gAsF85XACvyR7cALQ39yAArDwMGACwNW1wAK975IQBYgsxqAC8PNDsAKFlrYAAsIctfACwd2DUALiurxQApqmVzACvid9YALDqwlwAsBy0LA=
X-AOL-IP: 216.68.8.XXX

Thanks!

Jeff

2 

Received: from smtp2.fuse.net (mail-out2.fuse.net [216.68.8.XXX]) by rly-md01.mx.aol.com (v118.4) with ESMTP id MAILRELAYINMD013-8e34687072e245; Sat, 30 Jun 2007 21:45:19 -0400
Received: from gx4.fuse.net ([216.68.199.XX]) by smtp3.fuse.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20070627214952.NCIH6940.smtp3.fuse.net@gx4.fuse.net> for <AAH2@aol.com>; Wed, 27 Jun 2007 17:49:52 -0400

Based on these two lines, it looks like there were around three days betwee your relay receiving the message from you (the second line) and AOL’s MX receiving it from your ISP (the first line). Without mail server logs or failure notices, it’s difficult to tell whether the delay was due to the message being stalled on smtp3.fuse.net or rly-md01.mx.aol.com not accepting the message for those three days.

AOL is known to deny SMTP connections if your ISP is suspected to be a spam relay. You might want to contact the administrator of smtp3.fuse.net, and include the email header so that he can find this transaction in the mail server logs.