URIBL_BLOCKED - however uribl.com shows it's not

MiamiJack

MiamiJack

Active Member
Proxmox Subscriber
Sep 17, 2020
315
21
38
@Stoiko Ivanov I created this thread to separate where you initially noted on the other post that headers show the URIBL_BLOCKED message.

Once you mentioned the blocking according to mail headers I went through some different settings, and docs on uribl.com.

If I query query as shown on their site to test if I'm being blocked it looks good:
host -tA 2.0.0.127.multi.uribl.com
2.0.0.127.multi.uribl.com has address 127.0.0.1


If I look in mail.log, I see the SA information, and it looks like it's giving me the value for URIBL at the end:
Oct 1 21:21:55 mgw pmg-smtp-filter[2488]: 814315F7680AF038E7: SA score=0/5 time=3.942 bayes=undefined autolearn=ham autolearn_force=no hits=AWL(-0.420),DKIMWL_WL_HIGH(-0.001),DKIM_SIGNED(0.1),DKIM_VALID(-0.1),DKIM_VALID_AU(-0.1),HTML_IMAGE_RATIO_02(0.001),HTML_MESSAGE(0.001),MIME_HTML_ONLY(0.1),RCVD_IN_MSPIKE_H3(0.001),RCVD_IN_MSPIKE_WL(0.001),RCVD_IN_RP_CERTIFIED(-3),RCVD_IN_RP_SAFE(-2),SPF_HELO_NONE(0.001),SPF_PASS(-0.001),T_KAM_HTML_FONT_INVALID(0.01),URIBL_BLOCKED(0.001)

If I look at the mail header I still see the notice:
URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked.


Any suggestions?

Thanks!
 
  • Like
Reactions: Stoiko Ivanov
Hi.

I tried to implement the solution at https://pmg.proxmox.com/wiki/index.php/DNS_server_on_Proxmox_Mail_Gateway, but I always get this error:
Code: 
root@pmg14:~# dig a proxmox.com @127.0.0.1 +short

; <<>> DiG 9.16.27-Debian <<>> a proxmox.com @127.0.0.1 +short
;; global options: +cmd
;; connection timed out; no servers could be reached

The server is listening:
Code: 
root@pmg14:~# ss -tulnp | grep ":53.*unbound"
udp   UNCONN 0      0          127.0.0.1:53         0.0.0.0:*    users:(("unbound",pid=41443,fd=5))                                                                         
udp   UNCONN 0      0              [::1]:53            [::]:*    users:(("unbound",pid=41443,fd=3))                                                                         
tcp   LISTEN 0      256        127.0.0.1:53         0.0.0.0:*    users:(("unbound",pid=41443,fd=6))                                                                         
tcp   LISTEN 0      256            [::1]:53            [::]:*    users:(("unbound",pid=41443,fd=4))                                                                         

or the long version with systemd still running until I resolve the dig :
root@pmg14:~# ss -tulnp | grep ":53"
udp   UNCONN 0      0          127.0.0.1:53         0.0.0.0:*    users:(("unbound",pid=41443,fd=5))                                                                         
udp   UNCONN 0      0      127.0.0.53%lo:53         0.0.0.0:*    users:(("systemd-resolve",pid=76,fd=16))                                                                   
udp   UNCONN 0      0            0.0.0.0:5355       0.0.0.0:*    users:(("systemd-resolve",pid=76,fd=11))                                                                   
udp   UNCONN 0      0              [::1]:53            [::]:*    users:(("unbound",pid=41443,fd=3))                                                                         
udp   UNCONN 0      0               [::]:5355          [::]:*    users:(("systemd-resolve",pid=76,fd=13))                                                                   
tcp   LISTEN 0      256        127.0.0.1:53         0.0.0.0:*    users:(("unbound",pid=41443,fd=6))                                                                         
tcp   LISTEN 0      4096   127.0.0.53%lo:53         0.0.0.0:*    users:(("systemd-resolve",pid=76,fd=17))                                                                   
tcp   LISTEN 0      4096         0.0.0.0:5355       0.0.0.0:*    users:(("systemd-resolve",pid=76,fd=12))                                                                   
tcp   LISTEN 0      256            [::1]:53            [::]:*    users:(("unbound",pid=41443,fd=4))                                                                         
tcp   LISTEN 0      4096            [::]:5355          [::]:*    users:(("systemd-resolve",pid=76,fd=14))

Any suggestion for me?
Thank you.
 
cglmicro said:
I tried to implement the solution at https://pmg.proxmox.com/wiki/index.php/DNS_server_on_Proxmox_Mail_Gateway, but I always get this error:
Click to expand...
Please open a new thread, rather than answering to one that is more than 1.5 years old! (if the suggestions below don't help - please open a new thread)

sounds odd - things I'd look into:
* do you have some iptables/nftable rules preventing communication on 127.0.0.1? - I'd suggest to let traffic on `lo` simply pass
* systemd-resolved might cause some issues with that setup - (despite it shouldn't since it's listening to 127.0.0.53..., but who knows)
** unless you need it and know you need it - I'd suggest trying to remove it
* also make sure that your /etc/resolv.conf is correct (should not matter for the test with `dig` though)

I hope this helps!
 
You must log in or register to reply here.
Top Bottom