<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr">Hi Brandon,</div><div dir="ltr"><br></div><div dir="ltr">Your next actions are to level up the security of your network, your organization, and your team. I’ll craft up a post with a checklist you can use. </div><div dir="ltr"><br></div><div dir="ltr">If you don’t do this, then people on your team, your company, and your customers will continue to be “danger do not go there” listed. Spamhaus is not the only one providing easy tools to help organizations deploy “danger do not go there” list. </div><div dir="ltr"><br></div><div dir="ltr">Step 1 on the list …. Deploy Exploitable Port Filtering on the edge of your network ….</div><div dir="ltr"><br></div><div dir="ltr"><div style="display: block;" class=""><div style="-webkit-user-select: all; -webkit-user-drag: element; display: inline-block;" class="apple-rich-link" draggable="true" role="link" data-url="https://www.senki.org/operators-security-toolkit/filtering-exploitable-ports-and-minimizing-risk-to-and-from-your-customers/"><a style="border-radius:10px;font-family:-apple-system, Helvetica, Arial, sans-serif;display:block;-webkit-user-select:none;width:300px;user-select:none;-webkit-user-modify:read-only;user-modify:read-only;overflow:hidden;text-decoration:none;" class="lp-rich-link" rel="nofollow" href="https://www.senki.org/operators-security-toolkit/filtering-exploitable-ports-and-minimizing-risk-to-and-from-your-customers/" dir="ltr" role="button" draggable="false" width="300"><table style="table-layout:fixed;border-collapse:collapse;width:300px;background-color:#E9E9EB;font-family:-apple-system, Helvetica, Arial, sans-serif;" class="lp-rich-link-emailBaseTable" cellpadding="0" cellspacing="0" border="0" width="300"><tbody><tr><td vertical-align="center" align="center"><img style="width:300px;filter:brightness(0.97);height:145px;" width="300" height="145" draggable="false" class="lp-rich-link-mediaImage" alt="Direction20Threats-2.png-2.png" src="cid:09A69C59-B1BF-4249-983C-5180A519C067"></td></tr><tr><td vertical-align="center"><table bgcolor="#E9E9EB" cellpadding="0" cellspacing="0" width="300" style="font-family:-apple-system, Helvetica, Arial, sans-serif;table-layout:fixed;background-color:rgba(233, 233, 235, 1);" class="lp-rich-link-captionBar"><tbody><tr><td style="padding:8px 0px 8px 0px;" class="lp-rich-link-captionBar-textStackItem"><div style="max-width:100%;margin:0px 16px 0px 16px;overflow:hidden;" class="lp-rich-link-captionBar-textStack"><div style="word-wrap:break-word;font-weight:500;font-size:12px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-topCaption-leading"><a rel="nofollow" href="https://www.senki.org/operators-security-toolkit/filtering-exploitable-ports-and-minimizing-risk-to-and-from-your-customers/" style="text-decoration: none" draggable="false"><font color="#000000" style="color: rgba(0, 0, 0, 1);">Filtering Exploitable Ports and Minimizing Risk from the Internet and from Your Customers</font></a></div><div style="word-wrap:break-word;font-weight:400;font-size:11px;overflow:hidden;text-overflow:ellipsis;text-align:left;" class="lp-rich-link-captionBar-textStack-bottomCaption-leading"><a rel="nofollow" href="https://www.senki.org/operators-security-toolkit/filtering-exploitable-ports-and-minimizing-risk-to-and-from-your-customers/" style="text-decoration: none" draggable="false"><font color="#A2A2A9" style="color: rgba(60, 60, 67, 0.6);">senki.org</font></a></div></div></td></tr></tbody></table></td></tr></tbody></table></a></div></div><br></div><div dir="ltr">The other steps I’ll put into a blog post. </div><div dir="ltr"><br></div><div dir="ltr">Barry</div><div dir="ltr"><br><blockquote type="cite">On Mar 21, 2023, at 07:10, Brandon Zhi <Brandon@huize.asia> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="auto">Our person in charge has consulted with their previous person in charge, and their response is this.<div dir="auto"><br></div><div dir="auto">"problem began long before February 18th. The problem was that in 2022 they added our prefix <a href="http://87.251.79.0/24">87.251.79.0/24</a> to the black list, and said that if there were no complaints for 30-60 days, the record would be deleted. we agreed, almost a year has passed, the record has remained. They tried several times to put pressure on our providers, but we always record any termination of the contract with large fines, not a single provider has done this, we pay a lot of money for the Internet, and no one wants to take risks, now spamhouse pressure on"</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Actually, I didn’t know what a spamhouse was before this month, until we announced the IP in vultr </div><div dir="auto"><br></div><div dir="auto">They claim they've been working on the issue, but I've found that they don't respond to emails very well (I can only judge from this). Usually though, I tell them to take down the content, and then the content gets a different provider.</div><div dir="auto"><br></div><div dir="auto">Also, it's not clear to me whether we need to reply to emails sent from the spamhouse system. They claim that they took care of the content, but I personally think it's because they didn't respond to the email that spamhouse thinks they're not doing it</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On 2023年3月21日周二 上午5:15 Randy Bush <<a href="mailto:randy@psg.com">randy@psg.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">>> I don't think any ISP would reject an IP that is on the Spamhaus<br>
>> list.<br>
> you, clearly, have been living under several rocks for a very long<br>
> time.<br>
<br>
we reject automagically on spamhaus, <a href="http://mail-abuse.org" rel="noreferrer noreferrer" target="_blank">mail-abuse.org</a>, and sorbs. really<br>
appreciate their services.<br>
<br>
randy<br>
</blockquote></div>
</div></blockquote></body></html>