whitelist feather do not take effect,I have enabled Whitelist Management
------------------------------------------------------------------------
Key: JAMES-963
URL: https://issues.apache.org/jira/browse/JAMES-963
Project: JAMES Server
Issue Type: Test
Components: Matchers/Mailets (bundled)
Affects Versions: 2.3.2
Environment: linux centos 5.3 james 2.3.2
Reporter: zengmk
whitelist feather do not take effect,I have enabled Whitelist Management,the
database have the whitelist table,but when i sent a mail from local user to
remote recipient,and the remote recipient reply to the sender,the whitelist
table have no records.is this a bug? or do i have a wrong configuration?
My whiltelist management configurationis:
<mailet match="SMTPAuthSuccessful" class="WhiteListManager"
onMailetException="ignore">
<repositoryPath>db://maildb</repositoryPath>
<automaticInsert>true</automaticInsert>
<whitelistManagerAddress>[email protected]</whitelistManagerAddress>
<displayFlag>display</displayFlag>
<insertFlag>insert</insertFlag>
<removeFlag>remove</removeFlag>
</mailet>
<!-- "not spam" bayesian analysis feeder. -->
<mailet match="[email protected]"
class="BayesianAnalysisFeeder">
<repositoryPath> db://maildb </repositoryPath>
<feedType>ham</feedType>
<maxSize>200000</maxSize>
</mailet>
<!-- "spam" bayesian analysis feeder. -->
<mailet match="[email protected]"
class="BayesianAnalysisFeeder">
<repositoryPath> db://maildb </repositoryPath>
<feedType>spam</feedType>
<maxSize>200000</maxSize>
</mailet>
<!-- sample SMIME mailets configuration -->
<!-- In order to use SMIME capabilities you need to install the
bouncycastle JCE -->
<!-- provider in your environment (james/lib) -->
<!-- e.g: bcprov-jdk14-129.jar from
http://www.bouncycastle.org/latest_releases.html -->
<!--
<mailet match="IsSMIMEEncrypted" class="SMIMEDecrypt">
<keyStoreType>pkcs12</keyStoreType>
<keyStoreFileName>c:/path.pfx</keyStoreFileName>
<keyStorePassword>myKeyStorePass</keyStorePassword>
<keyAlias>myKeyAlias</keyAlias>
<keyAliasPassword>myKeyPass</keyAliasPassword>
</mailet>
<mailet match="IsSMIMESigned" class="SMIMECheckSignature">
<keyStoreType>pkcs12</keyStoreType>
<keyStoreFileName>c:/path.pfx</keyStoreFileName>
<keyStorePassword>myKeyStorePass</keyStorePassword>
<strip>false</strip>
<onlyTrusted>true</onlyTrusted>
</mailet>
-->
<!--
<mailet match="All" class="XMLVirtualUserTable">
<!- 1:1 mapping ->
<mapping>morg...@middle-earth=sauron@mordor</mapping>
<!- 1:n mapping ->
<mapping>ist...@middle-earth=saruman@isengard;radigast;gandalf</mapping>
<!- DSN mapping ->
<mapping>boro...@osgilliath=error:550 Requested action not taken:
no such user here</mapping>
<!- regex based mapping ->
<mapping>*...@osgilliath=regex:(.*)@osgilliath:$...@minas-tirith</mapping>
<!- both standard and regex mapping ->
<mapping>r...@*=onering@mordor;regex:ring@(.*):r...@${1}</mapping>
<!- conditional regex mapping example ->
<mapping>*...@listserver=regex:(.*)-...@listserver:${1}-subscr...@listserver;
regex:(.*)-...@listserver:${1}-unsubscr...@listserver
</mapping>
</mailet>
-->
<!-- Anti-spam processing -->
<!-- The following two entries avoid double anti-spam analysis -->
<!-- for forwarded messages. -->
<!-- Has spam checking already been done? -->
<mailet match="HasMailAttribute=spamChecked" class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- Spam checking will not be done twice -->
<mailet match="All" class="SetMailAttribute">
<spamChecked>true</spamChecked>
</mailet>
<!-- White List:
If you use block lists, you will probably want to check
for known permitted senders. This is particularly true
if you use more aggressive block lists, such as SPEWS,
that are prone to block entire subnets without regard
for non-spamming senders.
-->
<!-- Messages from authenticated senders never are spam -->
<mailet match="SMTPAuthSuccessful" class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- Messages signed by trusted users never are spam -->
<!-- Uncommenting the following entry, messages with valid signatures
will never be considered spam. -->
<!-- This can be a valid policy *if* SMIMECheckSignature was invoked
-->
<!-- with <onlyTrusted>true</onlyTrusted> set -->
<!--
<mailet match="HasMailAttribute=org.apache.james.SMIMECheckSignature"
class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
<!-- specific known senders -->
<!--
<mailet match="senderis=good...@goodhost"
class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
<!-- People on this list agree to pay a penalty if they send spam -->
<mailet match="InSpammerBlacklist=query.bondedsender.org."
class="ToProcessor">
<processor> transport </processor>
</mailet>
<!-- E-mail legally required not to be spam (see:
http://www.habeas.com) -->
<!--
<mailet match="HasHabeasWarrantMark" class="ToProcessor">
<processor> transport </processor>
</mailet>
-->
<!-- If the sender is in a recipient's whitelist, it is a valid
sender, -->
<!-- and as such the message should not be considered spam for such
recipient. -->
<mailet match="IsInWhiteList=db://maildb" class="ToProcessor"
onMatchException="noMatch">
<processor> transport </processor>
</mailet>
<!-- End of White List -->
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
