On 04/04/17 15:09, Nigel Titley wrote: > Folks, > > I'm coming to you guys as a last resort. I have an MTA whose IPv6 > address has found its way onto the Spamhaus SBL (note that the IPv4 > address is clear and always has been). I've delisted it but it's come > back. I've no idea *why* it has ended up on the SBL: it isn't an open > relay, it's got the right SPF and rDNS records, postmaster and abuse go > to real people (me) and there are no complaints, I can't see anything in > the email logs. Trying to contact Spamhaus is an exercise in futility; > their postmaster responds but isn't very helpful (just refers me to the > delisting procedure). > > Does anyone have any advice?
OK, Spamhaus has contacted me with more information. The server concerned is hosted at Linode. Linode allocates a single /128 to each virtual machine. When Spamhaus gets a spam report they blacklist the entire /64 (which is actually quite sensible for some value of "sensible") and a *lot* of co-lateral damage may take place. This is what seems to have happened in my case. Linode will, on request, allocate a complete /64 to your virtual machine to get around this issue. This is what I intend to do. Thanks to Spamhaus for getting back to me reasonably quickly and for Alex who contacted me directly with help and advice. All the best Nigel
