Steen,
sorry for the delay in answering.
>
> * Whitelist: Is it possible to use wildchars in usernames. I would
> like to whitelist all mails from a certain domain, no matter which
> user from that domain is sending. (Perhaps something like
> *.<remote-domain> ).
There is no need to insert such "wildchared" addresses in the whitelist; you can
achieve the desired behaviour simply appropriately coding your config file, as I did
too(search for "SenderHostIs=xxx.com yyy.org" in the snippet below):
<!-- White list management -->
<mailet match="All" class="WhiteListManager" onMailetException="ignore">
<table>db://maildb/whitelist</table>
<whitelistManagerAddress>[EMAIL PROTECTED]</whitelistManagerAddress>
<displayFlag>display</displayFlag>
<insertFlag>insert</insertFlag>
<removeFlag>remove</removeFlag>
</mailet>
<!-- Anti spam bayesian analysis -->
<mailet match="All" class="JDBCBayesianAnalysis" onMailetException="ignore">
<repositoryPath>db://maildb</repositoryPath>
<hamTable>bayesiananalysis_ham</hamTable>
<spamTable>bayesiananalysis_spam</spamTable>
<messageCountsTable>bayesiananalysis_messagecounts</messageCountsTable>
<spamManagerAddress>[EMAIL PROTECTED]</spamManagerAddress>
<rebuildSubjectFlag>rebuild spam corpus</rebuildSubjectFlag>
<headerName>X-MessageIsSpamProbability</headerName>
<ignoreLocalSender>true</ignoreLocalSender>
</mailet>
<mailet match="SenderHostIsLocal" class="ToProcessor">
<processor> transport </processor>
</mailet>
<mailet match="IsInWhiteList=db://maildb/whitelist" class="ToProcessor"
onMatchException="matchAll">
<processor> transport </processor>
</mailet>
<mailet match="SenderHostIs=xxx.com yyy.org" class="ToProcessor">
<processor> transport </processor>
</mailet>
<mailet match="CompareNumericHeaderValue=X-MessageIsSpamProbability > 0.90"
class="AddHeader" onMatchException="noMatch">
<name>X-MessageIsSpam</name>
<value>true</value>
</mailet>
<mailet match="CompareNumericHeaderValue=X-MessageIsSpamProbability > 0.99"
class="ToProcessor" onMatchException="noMatch">
<processor> spam </processor>
<notice>Spam not accepted</notice>
</mailet>
<!-- Send remaining mails to the transport processor for either local or
remote delivery -->
<mailet match="All" class="ToProcessor">
<processor> transport </processor>
</mailet>
</processor>
> And I would like to be able to whitelist a mail address for all my
> users in one step. (For example by using a wildchar: *.<mydomain> )
>
This is a good idea, and I will add it to WhiteListManager and IsInWhiteList.
But what if a user ingenuously answers to a spam message to be removed? The spammer
address would immediately go into the whitelist for many other users. Such option
should be used cautiously.
> * Spam manager: Is it possible to automatically add a whitelisted mail
> directly to the corpus. This way my users don't have to send non-spam
> mails to the spam manager.
>
Again, you can do that just playing around with the config file, putting appropriate
"not spam" bayesian analysis feeder mailet entries in appropriate places with
appropriate matchers.
But beware: while JDBCBayesianAnalysis is quite fast, the JDBCBayesianAnalysisFeeder
mailet does a lot of work (database activity) and takes several seconds or even
minutes to update the statistics in the database for a single message feeded. This is
ok as long as the number of spam/not.spam message feedings is low compared to the
number of messages analysed, but feeding any whitelisted message would kill
everything. Regarding this performance problem, I'm thinking on using a serializable
object (with some kind of "asynchronous intermittent lazy writer" and appropriate
behaviour against write failures) instead of a database for storing the corpus.
> * Spam manager: Are mails identified as spam automatically added to
> the corpus. Again to save my users from sending spam mails to the
> spam manager. (You know, my users are lazy)
Same as above, but moreover IMO it would be dangerous: the effect would be amplifying
"false positives" through a feedback mechanism, quickly ruining the corpus; only "true
positives", determined as such in some other way, should be fed as spam, and you can
do it simply playing around with the config.xml file.
>
> Steen
>
Vincenzo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
