<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Fair callout, as my employer does the same... which is one of many reasons why I use a personal mail account for lists.</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Outages-discussion <outages-discussion-bounces@outages.org> on behalf of Justin H. via Outages-discussion <outages-discussion@outages.org><br>
<b>Sent:</b> Friday, February 23, 2024 10:36 AM<br>
<b>To:</b> Outages Discussion <outages-discussion@outages.org><br>
<b>Subject:</b> Re: [Outages-discussion] Outages lists configuration thoughts</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">It's also possible (like my corporate account) that their signature
<br>
isn't under their control. It may be added by their outbound mail <br>
exchanger, not their client. This is one of the primary reasons I have <br>
a dedicated account for mailing lists.<br>
<br>
Justin H.<br>
<br>
Tim Burke via Outages-discussion wrote:<br>
> As a semi-lurker as well, IMHO the hilariously long signatures are <br>
> either caused by someone being too lazy to remove it from their <br>
> response, or what I consider a perceived feeling of over importance... <br>
> if I were bonkers enough to have a 48 line signature, I still wouldn't <br>
> want my entire email signature, including cell phone, direct line, <br>
> direct fax, mailing address, blood type, and mother's maiden name on a <br>
> sesame seed bun to go out to thousands of people... but I don't think <br>
> Mailman has a fix for that. 🙂<br>
> ------------------------------------------------------------------------<br>
> *From:* Outages-discussion <outages-discussion-bounces@outages.org> on <br>
> behalf of Shaun Potts via Outages-discussion <br>
> <outages-discussion@outages.org><br>
> *Sent:* Friday, February 23, 2024 9:06 AM<br>
> *To:* Josh Luthman <josh@imaginenetworksllc.com><br>
> *Cc:* Outages Discussion <outages-discussion@outages.org><br>
> *Subject:* Re: [Outages-discussion] Outages lists configuration thoughts<br>
> Hopefully I'm not out of place here, but I want to just say as a 99% <br>
> lurker and observer that the most obnoxious thing about reading all <br>
> the back and forth here is people sending 5 word emails with 83 lines <br>
> of signature. Can we trim that off or something?<br>
><br>
> On Fri, Feb 23, 2024 at 9:59 AM Josh Luthman via Outages-discussion <br>
> <outages-discussion@outages.org <br>
> <<a href="mailto:outages-discussion@outages.org">mailto:outages-discussion@outages.org</a>>> wrote:<br>
><br>
> Myself and others feel like these posts end up generating way more<br>
> noise than just letting it go. I'm not sure why it's so hard to<br>
> just swipe right rather than get frustrated with it. I don't<br>
> think anything outages@ is urgent enough to put it on mute or<br>
> something?<br>
><br>
> On Fri, Feb 23, 2024 at 9:53 AM Andy Ringsmuth via<br>
> Outages-discussion <outages-discussion@outages.org<br>
> <<a href="mailto:outages-discussion@outages.org">mailto:outages-discussion@outages.org</a>>> wrote:<br>
><br>
> Good morning all,<br>
><br>
> Yesterday’s AT&T flub again showed the need for us all to be<br>
> much more deliberate about how we use the outages and<br>
> outages-discussion lists.<br>
><br>
> I’m not sure off the top of my head who is responsible for the<br>
> overall setup on these lists, or I’d reach out to that<br>
> person/people directly.<br>
><br>
> Having said that, can we PLEASE consider setting the “Reply<br>
> To:” default for the outages list to be outages-discussion?<br>
> That is definitely an option within the Mailman list<br>
> configuration.<br>
><br>
> That would eliminate an insane number of extraneous (and very<br>
> very long) messages for those of us who use the outages list<br>
> as a notification source for immediate attention, which I<br>
> believe to be the intent of that list. I’m looking at one<br>
> message posted to outages yesterday that was a reply to a<br>
> reply to a reply to a reply to a digest message. 513 lines of<br>
> text!<br>
><br>
><br>
> Thank you for the consideration.<br>
><br>
> ----<br>
> Andy Ringsmuth<br>
> 5609 Harding Drive<br>
> Lincoln, NE 68521-5831<br>
> (402) 202-1230<br>
> andy@andyring.com <<a href="mailto:andy@andyring.com">mailto:andy@andyring.com</a>><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> Outages-discussion@outages.org<br>
> <<a href="mailto:Outages-discussion@outages.org">mailto:Outages-discussion@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> Outages-discussion@outages.org <<a href="mailto:Outages-discussion@outages.org">mailto:Outages-discussion@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> Outages-discussion@outages.org<br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
<br>
_______________________________________________<br>
Outages-discussion mailing list<br>
Outages-discussion@outages.org<br>
<a href="https://puck.nether.net/mailman/listinfo/outages-discussion">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
</div>
</span></font></div>
</body>
</html>