<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Sorry about the bad examples, but I remember contacting both about issues with SPF multiple times.  They both have seemed have to fixed things at least searching my logs for the last week.  Most of my customers have had to whitelist them though for past issues. It’s also <a href="http://ezpassnj.com" class="">ezpassnj.com</a> for the NJ collection.  Point still stands, assume incompetence over malice.<div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Sincerely,</div><div class=""><br class=""></div><div class="">Eric Tykwinski</div><div class="">TrueNet, Inc.</div><div class="">P: 610-429-8300</div></div>

</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Aug 23, 2022, at 10:20 PM, Eric Tykwinski <<a href="mailto:eric-list@truenet.com" class="">eric-list@truenet.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Bill,</div><div class=""><br class=""></div>Not only that, did they even follow their own rules, I’ve been fighting with <a href="http://septa.org/" class="">septa.org</a>, the Pennsylvania train authority, and <a href="http://easypassnj.com/" class="">easypassnj.com</a>, the New Jersey transit toll collectors about invalid SPF records for years, and they literally don’t give a shit.  If they say to put it in spam, well than that is their own fault.<div class=""><div class=""><br class=""><div class="">
<div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Sincerely,</div><div class=""><br class=""></div><div class="">Eric Tykwinski</div><div class="">TrueNet, Inc.</div><div class="">P: 610-429-8300</div></div>

</div>
<div class=""><br class=""><blockquote type="cite" class=""><div class="">On Aug 23, 2022, at 10:00 PM, Suresh Ramasubramanian <<a href="mailto:ops.lists@gmail.com" class="">ops.lists@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">

<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">

<div class="">
<div class="">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">Without saying why the mail was blocked (dumb content filter looking for porn? a spamhaus listing because the police server was hacked? something else?) that’s not going to help too much.</div>
<div dir="ltr" class=""><br class="">
</div>
<div dir="ltr" class="">I’ve been spam filtering stuff at large providers since the late 90s and it never gets any easier to block 100% spam or let 100% legit mail through.</div>
<div dir="ltr" class=""><br class="">
</div>
<div dir="ltr" class="">—srs</div>
</div>
</div>
<div id="ms-outlook-mobile-signature" class="">
<div class=""><br class="">
</div>
<div style="direction: ltr;" class="">--srs</div>
</div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1" class="">
<div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size:11pt" class=""><b class="">From:</b> NANOG <<a href="mailto:nanog-bounces+ops.lists=gmail.com@nanog.org" class="">nanog-bounces+ops.lists=gmail.com@nanog.org</a>> on behalf of William Herrin <<a href="mailto:bill@herrin.us" class="">bill@herrin.us</a>><br class="">
<b class="">Sent:</b> Wednesday, August 24, 2022 7:03:52 AM<br class="">
<b class="">To:</b> <a href="mailto:nanog@nanog.org" class="">nanog@nanog.org</a> <<a href="mailto:nanog@nanog.org" class="">nanog@nanog.org</a>><br class="">
<b class="">Subject:</b> email spam</font>
<div class=""> </div>
</div>
<div class="BodyFragment"><font size="2" class=""><span style="font-size:11pt;" class="">
<div class="PlainText">Hello,<br class="">
<br class="">
To folks at places like Google and Godaddy which have gotten, shall we<br class="">
say, overzealous about preventing spam from entering their systems,<br class="">
consider the risk:<br class="">
<br class="">
<a href="https://www.washingtonpost.com/education/2022/08/23/fairfax-county-counselor-solicitation-minor/" class="">https://www.washingtonpost.com/education/2022/08/23/fairfax-county-counselor-solicitation-minor/</a><br class="">
<br class="">
"Chesterfield County police said emails notifying Fairfax County<br class="">
Public Schools that an employee was arrested and charged with<br class="">
soliciting prostitution from a minor were not delivered to the school<br class="">
system."<br class="">
<br class="">
Long story short, the pedo kept his school job another year and a half.<br class="">
<br class="">
There was once a time when both the outbound emails and the bounce<br class="">
messages when they failed... worked. It was a spammy place but the<br class="">
important emails got through.<br class="">
<br class="">
Regards,<br class="">
Bill Herrin<br class="">
</div>
</span></font></div>
</div>

</div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></div></body></html>