<div dir="ltr">Yep. I just got informed that we've been doing the same for years.... I rarely ever hit "display images" in emails so I've never seen it before. Just had an interesting discussion with my boss - might get it removed in the name of cybersecurity, as it is the sort of thing that could be easily cloned with phishing/malware links that could be clicked on by our customers. <div><br></div><div>Until then, I've been told to live with it - like I have been for most of the past decade, apparently. </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 23, 2024 at 8:43 AM Tim Burke via Outages-discussion <<a href="mailto:outages-discussion@outages.org">outages-discussion@outages.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg7895793089054472733">
<div dir="ltr">
<div 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="m_7895793089054472733appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="m_7895793089054472733divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Outages-discussion <<a href="mailto:outages-discussion-bounces@outages.org" target="_blank">outages-discussion-bounces@outages.org</a>> on behalf of Justin H. via Outages-discussion <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a>><br>
<b>Sent:</b> Friday, February 23, 2024 10:36 AM<br>
<b>To:</b> Outages Discussion <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a>><br>
<b>Subject:</b> Re: [Outages-discussion] Outages lists configuration thoughts</font>
<div> </div>
</div>
<div><font size="2"><span style="font-size:11pt">
<div>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 <<a href="mailto:outages-discussion-bounces@outages.org" target="_blank">outages-discussion-bounces@outages.org</a>> on <br>
> behalf of Shaun Potts via Outages-discussion <br>
> <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a>><br>
> *Sent:* Friday, February 23, 2024 9:06 AM<br>
> *To:* Josh Luthman <<a href="mailto:josh@imaginenetworksllc.com" target="_blank">josh@imaginenetworksllc.com</a>><br>
> *Cc:* Outages Discussion <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a>><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>
> <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a> <br>
> <<a href="mailto:outages-discussion@outages.org" target="_blank">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 <<a href="mailto:outages-discussion@outages.org" target="_blank">outages-discussion@outages.org</a><br>
> <<a href="mailto:outages-discussion@outages.org" target="_blank">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>
> <a href="mailto:andy@andyring.com" target="_blank">andy@andyring.com</a> <<a href="mailto:andy@andyring.com" target="_blank">mailto:andy@andyring.com</a>><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> <a href="mailto:Outages-discussion@outages.org" target="_blank">Outages-discussion@outages.org</a><br>
> <<a href="mailto:Outages-discussion@outages.org" target="_blank">mailto:Outages-discussion@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> <a href="mailto:Outages-discussion@outages.org" target="_blank">Outages-discussion@outages.org</a> <<a href="mailto:Outages-discussion@outages.org" target="_blank">mailto:Outages-discussion@outages.org</a>><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
><br>
><br>
> _______________________________________________<br>
> Outages-discussion mailing list<br>
> <a href="mailto:Outages-discussion@outages.org" target="_blank">Outages-discussion@outages.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
<br>
_______________________________________________<br>
Outages-discussion mailing list<br>
<a href="mailto:Outages-discussion@outages.org" target="_blank">Outages-discussion@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
</div>
</span></font></div>
</div>
_______________________________________________<br>
Outages-discussion mailing list<br>
<a href="mailto:Outages-discussion@outages.org" target="_blank">Outages-discussion@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages-discussion" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br>
</div></blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div style="font-size:small">Jeff Shultz<br></div><div style="font-size:small">Central Office Technician </div><div style="font-size:small">SCTC</div><div style="font-size:small">(503) 769-2125</div><div><font size="4" face="arial black, sans-serif" color="#0000ff" style="background-color:rgb(243,243,243)">Go Big Ask for Gig</font></div></div></div></div></div>
<br>
<span style="font-size:1.3em">Like us on Social Media for News, Promotions, and other information!!</span><div><span style="font-size:1.3em"><br></span></div><div><span style="font-size:1.3em"> </span><a href="https://www.facebook.com/SCTCWEB/" target="_blank"><img src="https://cdn0.iconfinder.com/data/icons/free-social-media-set/24/facebook-32.png"></a> <a href="https://www.instagram.com/sctc_sctc/" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/follow-me/256/Instagram-32.png" alt="https://www.instagram.com/sctc_sctc/"></a> <a href="https://www.yelp.com/biz/sctc-stayton-3" target="_blank"><img src="https://cdn2.iconfinder.com/data/icons/social-media-2142/192/Yelp-32.png"></a> <a href="https://www.youtube.com/c/sctcvideos" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/free-social-icons/67/youtube_circle_color-32.png"></a><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><i style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><b><font face="arial" size="1">*** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ***</font></b></i></div></div>