MDaemon Messaging Server – Resolving URIBL Blocked Notifications
-
I only just noticed, but sems I've had a long standing issue with URIBL request being blocked! when searching the web seems this is a common issue but solutions seems to be limited.
Sun 2023-08-27 23:57:15.012: (SMTP) Spam Filter processing d:\mdaemon\queues\temp\md5001000000002.tmp... Sun 2023-08-27 23:57:15.012: * Message return-path: root@sapphire.cfts.co Sun 2023-08-27 23:57:15.012: * Message ID: <4a8c86952727e013afcb7c2a9c4931a8@sapphire.cfts.co> Sun 2023-08-27 23:57:15.012: Start SpamAssassin results Sun 2023-08-27 23:57:15.013: -103.20 points, 5.0 required; Sun 2023-08-27 23:57:15.013: * -0.0 USER_IN_WELCOMELIST User is listed in 'welcomelist_from' Sun 2023-08-27 23:57:15.013: * -100 USER_IN_WHITELIST From: address is in the whitelist Sun 2023-08-27 23:57:15.013: * 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was Sun 2023-08-27 23:57:15.013: * blocked. See Sun 2023-08-27 23:57:15.013: * http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block Sun 2023-08-27 23:57:15.013: * for more information. Sun 2023-08-27 23:57:15.013: * [URIs: cfts.co] Sun 2023-08-27 23:57:15.013: * -4.7 BAYES_00 BODY: Bayes spam probability is 0 to 1% Sun 2023-08-27 23:57:15.013: * [score: 0.0000] Sun 2023-08-27 23:57:15.013: * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts Sun 2023-08-27 23:57:15.013: * 0.0 HTML_MESSAGE BODY: HTML included in message Sun 2023-08-27 23:57:15.013: * 0.4 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML Sun 2023-08-27 23:57:15.013: * tag Sun 2023-08-27 23:57:15.013: * 1.0 SUBJ_BRKN_WORDNUMS Subject contains odd word breaks and numbers Sun 2023-08-27 23:57:15.013: End SpamAssassin results
I made a local DNS server as per blog: http://blog.ccsoftware.ca/2014/07/31/mdaemon-messaging-server-resolving-uribl-blocked-notifications/
The environment: Mdaemon 23, Windows 2019 server in a ESXi 7 VM environment.
It solved the issue, but then found out I could not send any emails, so not an ideal solution, does anybody have any ideas.
-
@peter OK seems to be sorted now, I had to change a few DNS rules in our firewalls to allow DNS requests direct from the mail server, so the instructions work as advrtised.
Mon 2023-08-28 09:12:53.453: ---------- Mon 2023-08-28 09:24:56.129: (SMTP) Spam Filter processing d:\mdaemon\queues\temp\md5001000000183.tmp... Mon 2023-08-28 09:24:56.129: * Message return-path: msprvs1=19604OTq5cKEx=bounces-280047@bounce.smartsheet.com Mon 2023-08-28 09:24:56.129: * Message ID: <5F.E7.21018.0E83CE46@jh.mta1vrest.cc.prd.sparkpost> Mon 2023-08-28 09:24:56.129: Start SpamAssassin results Mon 2023-08-28 09:24:56.129: -4.60 points, 5.0 required; Mon 2023-08-28 09:24:56.129: * -4.7 BAYES_00 BODY: Bayes spam probability is 0 to 1% Mon 2023-08-28 09:24:56.129: * [score: 0.0000] Mon 2023-08-28 09:24:56.129: * 0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts Mon 2023-08-28 09:24:56.129: * 0.0 HTML_MESSAGE BODY: HTML included in message Mon 2023-08-28 09:24:56.129: * -0.0 RCVD_IN_MSPIKE_H4 RBL: Very Good reputation (+4) Mon 2023-08-28 09:24:56.129: * [147.253.216.218 listed in wl.mailspike.net] Mon 2023-08-28 09:24:56.129: * -0.0 RCVD_IN_MSPIKE_WL Mailspike good senders Mon 2023-08-28 09:24:56.129: End SpamAssassin results Mon 2023-08-28 09:24:56.129: ----------
-
Arron Staff
I'm glad you got it sorted.