That’s ESS, our hosted email filtering service which includes customer configured list of RBLs.
--Erwin > On Jun 13, 2019, at 09:48, Kevin A. McGrail via mailop <mailop@mailop.org> > wrote: > > Nick, > > Thanks for escalating to them. I've been doing the same. > > However, I think you were given wrong information from Barracuda. In > the DSN snippet below, d95432a.ess.barracudanetworks.com claims it > blocked due to msrbl.net. Perhaps that some sort of PaaS / SaaS > offering that a customer can configure which would make them right. > > > >> ----- The following addresses had permanent fatal errors ----- >> <redacted> >> (reason: 550 Service unavailable; Client host [intel1.peregrinehw.com] >> blocked by combined.rbl.msrbl.net; 38.124.232.10 (redacted:blocked)) >> >> ----- Transcript of session follows ----- ... while talking to >> d95432a.ess.barracudanetworks.com.: >>>>> DATA >> <<< 550 Service unavailable; Client host [intel1.peregrinehw.com] > blocked by >> combined.rbl.msrbl.net; 38.124.232.10 (redacted:blocked) >> 554 5.0.0 Service unavailable > > > Regards, > KAM > >> On 6/13/2019 12:43 PM, Nick Schafer wrote: >> I got in contact with Barracuda and they don't actually use msrbl.net >> <http://msrbl.net>. They do however allow their customers to specify >> additional blacklists should they want to and from what I'm seeing, some >> of their customers do use msrbl.net <http://msrbl.net>. >> >> Best, >> >> Nick Schafer >> Deliverability Engineer, Mailgun <http://www.mailgun.com/> >> >> >> On Thu, Jun 13, 2019 at 8:09 AM Kevin A. McGrail via mailop >> <mailop@mailop.org <mailto:mailop@mailop.org>> wrote: >> >> Hello All, >> >> Trying to reach someone at Barracuda to escalate this issue to >> them. This morning we received this complaint: >> >>> <<< 550 Service unavailable; Client host [intel1.peregrinehw.com >> <http://intel1.peregrinehw.com>] blocked by >>> combined.rbl.msrbl.net <http://combined.rbl.msrbl.net>; >> 38.124.232.10 (redacted:blocked) >>> 554 5.0.0 Service unavailable >> >> To my knowledge that is caused by a combination of three things: >> >> 1 - *That RBL is no longer running. >> *https://www.dnsbl.info/dnsbl-details.php?dnsbl=combined.rbl.msrbl.net >> has a good description. [1] See http://www.msrbl.com/check-db >> >> 2 - Domain squatters have taken over the domain msrbl.net >> <http://msrbl.net> and are giving out positive responses for things. >> >> 3 - People who have configured their spam gateways to use that RBL >> will get all kinds of problems. It appears to me that >> barracudanetworks.com <http://barracudanetworks.com> is using it. >> >> I've opened ticket 03269004 with Barracuda to try and let them know >> and get the word out. >> >> But for everyone else on the list, if you are querying msrbl.net >> <http://msrbl.net>, it's effectively not working. I won't say >> compromised because I think it's just for sale on sedo so they are >> giving positive queries for a wildcard record. >> >> Regards, >> KAM >> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org <mailto:mailop@mailop.org> >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
