On 11/06/2014 07:27 AM, Jim Shupert wrote:
!st let me say that I am going to be building a new qmail toaster
mailserver because my current one is old.
( and has served us very well -- yahoo qmt )
I also very much wish to "better' my situation regarding spam.
I hope to employ spam dyke
and I am wondering what might my expectations be?
example
I have just gotten a whitelist request from a usr. for the dom of
alloyfx.com
www.blacklistalert.org/
dynamic.rhs.mailpolice.com /*LISTED!* /
**multi.uribl.com /*LISTED!* /
**webmail.rhs.mailpolice.com /*LISTED!*/
Yes, if one checks they are listed , likely they have no rdns
so - Am i to expect that this domaine will cont to need to be whitelisted
because they will continue to be 'listed"
>
so Q 1 , is that correct ? they will continue to be marked *** SPAM
*** - yes?
They'll need to be whitelisted in spamdyke in order to accept them. They
can also be whitelisted in spamassassin to get rid of the *** SPAM ***
subject tag, and to ensure that the scoring total there doesn't trigger
a rejection.
Q2
do I need to do anything "special" beyond the bootstrap.sh 1 & 2 to get
spam dyke
( and any other anti Spam suggestions you may have )
going?
Nothing additional is required.
what am i to expect?
Generally, I would expect smooth sailing, with spamdyke rejecting 80%+
of incoming messages (without even receiving let alone scanning them!).
Caution: regarding the firewall, if your QMT is behind a nat'ing router
(on a private subnet), you should adjust the firewall script
accordingly. I hope to have Sebastian's fix for this in a subsequent
release soon.
--
-Eric 'shubes'
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
