Hello Axb, Below are the response to your queries.
Why not fix the SBL issue instead of trying to work around it? Fixing the SBL issue is the first thing we do. But it takes some time so we do not want our outbound mail service to be affected due to this. 'Your local "fix" won't stop a URIBL_SBL hit at the other, rcpt's end.' In such case we relay our mails through an external server which has clean reputation. That way our mails are delivered to the recipient. Give us the SBL number and we may be able to help you out. Do you mean the response code from zen.spamhaus? the response code is 127.0.0.2 On Fri, Feb 23, 2018 at 10:35 PM, Axb <axb.li...@gmail.com> wrote: > > On 02/23/2018 03:26 PM, shridhar shetty wrote: > >> Hello, >> >> In our infra we use spamassassin to scan our **outgoing** mails too. This >> is to prevent spammers using our infra to send mails and get our IP's >> blacklisted. We perform various DNSBL tests on the mail body. >> >> One of our IPs got listed in Spamhaus SBL for some reason, so now our >> outgoing mails are getting detected as spam if the email body contains our >> local domainname whose IP is listed in SBL(hitting URIBL_SBL rule). >> We have hundreds of domainnames mapped to an single IP. >> > > > Why not fix the SBL issue instead of trying to work around it? > Your local "fix" won't stop a URIBL_SBL hit at the other, rcpt's end. > Give us the SBL number and we may be able to help you out. > > >
