Send Outages-discussion mailing list submissions to
        outages-discussion@outages.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
        outages-discussion-requ...@outages.org

You can reach the person managing the list at
        outages-discussion-ow...@outages.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."


Today's Topics:

   1. Re: [EXTERNAL] Re:  Main list slow again
      (Chapman, Brad (NBCUniversal))
   2. Re: [EXTERNAL] Re:  Main list slow again (Jay R. Ashworth)
   3. Re: [EXTERNAL] Re:  Main list slow again
      (Chapman, Brad (NBCUniversal))


----------------------------------------------------------------------

Message: 1
Date: Fri, 22 Apr 2022 05:49:15 +0000
From: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
To: Grant Taylor <gtay...@tnetconsulting.net>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [EXTERNAL] Re:  Main list slow again
Message-ID: <e7993511-6bcd-413e-865a-242033765...@nbcuni.com>
Content-Type: text/plain; charset="utf-8"

Test reply (10:49pm PST)

?Sent from my iPhone

> On Apr 21, 2022, at 8:16 PM, Grant Taylor <gtay...@tnetconsulting.net> wrote:
> 
> ?On 4/21/22 8:52 PM, Andy Ringsmuth wrote:
>> For anyone interested, it looks like there is still sluggishness inherent to 
>> the main outages@ list. A 10-minute delay, appears to be 
>> repeatable/reproducible.
> 
> I don't know about puck.nether.net to Gmail, but the ~8 minute delay between 
> Received: headers from puck.nether.net itself seems ... conspicuous to me.
> 
> Additional data:
> 
> The message that I'm replying to seems to have a much shorter delay:
> 
> Received: from puck.nether.net (localhost [IPv6:::1])
>    ... by puck.nether.net ...
>    Thu, 21 Apr 2022 22:55:05 -0400 (EDT)
> 
> Received: from buffalo.ash.relay.mailchannels.net
>    ... by puck.nether.net ...
>    Thu, 21 Apr 2022 22:52:06 -0400 (EDT)
> 
> 
> 
> -- 
> Grant. . . .
> unix || die
> 
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion

------------------------------

Message: 2
Date: Fri, 22 Apr 2022 13:11:45 +0000 (UTC)
From: "Jay R. Ashworth" <j...@baylink.com>
To: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
Cc: Grant Taylor <gtay...@tnetconsulting.net>,
        outages-discussion@outages.org
Subject: Re: [Outages-discussion] [EXTERNAL] Re:  Main list slow again
Message-ID: <426643814.1231.1650633105252.javamail.zim...@baylink.com>
Content-Type: text/plain; charset=utf-8

The timestamp on this in my mailbox was 0149EDT.

That sounds like a winner to me.

----- Original Message -----
> From: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
> To: "Grant Taylor" <gtay...@tnetconsulting.net>
> Cc: outages-discussion@outages.org
> Sent: Friday, April 22, 2022 1:49:15 AM
> Subject: Re: [Outages-discussion] [EXTERNAL] Re:  Main list slow again

> Test reply (10:49pm PST)
> 
> ?Sent from my iPhone
> 
>> On Apr 21, 2022, at 8:16 PM, Grant Taylor <gtay...@tnetconsulting.net> wrote:
>> 
>> ?On 4/21/22 8:52 PM, Andy Ringsmuth wrote:
>>> For anyone interested, it looks like there is still sluggishness inherent 
>>> to the
>>> main outages@ list. A 10-minute delay, appears to be 
>>> repeatable/reproducible.
>> 
>> I don't know about puck.nether.net to Gmail, but the ~8 minute delay between
>> Received: headers from puck.nether.net itself seems ... conspicuous to me.
>> 
>> Additional data:
>> 
>> The message that I'm replying to seems to have a much shorter delay:
>> 
>> Received: from puck.nether.net (localhost [IPv6:::1])
>>    ... by puck.nether.net ...
>>    Thu, 21 Apr 2022 22:55:05 -0400 (EDT)
>> 
>> Received: from buffalo.ash.relay.mailchannels.net
>>    ... by puck.nether.net ...
>>    Thu, 21 Apr 2022 22:52:06 -0400 (EDT)
>> 
>> 
>> 
>> --
>> Grant. . . .
>> unix || die
>> 
>> _______________________________________________
>> Outages-discussion mailing list
>> Outages-discussion@outages.org
>> https://puck.nether.net/mailman/listinfo/outages-discussion
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion

-- 
Jay R. Ashworth                  Baylink                       j...@baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates       http://www.bcp38.info          2000 Land Rover DII
St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647 1274


------------------------------

Message: 3
Date: Fri, 22 Apr 2022 16:52:26 +0000
From: "Chapman, Brad (NBCUniversal)" <brad.chap...@nbcuni.com>
To: Grant Taylor <gtay...@tnetconsulting.net>
Cc: "outages-discussion@outages.org" <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [EXTERNAL] Re:  Main list slow again
Message-ID:
        
<by5pr14mb34139c6304c900afaaba528aeb...@by5pr14mb3413.namprd14.prod.outlook.com>
        
Content-Type: text/plain; charset="utf-8"

I just checked my email this morning...



Sent: Fri, 22 Apr 2022 05:49:15 +0000

Received: Fri, 22 Apr 2022 05:51:10 +0000

Round trip: 1:55

-Brad

From: Outages-discussion <outages-discussion-boun...@outages.org> on behalf of 
Chapman, Brad (NBCUniversal) <brad.chap...@nbcuni.com>
Date: Thursday, April 21, 2022 at 10:51 PM
To: Grant Taylor <gtay...@tnetconsulting.net>
Cc: outages-discussion@outages.org <outages-discussion@outages.org>
Subject: Re: [Outages-discussion] [EXTERNAL] Re: Main list slow again
Test reply (10:49pm PST)

?Sent from my iPhone

> On Apr 21, 2022, at 8:16 PM, Grant Taylor <gtay...@tnetconsulting.net> wrote:
>
> ?On 4/21/22 8:52 PM, Andy Ringsmuth wrote:
>> For anyone interested, it looks like there is still sluggishness inherent to 
>> the main outages@ list. A 10-minute delay, appears to be 
>> repeatable/reproducible.
>
> I don't know about puck.nether.net to Gmail, but the ~8 minute delay between 
> Received: headers from puck.nether.net itself seems ... conspicuous to me.
>
> Additional data:
>
> The message that I'm replying to seems to have a much shorter delay:
>
> Received: from puck.nether.net (localhost [IPv6:::1])
>    ... by puck.nether.net ...
>    Thu, 21 Apr 2022 22:55:05 -0400 (EDT)
>
> Received: from buffalo.ash.relay.mailchannels.net
>    ... by puck.nether.net ...
>    Thu, 21 Apr 2022 22:52:06 -0400 (EDT)
>
>
>
> --
> Grant. . . .
> unix || die
>
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion@outages.org
> https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!9Nreewt7voLKgVNxeJDI_GegDFKjt4D0fmHwoebuY23YVpbcqIt_2eJC-n8f9W0Gzw$<https://urldefense.com/v3/__https:/puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!9Nreewt7voLKgVNxeJDI_GegDFKjt4D0fmHwoebuY23YVpbcqIt_2eJC-n8f9W0Gzw$>
_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!9Nreewt7voLKgVNxeJDI_GegDFKjt4D0fmHwoebuY23YVpbcqIt_2eJC-n8f9W0Gzw$<https://urldefense.com/v3/__https:/puck.nether.net/mailman/listinfo/outages-discussion__;!!PIZeeW5wscynRQ!9Nreewt7voLKgVNxeJDI_GegDFKjt4D0fmHwoebuY23YVpbcqIt_2eJC-n8f9W0Gzw$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/outages-discussion/attachments/20220422/8afb3a89/attachment.htm>

------------------------------

Subject: Digest Footer

_______________________________________________
Outages-discussion mailing list
Outages-discussion@outages.org
https://puck.nether.net/mailman/listinfo/outages-discussion


------------------------------

End of Outages-discussion Digest, Vol 146, Issue 2
**************************************************

Reply via email to