<html><head></head><body>well that explains a lot.<br><br>For their own sake I hope they shape up - but I doubt they will.<br><br><div class="gmail_quote">On 20 March 2023 20:24:09 UTC, ayang@august.tw wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre dir="auto" class="k9mail">Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to RIR policy violations, which include prohibited sharing of ASNs with third parties, IP hijacking, and malicious path prepending.<br><br>Given this history, it is not surprising that Spamhaus would blacklist IP addresses associated with their ASN. In my opinion, such action is well-justified.<br><br>Best regards,<br>August Yang<br><br>On 2023-03-20 15:32, Collider wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Why do two different companies with what should be independent<br>networks share an AS number?<br><br>On 20 March 2023 18:20:08 UTC, Aaron Wendel<br><aaron@wholesaleinternet.net> wrote:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">The solution to your problem is to terminate the customer causing<br>the abuse, in this case 62yun.com. Once you do that I'm sure<br>Spamhaus will stop listing all your IPs.<br><br>Aaron<br><br>On 3/20/2023 6:54 AM, Brandon Zhi wrote:<br><br>It seems you've reached the point that they ignore specific<br>prefixes and set every prefix you are advertising as criminal.<br><br>*<br>*<br>Our sponsor (LIR) 62yun.com <<a href="http://62yun.com">http://62yun.com</a>>, they have 2 prefixes<br>for VPS/Dedicated Server using our ASN.*<br>*<br>62yun did receive a lot of complaints, but as far as I know they<br>have been handling them (their head said their team is not good at<br>English and so they did not reply emails)<br>For me, I cannot reply to all emails for them, since I don't have<br>that much time. I also need to work for my company.<br><br>As I understand it, most things at Spamhaus are manual<br>determinations.<br>You click on "show details" and they give you a list of timestamped<br>report IDs, each with a 1-line description of the reviewer's<br>assessment of the fault.<br><br>I checked <a href="https://check.spamhaus.org/listed/?searchterm=46.23.100.0">https://check.spamhaus.org/listed/?searchterm=46.23.100.0</a><br>and the reason they gave us was simple, saying our not willing to<br>handle abuse. but we stressed with them many times that we are 2<br>different companies. We also do not have the authority to handle<br>these complaints, but we will alert 62yun.com <<a href="http://62yun.com">http://62yun.com</a>>.<br><br>But they still intend to blacklist all the prefixes under our ORG<br>ID, even if the user is not us.<br><br>Based on my past experiences, Spamhaus is rather gracious at<br>first, but if you ignore them, they will start blocking you en<br>masse. About 10 years ago, I worked for a datacenter/NSP and<br>personally handled all Spamhaus complaints, and as soon as I left<br>to go to another company (and the company stopped taking care of<br>the complaints), Spamhaus blocked every single one of their IPs<br>until they committed to actually handling the complaints again.<br><br>This has little impact on 62yun.com <<a href="http://62yun.com">http://62yun.com</a>>'s VPS<br>business, and my feeling is that if someone uses their VPS to build<br>a mail server those emails that are sent from this server may be<br>rejected.<br><br>However, we are recently building a CDN for one of our partners (a<br>social media company), and we need to use a provider like vultr,<br>which is not really an IP Transit provider, to announce prefixes,<br>however, they reject prefixes on the Spamhaus list.<br><br>I don't think any ISP would reject an IP that is on the Spamhaus<br>list.<br><br>*Brandon Zhi*<br>HUIZE LTD<br><br>www.huize.asia <<a href="https://huize.asia/">https://huize.asia/</a>>| www.ixp.su<br><<a href="https://www.ixp.su/">https://www.ixp.su/</a>> | Twitter<br><br>This e-mail and any attachments or any reproduction of this e-mail<br>in whatever manner are confidential and for the use of the<br>addressee(s) only. HUIZE LTD can’t take any liability and<br>guarantee of the text of the email message and virus.<br><br>On Mon, 20 Mar 2023 at 02:29, Tim Burke <tim@mid.net> wrote:<br><br>Have you received complaints from Spamhaus in the past? If so,<br>have you acted on them in a timely manner?<br><br>Based on my past experiences, Spamhaus is rather gracious at<br>first, but if you ignore them, they will start blocking you en<br>masse. About 10 years ago, I worked for a datacenter/NSP and<br>personally handled all Spamhaus complaints, and as soon as I left<br>to go to another company (and the company stopped taking care of<br>the complaints), Spamhaus blocked every single one of their IPs<br>until they committed to actually handling the complaints again.<br><br>V/r<br>Tim<br><br>On Mar 18, 2023, at 8:57 AM, Brandon Zhi <Brandon@huize.asia><br>wrote:<br><br>Hello guy,<br><br>We recently discovered that any IP address announced by our ASN<br>is blacklisted by Spamhaus, even if we only announced it but not<br>use it.<br><br>I would like to ask if this is manually set by Spamhaus or is the<br>system misjudgment? Has anyone encountered the same situation as us?<br><br>Best,<br><br>*Brandon Zhi*<br>HUIZE LTD<br><br>www.huize.asia <<a href="https://huize.asia/">https://huize.asia/</a>>| www.ixp.su<br><<a href="https://www.ixp.su/">https://www.ixp.su/</a>> | Twitter<br><br>This e-mail and any attachments or any reproduction of this<br>e-mail in whatever manner are confidential and for the use of the<br>addressee(s) only. HUIZE LTD can’t take any liability and<br>guarantee of the text of the email message and virus.<br></blockquote><br>--<br>Sent from my Android device with K-9 Mail. Please excuse my brevity.<br></blockquote></pre></blockquote></div><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></body></html>