Not sure I understand your request - the ip 192.28.150.228 is listed on zen.spamhaus.com (which is a DNS block list):
* if you're the admin of a mailserver running on 192.28.150.228 - then check your logs - most likely someone is using your system to send out spam from it
* if you have a PMG, which rejects mail from 192.28.150.228, but want to receive mails from them (despite the ip being blacklisted) - add the ip to the mail proxy whitelist (GUI -> Configuration -> Mail Proxy -> Whitelist)
I hope this helps!
are all the ips the emails come from listed on zen.spamhaus.org?E-mail from all domains are showing same rejection message..
Seems your installation have an issue, you block IPs which are not listed on the blacklists. What did you change recently?
=> Disable RBL rejects, does this help?
Which version do you run exactly?
are all the ips the emails come from listed on zen.spamhaus.org? --not listed in spamhausare all the ips the emails come from listed on zen.spamhaus.org?
(you can check ips online at sites like: http://multirbl.valli.org/ or http://www.anti-abuse.org/multi-rbl-check/)
I hope this helps!
please share some more logs - (/var/log/mail.log) - anonymize what's necessary
this sounds odd - the responses to DNSBL lookups are usually in 127.0.0.0/8 (and not 37.131.68.29)addr 212.224.123.68 listed by domain zen.spamhaus.org as 37.131.68.29
dig +norec 68.123.224.212.zen.spamhaus.org @c.gns.spamhaus.org.` (maybe also replace 'c' in 'c.gns.spamhaus.org.' with 'a' - 'd')
; <<>> DiG 9.11.5-P4-5.1-Debian <<>> +norec 68.123.224.212.zen.spamhaus.org @c.gns.spamhaus.org.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48627
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;68.123.224.212.zen.spamhaus.org. IN A
** `dig 68.123.224.212.zen.spamhaus.org`
; <<>> DiG 9.11.5-P4-5.1-Debian <<>> 68.123.224.212.zen.spamhaus.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17385
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; ANSWER SECTION:
68.123.224.212.zen.spamhaus.org. 0 IN A 37.131.68.29
looks
like your recursive dns-server has some problem (or some broken cache):
shows that 212.224.123.68 is not listed with spamhaus (NXDOMAIN) when asking their authoritative nameserverCode:dig +norec 68.123.224.212.zen.spamhaus.org @c.gns.spamhaus.org.` (maybe also replace 'c' in 'c.gns.spamhaus.org.' with 'a' - 'd') ; <<>> DiG 9.11.5-P4-5.1-Debian <<>> +norec 68.123.224.212.zen.spamhaus.org @c.gns.spamhaus.org. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48627 ;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;68.123.224.212.zen.spamhaus.org. IN A
while
shows that it gets a (very odd) response from your internal dnsCode:** `dig 68.123.224.212.zen.spamhaus.org` ; <<>> DiG 9.11.5-P4-5.1-Debian <<>> 68.123.224.212.zen.spamhaus.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17385 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; ANSWER SECTION: 68.123.224.212.zen.spamhaus.org. 0 IN A 37.131.68.29
-> check your internal DNS (check its logs, clear its cache, restart the service)
I hope this helps!
Try the dig lookups you ran from your PMG from your DNS server.
and post the results
on the internal DNS server (and on the secondary)!* provide the output of:
** `dig +norec 68.123.224.212.zen.spamhaus.org @c.gns.spamhaus.org.` (maybe also replace 'c' in 'c.gns.spamhaus.org.' with 'a' - 'd')
** `dig 68.123.224.212.zen.spamhaus.org`
** `dig 68.123.224.212.zen.spamhaus.org @127.0.0.1`
you have a typo here - spamhaus not spamhusspamhus.org
It is type mistake from my end..configuration screen shot in belowsorry wasn't clear enough :
run:
on the internal DNS server (and on the secondary)!
you have a typo here - spamhaus not spamhus