Talk:Email

From SME Server
Revision as of 09:12, 8 March 2009 by Snoble (talk | contribs)
Jump to navigationJump to search

What is this?

db spamassassin setprop wbl.global This e-mail address is being protected from spam bots, you need JavaScript enabled to view it White
db spamassassin setprop wbl.global This e-mail address is being protected from spam bots, you need JavaScript enabled to view it Black

--Normando Hall 15:42, 25 August 2007 (MDT)


RBLList

config delprop qpsmtpd  RBLList
/etc/e-smith/events/actions/initialize-default-databases

gives

RBLList=bl.spamcop.net:combined.njabl.org:dnsbl.ahbl.org:dnsbl-1.uceprotect.net:dnsbl-2.uceprotect.net:list.dsbl.org:multihop.dsbl.org:psbl.surriel.com:zen.spamhaus.org

so why are we saying the following, isn't sme best practice

Many will argue what's best but most would agree that you can set best-practice recommended settings by:

config setprop qpsmtpd RBLList zen.spamhaus.org:whois.rfc-ignorant.org:dnsbl.njabl.org
signal-event email-update

Snoble 05:44, 6 March 2009 (UTC)

If I'm interpreting your question/post correctly....

I think the "best-practise" comment came from an earlier recommendation for "conservative" settings for RBLList. These settings were seen as non agressive, whereas the default settings that were in sme 7.0 (I think it was 7.0) when it was released, were more agressive and perhaps would block mail that some people wanted to receive.

Perhaps the words "best-practise recommended" should be replaced with "conservative non agressive".

Ray

Thanks Ray,

is the current default still too aggressive ?
is the suggested conservative value valid, and will it always be, ie if it can become outdated we should remove it

when there was a problem with an RBL before a fix was quickly released in smeupdates, if one of the wiki suggestions becomes outdated there is no automatic way to fix it

Stephen