On Thu, Mar 09, 2023 at 08:45:58AM -0800, Michael Peddemors via mailop wrote: > Yes, it's called 'rwhois'. Of course, linode can SWIP the larger portions, > with a clear indication of what parts of the IP space are used for what. > > AS well, you 'could' change default PTR's for segments used differently. > > At least you are asking how you can do things differently. > > I know there has been a lot of Linode 'slagging' on the list, but it isn't > as bad as some other networks. > > Now, having said that that, you are looking at the IPv6 space. Are you > planning to run email on IPv6? Many challenges ahead. > > As a customer, ask Linode to provide 'rwhois' for you. But for email, you > should stick to IPv4. Just my two bits.
I literally only tried enabling mail on my server the other day after running Tobias Fiebig's security scan test. I failed the ipv6 test so thought, well, let's enable that in sendmail and see if I can make that box green...what could possibly go wrong? Quite quickly we realized the ipv6 address of the box was on spamhaus's XBL. By 'rwhois', I think you mean running whois with an ip address versus a hostname. This is exactly how I use it to know who owns which netblock. That's how I can see Linode owns the /28. When you say "ask Linode to provide 'rwhois'", what specifically do you mean for them to do? Once that's done (if they're willing to do this for me), would spamhaus and other RBLs then know to list smaller blocks in that space? If I can get this spamhaus issue solved, why should I not just leave it in place so my mailer will talk ipv4 or ipv6? Why just stick with ipv4? I realize it's not necessary today to be able to send on ipv6 but why should I not get this working?
signature.asc
Description: PGP signature
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
