G
gerryb
Guest
Since 8.4, and 8.6 has not fixed, spam protection based on DNS blackhole lists blocks authenticated emails for relay. This is not the correct behavour. SMPT connections coming in to local addresses should be checked against spamhous data bases and blocked if on their list, but spamhous DNS blackhole list should not be looked up from clients who have logged logged in and authenticated themselves, and simply sending out their own originating email.
Spamhous sensibly lists most ISP home connection IPs as blackholes, as these are not expected to relay email...if they are doing so, they are likely to have been hi-jacked. However home/office clients who log in and are authenticated must be allowed to send emails.
The only way to allow clients to send emails at present is to turn off on spam protection based on DNS blackhole lists. Asking ISPs to get spamhous to take off their IPs is not sensible, and they may well refuse.
Q: What is the fix that allows authenticated SMTP connections not to be looked up by the spam protection based on DNS blackhole lists? (That is putting the system back to how it worked in versions prior to 8.4)
Thanks, Gerard Bulger
Spamhous sensibly lists most ISP home connection IPs as blackholes, as these are not expected to relay email...if they are doing so, they are likely to have been hi-jacked. However home/office clients who log in and are authenticated must be allowed to send emails.
The only way to allow clients to send emails at present is to turn off on spam protection based on DNS blackhole lists. Asking ISPs to get spamhous to take off their IPs is not sensible, and they may well refuse.
Q: What is the fix that allows authenticated SMTP connections not to be looked up by the spam protection based on DNS blackhole lists? (That is putting the system back to how it worked in versions prior to 8.4)
Thanks, Gerard Bulger