<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=US-ASCII">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #8000ff; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#8000ff size=2>
<DIV>In a message dated 3/7/2005 7:42:24 PM Central Standard Time,
moleski@canisius.edu writes:</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000
size=2>Buddy,<BR><BR>Your messages are coming through to the
list.<BR><BR>Otherwise, people would not be replying to them.<BR><BR>
Marty<BR></FONT></BLOCKQUOTE>
<DIV>Yep It's fixed now.</DIV>
<DIV>Buddy</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2><BR>--On
Monday, March 07, 2005 6:44 PM -0500 BUDDYonRC@aol.com
wrote:<BR><BR>><BR>><BR>> In a message dated 3/7/2005 5:10:55 PM
Central Standard Time, rcsteve@tcrcm.org writes:<BR>><BR>><BR>> Hi
Buddy-- don't worry, your messages are coming through. This list uses email,
and email can have some strange excentricities.<BR>><BR>> Email goes
through email servers, one on each end. In the situation of the list server,
add in a third server in the middle.<BR>><BR>> Any of the servers can
get busy, bogged down. Here is an example:<BR>><BR>> Lets say you have
sent out a message to the list server. Your email program does not talk
directly to the nsrca list server, it hands the email off to an email server
provided by your ISP (in this case AOL). Your ISP's mail server then
queues up your<BR>> message until it has time to try and contact the nsrca
server. Depending how busy it is, this could be 1 second, minutes, or in rare
cases (during a spam storm) hours.<BR>><BR>> Once your ISP server has
time, it will try to contact the nsrca mail server. If the nsrca server is not
busy, the message is transferred, and queued for send out to the list members.
If it is busy (maybe with other nsrca list stuff, but could be one or<BR>>
more of their other commercial clients--nscra just rents space from an ISP)
then it sends a short message back to your ISP server "busy-wait". So AOL's
server puts it in a delay queue, and after it takes care of the other 15
million client messages<BR>> waiting in its queues, tries again. Oh, but it
gets another busy-wait message, it doubles the delay time and waits
again. With busy traffic, and doubling of the delay time for each
busy-wait times, messages can get wait-delay times 24 hours or
longer.<BR>><BR>> This same process can happen on the distribution of
the message out to the list members as well. For example, when the nsrca
server tried to contact the AOL server, if it got a wait-busy reply, it puts
the message to you in a wait queue and goes on<BR>> through the rest of the
list before trying again.<BR>><BR>> Of course, some other problems can
occur as well. In the past, we have had AOL's automated spam filtering think
that email from the list was spam and started blocking it.<BR>><BR>>
Looking the email header info from your last message, it looks like it took 2
seconds for AOL's server to receive the message from you. It then took 6 more
seconds for it to deliver it to the nsrca server. Pretty quick, obviously no
delay here. It<BR>> rumbles around through several spam and virus checkers
at nsrca's ISP for a few seconds. Then it hits a server that's clock is 1+
hour off so who knows. Finally, NSRCA's servers shoot it to my server 1 minute
and 3 seconds after you had hit the send<BR>> button.<BR>><BR>> So it
got to me very fast. My best guess is that AOL's incoming servers were swamped
(there is a spam storm going on this weekend), they told the NSRCA server to
wait-delay a couple of times, and now your message is in email pergatory. It
will<BR>> eventually flush through.<BR>><BR>> Below is a copy of the
route list of your message that got to me. Its kind of interesting. You
read it from the bottom up. Each of the "Received:" lines is another server or
application (like virus checker) that handled the message.<BR>><BR>>
Steve Sterling<BR>> NSRCA Webteam<BR>><BR>> Received: by
tux3.sgster.dyndns.org (Postfix, from userid 501)<BR>> id 24F2E4D0E;
Sun, 6 Mar 2005 14:49:08 -0800 (PST)<BR>> Received: from
sf.mail.nxs.net (unknown [198.144.160.66])<BR>> by
tux3.sgster.dyndns.org (Postfix) with ESMTP id 9A5424D02<BR>> for
<rcsteve@tcrcm.org>; Sun, 6 Mar 2005 14:48:59 -0800 (PST)<BR>>
Received: (qmail 4499 invoked by uid 507); 6 Mar 2005 22:08:38 -0000<BR>>
Received: from unknown (HELO mail.nxs.net)
(198.144.160.60)<BR>> by 0 with SMTP; 6 Mar 2005 22:08:38
-0000<BR>> Received: from sa.mail.nxs.net (unverified [198.144.160.68]) by
nxs.net<BR>> (Rockliffe SMTPRA 6.0.9) with ESMTP id
<B0125217736@mail.nxs.net> for
<discussion@nsrca.org>;<BR>> Sun, 6 Mar 2005 17:48:14
-0500<BR>> Received: (qmail 18876 invoked by uid 507); 6 Mar 2005 23:09:20
-0000<BR>> Received: from unknown (HELO sf.mail.nxs.net)
(198.144.160.65)<BR>> by 0 with DES-CBC3-SHA encrypted SMTP; 6
Mar 2005 23:09:20 -0000<BR>> Received: (qmail 4040 invoked by uid 507); 6
Mar 2005 22:07:59 -0000<BR>> Received: from unknown (HELO vs.mail.nxs.net)
(198.144.160.64)<BR>> by 0 with SMTP; 6 Mar 2005 22:07:59
-0000<BR>> Received: from mx1a.mail.nxs.net
([198.144.167.162])<BR>> by vs.mail.nxs.net (SAVSMTP 3.1.0.29) with
SMTP id M2005030617311725724<BR>> for <discussion@nsrca.org>;
Sun, 06 Mar 2005 17:31:17 -0500<BR>> Received: (qmail 29564 invoked from
network); 6 Mar 2005 22:48:12 -0000<BR>> Received: from unknown (HELO
imo-d03.mx.aol.com) (205.188.157.35)<BR>> by mx1a.mail.nxs.net
with SMTP for <discussion@nsrca.org>; 6 Mar 2005 22:48:12 -0000<BR>>
Received: from BUDDYonRC@aol.com<BR>> by imo-d03.mx.aol.com
(mail_out_v37_r3.8.) id 8.1a4.33132eee (16633)<BR>> for
<discussion@nsrca.org>; Sun, 6 Mar 2005 17:48:06 -0500 (EST)<BR>>
From: BUDDYonRC@aol.com<BR>> Message-ID:
<1a4.33132eee.2f5ce2a5@aol.com><BR>> Date: Sun, 6 Mar 2005 17:48:05
EST<BR>> Subject: Help!!!<BR>> To: discussion@nsrca.org<BR>><BR>>
-----Original Message-----<BR>> From: discussion-request@nsrca.org
[mailto:discussion-request@nsrca.org]On Behalf Of BUDDYonRC@aol.com<BR>>
Sent: Sunday, March 06, 2005 2:48 PM<BR>> To: discussion@nsrca.org<BR>>
Subject: Help!!!<BR>><BR>><BR>> If anyone can help? I am getting mail
from everyone that mails me direct but nothing from the discussion list. I am
beginning to think I have been cut off due to recent rules change discussions
that I started.<BR>> Please let me back on I won't do it again.<BR>>
Buddy<BR>><BR>><BR>><BR>> No Steve<BR>> I am not getting
through I have been booted and when I try to sign up again I Get a reply
Journal that says I cannot be added to the discussion mailing list:
error-518979585<BR>> I dont know why or how to fix the problem. I left a
message For ED Hartly on the NSRCA site<BR>> I got ahold of AOL and reset
Spam filters they couldnt find a reason that it wont work nor can I my mail
works everywhere else.<BR>>
Buddy<BR><BR><BR><BR><BR>=================================================<BR>To
access the email archives for this list, go
to<BR>http://lists.f3a.us/pipermail/nsrca-discussion/<BR>To be removed from
this list, go to http://www.nsrca.org/discussionA.htm<BR>and follow the
instructions.<BR><BR></FONT></BLOCKQUOTE>
<DIV></DIV>
<DIV> </DIV></FONT></BODY></HTML>