The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today. -- ED --
* Ed McCanless
The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today.
I have rec'd 42 counting up to the two copies of your post since midnight EST (Central Indiana). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today.
I got about 60, so I assume I received all mails. Please also check the reason for your double post. Since they have different "message id", they were problably mangled by a filter or indeed sent out twice. Slowly I suspect one of the router admins has fiddled with smtp fixup protocol on one of the bigger routers, or the listserver has upgraded to an incompatible version of software/settings. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com
I also received a slew of emails overnight. Looking at the headers, the list through-put from Basil to my IMAP inbox was :43 seconds, assuming everyone's time is correct. I'd look to BellSouth for the answer... (Basil replied one at 5:43 AM MST, I assume that is the one you got) On Mon, 2006-10-30 at 08:55 -0500, Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today.
-- ED --
-- Tom in NM SuSE 9.3/Evolution 7:39am up 1 day 7:20, 2 users, load average: 0.01, 0.07, 0.08 ====
Tom Patton wrote:
I also received a slew of emails overnight. Looking at the headers, the list through-put from Basil to my IMAP inbox was :43 seconds, assuming everyone's time is correct. I'd look to BellSouth for the answer... (Basil replied one at 5:43 AM MST, I assume that is the one you got)
On Mon, 2006-10-30 at 08:55 -0500, Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today.
My time (clock) is never more than 0.03 seconds out from the atomic clock. Cheers. -- I'm dangerous when I know what I'm doing.
I'm on dialup, so I manually set mine ~once a week when I think to from the Naval Clock. But the headers show UTC from you to my IMAP inbox at micro-net... ;-) On Tue, 2006-10-31 at 01:52 +1100, Basil Chupin wrote:
My time (clock) is never more than 0.03 seconds out from the atomic clock.
-- Tom in NM SuSE 9.3/Evolution 8:03am up 1 day 7:45, 2 users, load average: 0.02, 0.05, 0.07 ====
Basil Chupin wrote:
Tom Patton wrote:
I also received a slew of emails overnight. Looking at the headers, the list through-put from Basil to my IMAP inbox was :43 seconds, assuming everyone's time is correct. I'd look to BellSouth for the answer... (Basil replied one at 5:43 AM MST, I assume that is the one you got)
On Mon, 2006-10-30 at 08:55 -0500, Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post since about 8:52 P.M. (North Carolina, USA). Oops! My mind wasn't fully in gear, this should have said 8:52 P.M. Saturday. That one was from Basil Chupin, Subject: Re: [SLE] New problem, at 7:43 A.M. Mondays have been the day of normal volume, until today.
My time (clock) is never more than 0.03 seconds out from the atomic clock.
Cheers. How do you do that?
I still haven't seen Tom's reply, outside of this one from you, Basil. Will check with Bell South, but expect them to deny any blame. Thanks, -- ED --
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 13:11 -0500, Ed McCanless wrote:
Basil Chupin wrote:
My time (clock) is never more than 0.03 seconds out from the atomic clock.
How do you do that?
Probably the same way as I do it: by running the NTP daemon. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRl7itTMYHG2NR9URAoiwAJ9gADsJuNfEhAwwQi2sh12lsoihWwCfTgv0 OmWCJMNYx6CTBcUWOEGF+hg= =G7Ow -----END PGP SIGNATURE-----
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2006-10-30 at 13:11 -0500, Ed McCanless wrote:
Basil Chupin wrote:
My time (clock) is never more than 0.03 seconds out from the atomic clock.
How do you do that?
Probably the same way as I do it: by running the NTP daemon.
Yep. But as my ISP is also a ntp server I ocassionally use the 'ntpdate -u 203.12.160.2' command to check on the ntp daemon's honesty :-) . Cheers. -- I'm dangerous when I know what I'm doing.
On Mon, 2006-10-30 at 13:11 -0500, Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post
since about 8:52 P.M. (North Carolina, USA). Oops! My mind wasn't fully in gear, this should have said 8:52 P.M. Saturday. I assumed such...
I still haven't seen Tom's reply, outside of this one from you, Basil. Will check with Bell South, but expect them to deny any blame. I wonder if Basil had replied both through SuSE and directly...and you got his direct route?
I've had similar issues (not frequently) with micro-net. I know once they lost a raid drive, and it resulted in a flood of day old mail once they replaced it. Or maybe they are hunting for a DOS attacker, and blocking selective sources. It sure sounds like it is their problem, and doubtful that SuSE-E is creating the delay... (I didn't count, but there has been a fairly steady stream of list mail all day.) -- Tom in NM SuSE 9.3/Evolution 1:42pm up 1 day 13:27, 3 users, load average: 0.18, 0.24, 0.19 ====
Tom Patton wrote:
On Mon, 2006-10-30 at 13:11 -0500, Ed McCanless wrote:
The mail problem suddenly got worse here. I have received only one post
since about 8:52 P.M. (North Carolina, USA). Oops! My mind wasn't fully in gear, this should have said 8:52 P.M. Saturday. I assumed such... I still haven't seen Tom's reply, outside of this one from you, Basil. Will check with Bell South, but expect them to deny any blame. I wonder if Basil had replied both through SuSE and directly...and you got his direct route?
I never reply directly--well, only in exceptional circumstances but none exist at the moment.
I've had similar issues (not frequently) with micro-net. I know once they lost a raid drive, and it resulted in a flood of day old mail once they replaced it. Or maybe they are hunting for a DOS attacker, and blocking selective sources. It sure sounds like it is their problem, and doubtful that SuSE-E is creating the delay...
This is most likely just a coincidence but at the times when I've had mail problems with this list last week I got the feeling that they started at around 0700 hours Zurich time.
(I didn't count, but there has been a fairly steady stream of list mail all day.)
No problems at this end for several days now (touch wood). Cheers. -- I'm dangerous when I know what I'm doing.
participants (6)
-
Basil Chupin -
Carlos E. R. -
Ed McCanless -
Patrick Shanahan -
Sandy Drobic -
Tom Patton