On Feb 24, 2006, at 12:52 PM, Robert Citek wrote:
> Since yesterday, I've been getting e-mails only spuriously.
Wild. As of about 7 PM I'm getting flooded with day-old e-mail,
including the beginning of Lee's thread about AFS. Check out the
headers:
Received: from list1.publishingconcepts.com (HELO
list.publishingconcepts.com) ([12.156.3.136])
by mxip01a.cluster1.charter.net with ESMTP; 24 Feb 2006 20:05:04
-0500
X-IronPort-AV: i="4.02,145,1139202000";
d="scan'208"; a="1873788422:sNHT82342476"
Received: from smtp01.publishingconcepts.com (10.11.0.121:3422) by
list.publishingconcepts.com (LSMTP for Windows NT v1.1b) with SMTP id
<[EMAIL PROTECTED]>; Fri, 24 Feb 2006 18:55:55
-0600
Received: FROM smtp01.publishingconcepts.com BY
smtp01.publishingconcepts.com ; Fri Feb 24 17:50:43 2006 -0600
X-Resent-To-Address: [EMAIL PROTECTED]
X-Resent-From-Address: [EMAIL PROTECTED]
X-Resent-Message: <[EMAIL PROTECTED]>
X-Resent-At: Fri, 24 Feb 2006 01:16:16 -0600
Received: from michelob.sluug.org (unverified [128.252.19.8]) by
smtp01.publishingconcepts.com
(Rockliffe SMTPRA 5.2.5) with ESMTP id
<[EMAIL PROTECTED]> for
<[EMAIL PROTECTED]>;
Thu, 23 Feb 2006 21:43:10 -0600
Received: from michelob.sluug.org (loopback [127.0.0.1])
by michelob.sluug.org (8.13.4/8.13.4) with ESMTP id k1O3dY1b019312
for <[EMAIL PROTECTED]>; Thu, 23 Feb 2006 21:39:34 -0600
It looks like michelob.sluug.org handed the post to
smtp01.publishingconcepts.com at 9:43 PM on Thursday. But
smtp01.publishingconcepts.com did not hand off the post to
list.publishingconcepts.com until 6:55 PM on Friday, more than 21
hours later.
Here's my theory of what happened: smtp01 is just one in a pool of
mail servers. Sometime last night someone tweaked the anti-virus/
spam software on smtp01 to hold all messages that matched a pattern
that was just a bit too stringent, e.g. /.*/. It took
publishingconcepts.com a while to notice because smtp01 did not die
but rather appeared to be running just fine. It would still accept
mail, just not pass it on nor bounce it because the message
looked like spam or a virus. Since the other servers were still
handling a portion of the mail traffic, some of the messages could
still make it through, hence the spurious e-mails. Those messages
that went to smtp01 just sat in limbo until someone clued in ("why is
the junk mail disk getting so full so fast?") and fixed the problem,
which happened some time before 7pm tonight.
That sound like a reasonable story?
Regards,
- Robert
http://www.cwelug.org/downloads
Help others get OpenSource software. Distribute FLOSS
for Windows, Linux, *BSD, and MacOS X with BitTorrent
_______________________________________________
CWE-LUG mailing list
[email protected]
http://www.cwelug.org/
http://www.cwelug.org/archives/
http://www.cwelug.org/mailinglist/
