|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
Mail::SpamAssassin::PlUser:ContributeMail::SpamAssassin::Plugin::DomainKeys(3)
NAME
Mail::SpamAssassin::Plugin::DomainKeys - perform DomainKeys verifica-
tion tests
SYNOPSIS
loadplugin Mail::SpamAssassin::Plugin::DomainKeys [/path/to/DomainKeys.pm]
Signature:
header DK_SIGNED eval:check_domainkeys_signed()
header DK_VERIFIED eval:check_domainkeys_verified()
Policy:
Note that DK policy record is only fetched if DK_VERIFIED is false
to save signing domain from unnecessary DNS queries,
as recommended (SHOULD) by draft-delany-domainkeys-base.
Rules DK_POLICY_* should preferably not be relied upon when DK_VERI-
FIED
is true, although they will return false in current implementation
when a policy record is not fetched, except for DK_POLICY_TESTING,
which is true if t=y appears in a public key record OR in a policy
record (when available).
header DK_POLICY_TESTING eval:check_domainkeys_testing()
header DK_POLICY_SIGNSOME eval:check_domainkeys_signsome()
header DK_POLICY_SIGNALL eval:check_domainkeys_signall()
Whitelisting based on verified signature:
header USER_IN_DK_WHITELIST eval:check_for_dk_whitelist_from()
header USER_IN_DEF_DK_WL eval:check_for_def_dk_whitelist_from()
DESCRIPTION
This is the DomainKeys plugin and it needs lots more documentation.
USER SETTINGS
domainkeys_timeout n (default: 5)
How many seconds to wait for a DomainKeys query to complete, before
scanning continues without the DomainKeys result.
whitelist_from_dk add@ress.com [signing domain name]
Use this to supplement the whitelist_from addresses with a check to
make sure the message has been signed by a DomainKeys signature
that can be verified against the From: domain's DomainKeys public
key.
In order to support signing domain names that differ from the
address domain name, only one whitelist entry is allowed per line,
exactly like "whitelist_from_rcvd". Multiple "whitelist_from_dk"
lines are allowed. File-glob style meta characters are allowed for
the From: address, just like with "whitelist_from_rcvd". The
optional signing domain name parameter must match from the right-
most side, also like in "whitelist_from_rcvd".
If no signing domain name parameter is specified the domain of the
address parameter specified will be used instead.
The From: address is obtained from a signed part of the message
(ie. the "From:" header), not from envelope data that is possible
to forge.
Since this whitelist requires a DomainKeys check to be made, net-
work tests must be enabled.
Examples:
whitelist_from_dk joe@example.com
whitelist_from_dk *@corp.example.com
whitelist_from_dk bob@it.example.net example.net
whitelist_from_dk *@eng.example.net example.net
def_whitelist_from_dk add@ress.com [signing domain name]
Same as "whitelist_from_dk", but used for the default whitelist
entries in the SpamAssassin distribution. The whitelist score is
lower, because these are often targets for spammer spoofing.
perl v5.8.8 200Mail::SpamAssassin::Plugin::DomainKeys(3)
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Sat Sep 8 16:38:00 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
svn man page (6162 hits)
(FreeBSD 6.2)
sqlite3 man page (5598 hits)
(openSUSE 10.2)
adv_cap_autoneg man page (5045 hits)
(Solaris 10 11_06)
CPAN man page (4791 hits)
(Suse Linux 10.1)
ssh man page (4439 hits)
(Suse Linux 10.1)
ssh-socks5-proxy-connect man page (3525 hits)
(Solaris 10 11_06)
signal man page (3395 hits)
(Suse Linux 10.1)
netcat man page (3375 hits)
(Suse Linux 10.1)
pprosetup man page (2886 hits)
(Solaris 10 11_06)
startproc man page (2738 hits)
(Suse Linux 10.1)
|
Man Pages 
Unix/Linux Forum 