Luc Rossini

@PointPubMedia .@PointPubMedia, All ok Now? If you’re not seeing any more NDRs then the NDR sender fixed or updated the BL data they synchronise from Spamhaus.

@PointPubMedia @spamhaus The Spamhaus checker gives the correct result as it checks our blocklists in realtime. A discrepancy between our checker result and an NDR suggests the NDR sender has a delay updating their local Spamhaus data from us. Test again after an hour or so.

@spamhaus website check said no issue but it's not what are having from NDR...

@FireLinksIO @spamhaus @LinkedIn If @linkedin were to start trying to validate millions of URLs against our IP/domain Reputation Checker webpage we’d have to ask them to immediately stop.

@FireLinksIO @spamhaus @LinkedIn Why doesn’t the Spamhaus Reputation Checker have a backup service running multiple zones? That would be because the Spamhaus Reputation Checker is a webpage tool not a zone, specifically it’s this webpage: check.spamhaus.org

The gremlins are back... and the IP and Domain Reputation Checker is not available... our brilliant geeks are working on getting it back online.

We recently shared that some systems saw >30% of spam messages being caught by our Hash Blocklist alone - well, the positive feedback isn't slowing down! Learn about the dataset here, which lists malicious content, as opposed to IP addresses or domains: hubs.ly/Q01fZcWc0

@rootnk Hi. We’d appreciate it if you stop adding @spamhaus to your spam report tweets. Spamhaus does not process nor look into 3rd-party spam reports. Thank you.

@lloyd_frombriz @GoToSuite @spamhaus Mr Frombriz, Could I ask you kindly to stop adding @spamhaus to all your tweets. Spamhaus does not look at nor use external spam reports. Thank you.

@GoToSuite As mentioned previously read RFC2142 and have a functioning abuse desk. Clicking links in spam confirms your address and they resell it at a higher price. If you enforced your AUP this wouldn't be a problem. Paging @spamhaus spam still following with their approval.

Get started with #GoToStage and set up a public or private channel to post your #GoToWebinar recordings. 🎥 Watch our video to learn how: bit.ly/3fRFWwz

@j_a_silvestre @AndorraTelecom ... si teniu algun problema per enviar correu a causa de la PBL, normalment la causa és que la vostra autenticació SMTP no funciona correctament. Per ajuda consulteu #183" target="_blank" rel="nofollow noopener">spamhaus.org/faq/section/Sp…

@j_a_silvestre @AndorraTelecom Hola, Spamhaus PBL és una llista de rangs d'IP que "no són IP de servidor de correu". El rang 109.111.112.* apareix assignat a usuaris finals d’Andorra Telecom i per tant és normal que estigui nel PBL. Si trobeu correus bloquejats per la PBL el problema no és amb el rDNS ...

Mail server administrators and operators, please pass this announcement/notice on to any colleagues on mail server forums or discussion lists.

Using Spamhaus’s free public DNSBLs in your mail server’s spam filter but they hardly catch any spam at all? Here’s why: spamhaus.com/resource-cente…

Very important update for mail server admins with mail servers using Spamhaus free public DNSBLs via a public DNS resolver service : CHECK your mail server config knows what to do with the new Spamhaus DNSBL return codes.

Another new release! This time a Developer License from @SpamhausTech. Six months access to enhanced IP reputation data. spamhaus.com/resource-cente… #dev_life #build #data

@nevillematthews BTInternet are correct, it's not their issue. If he encounters the Spamhaus PBL it means he's connecting to them on Port 25, not 465, ergo he has an SMTP AUTH issue. Advise him to check his SMTP AUTH settings: #197" target="_blank" rel="nofollow noopener">spamhaus.org/faq/section/Sp…

I have a client who has Virgin broadband at home. Has a paid #BTInternet email address, sending via Port 465/SSL to mail.btinternet.com mail servers. It was working until recently. Spamhaus 86.24.0.0/16 blocking for direct MX, not Auth SMTP. BT denying it's their problem.

@HyperopticCS @urzz1871 @spamhaus @HyperopticCS, from the description your customer appears to be encountering a Spamhaus PBL filter on (your) outbound SMTP server, which suggests the customer's MUA is failing to Authenticate with your SMTP server. The quick fix for this issue is here: #197" target="_blank" rel="nofollow noopener">spamhaus.org/faq/section/Sp…

@spamhaus Any advice, please? My ISP, #Hyperoptic, has allocated me an IP address on the SBL Blacklist and don't seem to be able to do anything about it, so I'm unable to send POP3 mail. How do I get this cleared? The form requires a hostname, which I don't have...

@urzz1871 @spamhaus Okay, that'll be the PBL, not the SBL. The PBL is not a 'blacklist' but a list of home broadband IPs that should use 'SMTP Authentication' when sending mail. This is what you need to fix this issue and turn your SMTP Authentication on: #183" target="_blank" rel="nofollow noopener">spamhaus.org/faq/section/Sp…

@RachelBActor @virginmedia Port 465 is fine, you can use either 587 or 465 - whichever of those your provider wants you to use. (Unless I'm mistaken I don't believe Spamhaus has any documentation advising against using 465)

Hey @virginmedia Email suddenly stopped working. My IP has been added to Spamhaus who advise use 587 & not 465, but your servers won't allow this. My broadband has been down for a week and now this?! Can you please help? I've already spent 30 mins with useless customer service

@JohnGonzalezFr @spamhaus I appreciate and apologise for your frustration. Unfortunately the more technically complex an issue, the more technically complex the process. We are working on making it less so. I personally answered your email on 31 March giving you contact information for the CBL team.

All questions about any Spamhaus listing are handled exclusively via our Blocklist Removal Center: spamhaus.org/lookup/. Unfortunately we do not handle requests via any other channel, including Twitter.

@drum_puppy Check the reject messages for what IP address or domain was rejected. If an IP address, enter it at spamhaus.org/lookup/ to see what @spamhaus list it's on. If it comes back as listed on 'PBL' then you have a local authentication problem and the PBL FAQ will help you fix it.

@GI_Fucken_Jack Spamhaus PBL only works on port 25. If you check your mail server log for the incident you will find that your authentication had failed so it connected to your mail server on port 25 instead of port 587. The purpose of the PBL is to prevent home broadband IPs doing exactly that.