I've resolved this now. Thanks to Matthew Stith for pointing out that Spamhaus's largest ipv6 blocks are indeed /64 and not /32.
Oddly, today I plainly see the spamhaus listing the /64 and not the /32 I saw yesterday. Did something change??? I am pretty sure I wasn't imagining things and pretty sure I copypasted that 2600:3c02::/32 from the 'Why was this IP listed?' section. Ahh well. What I did: My linodes have a /128 address (within a shared /64) and a separate /64 block. The /128 clearly has bad network neighbors and there's nothing I can do about that. I spent the day changing the ipv6 on these linodes to first addr in the separate /64 block. That block on all my servers is clean, not in any blacklists. I did ask Linode if they'd do rwhois on my /64 blocks but said they don't do that at this time but said I was not the only one who had asked for that and they said they added my request to their internal feature request. So maybe one day... Thanks also to Grant Taylor who provided some insite and some encouragement to persiste in getting this working. I absolutely understand there's some unpredictability here delivering mail over ipv6 but the future is now, ipv6 isn't going away. I fully realize there are probably no ipv6 only domains out there at this time. I have seen different levels of filtering and strictness even between different MXs within the same domain on ipv4, so honestly to say I shouldn't do this because there's there might be differences between ipv4 and ipv6 MXs is frankly no worse than what we already are seeing. If I see something so broken, I am known for letting someone know. Michael Grant
signature.asc
Description: PGP signature
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
