On 17 Apr 2016, at 3:04, Benjamin Yeo wrote:
Hi Guys. I've just downloaded the latest SpamAssassin and I want to
integrate with my mail server James 2.3.1.
I have some questions that I can't seems to find answers to on the
wiki of
spamassassin.
Is there blacklisting options that I can use per user that stores this
data
in the database?
See https://wiki.apache.org/spamassassin/UsingSQL for how to put
user_prefs records in a database that spamd can use. That page only
shows a few of the settings that can go into user_prefs, but you can
also put just about anything that can go into local.cf into user_prefs,
including blacklist/whitelist directives.
Is there also greylisting options that I can use per user?
SpamAssassin is a message data analysis framework, not a SMTP session
management tool. As such, it operates at the end-of-data phase of SMTP
and so has no role in greylisting.
For greylisting, I am going to hold the email before sending a
verification
check to the sender of the email.
That is an inherently abusive practice. Do not do it. There are a
significant number of mail systems which reject all verification
attempts as well as all other mail from sites they believe to be using
that misguided tactic, which is entirely reasonable.
When verification is done successfully,
if fail, email will be discarded, if successful, email will then be
sent.
Is this at SpamAssassin's level or James's level? I have been trying
to
integrate and try out everything but still nothing.
Just don't do it. The fact that you need to ask that question makes it
clear that you don't understand how SMTP mail works well enough to do
minimally abusive and reasonably functional sender verification and so
are almost certain to repeat the naive mistakes that have been made by
most past implementations of this fundamentally bad idea.
