<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">FYI geek team I received it too.<br><br><div dir="ltr"><div><span style="background-color: rgba(255, 255, 255, 0);">Ms. Lady Benjamin PD Cannon, ASCE<br class="">6x7 Networks & 6x7 Telecom, LLC <br class="">CEO <br class=""><a href="mailto:ben@6by7.net" class="">ben@6by7.net</a><br class="">"The only fully end-to-end encrypted global telecommunications company in the world.”</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br class="">FCC License KJ6FJJ<br class=""></span></div><span style="background-color: rgba(255, 255, 255, 0);"><br></span><div><span style="background-color: rgba(255, 255, 255, 0);">Sent from my iPhone via RFC1149.</span></div></div><div dir="ltr"><br><blockquote type="cite">On Jan 13, 2021, at 4:28 PM, Sabri Berisha <sabri@cluecentral.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>----- On Jan 13, 2021, at 2:22 PM, Bryan Fields Bryan@bryanfields.net wrote:</span><br><span></span><br><span>Hi Bryan,</span><br><span></span><br><blockquote type="cite"><span>What you can do is when you notice these, email geeks@nanog with the full</span><br></blockquote><blockquote type="cite"><span>email including headers immediately. We can then cross check it against new</span><br></blockquote><blockquote type="cite"><span>signups. I wish there was a more scientific way to process it.</span><br></blockquote><span></span><br><span>The first time I got it, I sent this to support@donotpay.com:</span><br><span></span><br><blockquote type="cite"><span>I received this email in, what appears to be, reply to a post I made on NANOG.</span><br></blockquote><span></span><br><blockquote type="cite"><span>Needless to say, I never signed up for this. I did not even know you existed.</span><br></blockquote><blockquote type="cite"><span>Since you do add "support@donotpay.com" in your email, I assume this is a</span><br></blockquote><blockquote type="cite"><span>honest mistake, and you'll be happy that I'm contacting you and will be fixing</span><br></blockquote><blockquote type="cite"><span>it immediately.</span><br></blockquote><span></span><br><blockquote type="cite"><span>Obviously, further unsolicited emails will result in ... a different approach</span><br></blockquote><blockquote type="cite"><span>taken.</span><br></blockquote><span></span><br><span>A few days later, I got the same again, and contacted their hosting provider,</span><br><span>Mailgun (while CCing support@donotpay.com), with the following:</span><br><span></span><br><blockquote type="cite"><span>I've received, multiple times, email such as below after posting to the North</span><br></blockquote><blockquote type="cite"><span>American Network Operators Group (NANOG) email list. I've tried contacting</span><br></blockquote><blockquote type="cite"><span>support@donotpay.com (ticket #13202), but they seem oblivious to the issue</span><br></blockquote><blockquote type="cite"><span>and asked me to unsubscribe.</span><br></blockquote><span></span><br><blockquote type="cite"><span>Please educate your customer. Alternatively, I will contact Amazon, who seem</span><br></blockquote><blockquote type="cite"><span>to advertise your IP space.</span><br></blockquote><span></span><br><blockquote type="cite"><span>161.38.200.0/22 *[BGP/170] 00:51:18, localpref 150</span><br></blockquote><blockquote type="cite"><span> AS path: 53356 60011 3356 16509 I, validation-state: unverified</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>to 195.16.87.249 via ge-0/0/6.0</span><br></blockquote></blockquote><span></span><br><blockquote type="cite"><span>Headers are as follows:</span><br></blockquote><span></span><br><span>[snip]</span><br><span></span><br><span>I did not even get a reply on that. So, as promised, the third time I was</span><br><span>spammed, I took the liberty of contacting AWS. They responded with:</span><br><span></span><br><blockquote type="cite"><span>This is a follow up regarding the abusive content or activity report that you</span><br></blockquote><blockquote type="cite"><span>submitted to AWS. We have investigated this report, and have taken steps to</span><br></blockquote><blockquote type="cite"><span>mitigate the reported abusive content or activity.</span><br></blockquote><span></span><br><span>But of course, nothing changed.</span><br><span></span><br><span>This goes a lot further than someone accidentally subscribing. So, it seems</span><br><span>that there are few options other than to simply block mail from that /22. </span><br><span></span><br><span>Thanks,</span><br><span></span><br><span>Sabri</span><br></div></blockquote></body></html>