Changes

Jump to navigation Jump to search
605 bytes added ,  13:39, 4 July 2017
Add note about high traffic dns servers and URIBL
Line 15: Line 15:  
: There are forum reports of problems for users who had DKIM enabled using the DKIM contrib.
 
: There are forum reports of problems for users who had DKIM enabled using the DKIM contrib.
 
===URIBL===
 
===URIBL===
: SME Server now supports URIBL - the ability to block emails that contain known malicious URLs within the body of the email.  This service is disabled by default.
+
: qpsmtpd now supports URIBL - the ability to block emails that contain known malicious URLs within the body of the email.  This service is disabled by default.
    
: Enable URIBL with the default services using:
 
: Enable URIBL with the default services using:
 
  <nowiki>config setprop qpsmtpd URIBL enabled
 
  <nowiki>config setprop qpsmtpd URIBL enabled
 
signal-event email-update</nowiki>
 
signal-event email-update</nowiki>
 +
 +
: '''Note:''' If your SME server is using high traffic external DNS forwarders like [https://developers.google.com/speed/public-dns/ google] (8.8.8.8 / 8.8.4.4), [https://www.opendns.com/setupguide/ opendns] (208.67.222.222 / 208.67.220.220), or any large ISP's (Cox, Comcast, Verizon), enabling URIBL may block all incoming email.  This will only affect you if you have configured a DNS forwarder in server-manager -- a default SME server installation does its own direct DNS lookups and would not be affected unless you receive over 250,000 emails per day.
 +
 +
:  Read more at http://uribl.com/refused.shtml
    
==="Naughty" plugin===
 
==="Naughty" plugin===

Navigation menu