You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by gb...@apache.org on 2018/02/18 18:32:05 UTC
svn commit: r1824686 - in /spamassassin/trunk: lib/Mail/SpamAssassin/
lib/Mail/SpamAssassin/BayesStore/ lib/Mail/SpamAssassin/Message/
lib/Mail/SpamAssassin/Plugin/ spamd-apache2/lib/Mail/SpamAssassin/
spamd-apache2/lib/Mail/SpamAssassin/Spamd/ spamd-a...
Author: gbechis
Date: Sun Feb 18 18:32:04 2018
New Revision: 1824686
URL: http://svn.apache.org/viewvc?rev=1824686&view=rev
Log:
fix all pod errors spotted in bz 7168 and many more
Modified:
spamassassin/trunk/lib/Mail/SpamAssassin/AICache.pm
spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/BDB.pm
spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/MySQL.pm
spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/PgSQL.pm
spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/Redis.pm
spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/SQL.pm
spamassassin/trunk/lib/Mail/SpamAssassin/Message/Metadata.pm
spamassassin/trunk/lib/Mail/SpamAssassin/Message/Node.pm
spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm
spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DNSEval.pm
spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/TxRep.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclIP.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclRFC1413.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/Config.pm
spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Config.pm
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/AICache.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/AICache.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/AICache.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/AICache.pm Sun Feb 18 18:32:04 2018
@@ -20,8 +20,6 @@
Mail::SpamAssassin::AICache - provide access to cached information for
ArchiveIterator
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module allows ArchiveIterator to use cached atime information instead of
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/BDB.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/BDB.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/BDB.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/BDB.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::BayesStore::BDB - BerkeleyDB Bayesian Storage Module Implementation
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module implementes a BDB based bayesian storage module.
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/MySQL.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/MySQL.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/MySQL.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/MySQL.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::BayesStore::MySQL - MySQL Specific Bayesian Storage Module Implementation
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module implements a MySQL specific based bayesian storage module. It
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/PgSQL.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/PgSQL.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/PgSQL.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/PgSQL.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::BayesStore::PgSQL - PostgreSQL Specific Bayesian Storage Module Implementation
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module implements a PostgreSQL specific bayesian storage module.
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/Redis.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/Redis.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/Redis.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/Redis.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::BayesStore::Redis - Redis Bayesian Storage Module Implementation
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module implementes a Redis based bayesian storage module.
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/SQL.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/SQL.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/SQL.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/BayesStore/SQL.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::BayesStore::SQL - SQL Bayesian Storage Module Implementation
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module implementes a SQL based bayesian storage module.
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Message/Metadata.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Message/Metadata.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Message/Metadata.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Message/Metadata.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::Message::Metadata - extract metadata from a message
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This class is tasked with extracting "metadata" from messages for use as
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Message/Node.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Message/Node.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Message/Node.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Message/Node.pm Sun Feb 18 18:32:04 2018
@@ -19,8 +19,6 @@
Mail::SpamAssassin::Message::Node - decode, render, and make available MIME message parts
-=head1 SYNOPSIS
-
=head1 DESCRIPTION
This module will encapsulate an email message and allow access to
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/PerMsgStatus.pm Sun Feb 18 18:32:04 2018
@@ -728,6 +728,7 @@ return a pointer to a hash for rule & sc
test names and individual scores of the tests which were triggered by the mail.
=cut
+
sub get_names_of_tests_hit_with_scores_hash {
my ($self) = @_;
@@ -745,6 +746,7 @@ return a comma-separated string of rule=
test names and individual scores of the tests which were triggered by the mail.
=cut
+
sub get_names_of_tests_hit_with_scores {
my ($self) = @_;
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DNSEval.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DNSEval.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DNSEval.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DNSEval.pm Sun Feb 18 18:32:04 2018
@@ -327,6 +327,7 @@ This checks all the from addrs domain na
=back
=cut
+
sub check_rbl_from_domain {
my ($self, $pms, $rule, $set, $rbl_server, $subtest) = @_;
_check_rbl_addresses($self, $pms, $rule, $set, $rbl_server, $subtest, $_[1]->all_from_addrs_domains());
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/TxRep.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/TxRep.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/TxRep.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/TxRep.pm Sun Feb 18 18:32:04 2018
@@ -20,7 +20,6 @@
Mail::SpamAssassin::Plugin::TxRep - Normalize scores with sender reputation records
-
=head1 SYNOPSIS
The TxRep (Reputation) plugin is designed as an improved replacement of the AWL
@@ -122,7 +121,7 @@ with the one bound to an IP address, DKI
factor for the EMAIL reputation is set to zero). AWL uses the score of 100 (resp. -100)
for the blacklisting (resp. whitelisting) purposes. TxRep increases the value
proportionally to the weight factor of the EMAIL reputation. It is explained in details
-in the section L</BLACKLISTING / WHITELISTING>. TxRep can blacklist or whitelist also
+in the section L<BLACKLISTING / WHITELISTING>. TxRep can blacklist or whitelist also
IP addresses, domain names, and dotless HELO names.
7. B<Sender Identification> - AWL identifies a sender on the basis of the email address
@@ -196,7 +195,8 @@ on the reputation checked: EMAIL, EMAIL_
ID is used only in the case of dual storage, and takes the form of either _U (for
user storage reputations), or _G (for global storage reputations).
-=cut # ....................................................................
+=cut
+
package Mail::SpamAssassin::Plugin::TxRep;
use strict;
@@ -265,7 +265,8 @@ Note that certain tests are ignored when
- rules with tflags set to 'noautolearn'
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'use_txrep',
default => 0,
@@ -273,7 +274,6 @@ Note that certain tests are ignored when
});
-# -------------------------------------------------------------------------
=item B<txrep_factor>
range [0..1] (default: 0.5)
@@ -293,7 +293,8 @@ long-term mean including also the new un
just use the calculated score, disabling so the score averaging, though still
recording the reputation to the database.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_factor',
default => 0.5,
@@ -306,7 +307,6 @@ recording the reputation to the database
});
-# -------------------------------------------------------------------------
=item B<txrep_dilution_factor>
range [0.7..1.0] (default: 0.98)
@@ -337,7 +337,8 @@ lower factors will help the reputation t
the same time, it will also reduce the impact of the historical reputation
though.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_dilution_factor',
default => 0.98,
@@ -375,7 +376,6 @@ though.
});
-# -------------------------------------------------------------------------
=item B<txrep_learn_penalty>
range [0..200] (default: 20)
@@ -385,7 +385,8 @@ be added to the total reputation score o
spam score. The impact of the penalty will be the smaller the higher is the
number of messages that the sender already has in the TxRep database.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_learn_penalty',
default => 20,
@@ -398,7 +399,6 @@ number of messages that the sender alrea
});
-# -------------------------------------------------------------------------
=item B<txrep_learn_bonus>
range [0..200] (default: 20)
@@ -408,7 +408,8 @@ deduced from the total reputation score
spam score. The impact of the penalty will be the smaller the higher is the
number of messages that the sender already has in the TxRep database.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_learn_bonus',
default => 20,
@@ -421,7 +422,6 @@ number of messages that the sender alrea
});
-# -------------------------------------------------------------------------
=item B<txrep_autolearn>
range [0..5] (default: 0)
@@ -433,7 +433,8 @@ resp. the L</C<txrep_learn_bonus>> in th
Value 0 at this option disables the auto-learn reputation adjustment - only the
score calculated before the auto-learn will be stored to the reputation database.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_autolearn',
default => 0,
@@ -446,7 +447,6 @@ score calculated before the auto-learn w
});
-# -------------------------------------------------------------------------
=item B<txrep_track_messages>
0 | 1 (default: 1)
@@ -457,7 +457,8 @@ to avoid false score adjustments due to
and to allow proper relearning of messages that were either previously wrongly
learned, or need to be relearned after modifying the learn penalty or bonus.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_track_messages',
default => 1,
@@ -465,7 +466,6 @@ learned, or need to be relearned after m
});
-# -------------------------------------------------------------------------
=item B<txrep_whitelist_out>
range [0..200] (default: 10)
@@ -482,7 +482,8 @@ reputation happens at every message sent
being sent to the recipient, the better reputation his email address will have.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_whitelist_out',
default => 10,
@@ -495,7 +496,6 @@ being sent to the recipient, the better
});
-# -------------------------------------------------------------------------
=item B<txrep_ipv4_mask_len>
range [0..32] (default: 16)
@@ -511,7 +511,8 @@ A value 0 is allowed but is not particul
whole internet as a single organization. The number need not be a multiple
of 8, any split is allowed.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_ipv4_mask_len',
default => 16,
@@ -527,7 +528,6 @@ of 8, any split is allowed.
});
-# -------------------------------------------------------------------------
=item B<txrep_ipv6_mask_len>
range [0..128] (default: 48)
@@ -544,7 +544,8 @@ allowed but is not particularly useful,
as a single organization. The number need not be a multiple of 4, any split
is allowed.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_ipv6_mask_len',
default => 48,
@@ -560,7 +561,6 @@ is allowed.
});
-# -------------------------------------------------------------------------
=item B<user_awl_sql_override_username>
string (default: undefined)
@@ -571,7 +571,8 @@ If this option is set the SQLBasedAddrLi
username with the value given. This can be useful for implementing global
or group based TxRep databases.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'user_awl_sql_override_username',
default => '',
@@ -579,7 +580,6 @@ or group based TxRep databases.
});
-# -------------------------------------------------------------------------
=item B<txrep_user2global_ratio>
range [0..10] (default: 0)
@@ -629,7 +629,9 @@ ID. In such case it is pointless enablin
maximally lead to two identical global storages in different locations.
This feature is disabled by default.
-=cut # ...................................................................
+
+=cut
+
push (@cmds, {
setting => 'txrep_user2global_ratio',
default => 0,
@@ -642,7 +644,6 @@ This feature is disabled by default.
});
-# -------------------------------------------------------------------------
=item B<auto_whitelist_distinguish_signed>
(default: 1 - enabled)
@@ -662,7 +663,8 @@ you are upgrading from AWL and using a p
column will not exist. It is recommended that you add this column, but if
that is not possible you must set this option to 0 to avoid SQL errors.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'auto_whitelist_distinguish_signed',
default => 1,
@@ -685,7 +687,8 @@ domains are hopefuly rare, and ask for t
=back
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_spf',
default => 1,
@@ -693,7 +696,6 @@ domains are hopefuly rare, and ask for t
});
-# -------------------------------------------------------------------------
=head2 REPUTATION WEIGHTS
The overall reputation of the sender comprises several elements:
@@ -750,7 +752,8 @@ without regarding the originating IP has
We recommend using a relatively low value for this partial reputation.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_weight_email',
default => 3,
@@ -762,7 +765,6 @@ We recommend using a relatively low valu
}
});
-# -------------------------------------------------------------------------
=item B<txrep_weight_email_ip>
range [0..10] (default: 10)
@@ -784,7 +786,8 @@ the sender more reliably than the IP add
This is by design the most relevant reputation, and its weight should be kept
high.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_weight_email_ip',
default => 10,
@@ -796,7 +799,6 @@ high.
}
});
-# -------------------------------------------------------------------------
=item B<txrep_weight_domain>
range [0..10] (default: 2)
@@ -823,7 +825,8 @@ because both ham and spam may be sent by
The default value is set relatively low. Higher weight values may be useful,
but we recommend caution and observing the scores before increasing it.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_weight_domain',
default => 2,
@@ -835,7 +838,6 @@ but we recommend caution and observing t
}
});
-# -------------------------------------------------------------------------
=item B<txrep_weight_ip>
range [0..10] (default: 4)
@@ -849,7 +851,8 @@ there may be cases when the same IP addr
senders (for example the marketing department of a company sends you spam, but
you still need to get messages from their billing address).
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_weight_ip',
default => 4,
@@ -861,7 +864,6 @@ you still need to get messages from thei
}
});
-# -------------------------------------------------------------------------
=item B<txrep_weight_helo>
range [0..10] (default: 0.5)
@@ -880,7 +882,8 @@ some of the HELO names.
This option is still considered experimental, hence the low weight value, but after
some testing it could be likely at least slightly increased.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_weight_helo',
default => 0.5,
@@ -893,7 +896,6 @@ some testing it could be likely at least
});
-# -------------------------------------------------------------------------
=back
=head1 ADMINISTRATOR SETTINGS
@@ -911,7 +913,8 @@ user's C<user_prefs> file.
Select alternative database factory module for the TxRep database.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'txrep_factory',
is_admin => 1,
@@ -920,7 +923,6 @@ Select alternative database factory modu
});
-# -------------------------------------------------------------------------
=item B<auto_whitelist_path /path/filename>
(default: ~/.spamassassin/tx-reputation)
@@ -930,7 +932,8 @@ has their own reputation database in the
mode 0700. For system-wide SpamAssassin use, you may want to share this
across all users.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'auto_whitelist_path',
is_admin => 1,
@@ -945,7 +948,6 @@ across all users.
});
-# -------------------------------------------------------------------------
=item B<auto_whitelist_db_modules Module ...>
(default: see below)
@@ -962,7 +964,8 @@ ie. a space-separated list of Perl modul
NDBM_File is not supported (see SpamAssassin bug 4353).
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'auto_whitelist_db_modules',
is_admin => 1,
@@ -971,7 +974,6 @@ NDBM_File is not supported (see SpamAssa
});
-# -------------------------------------------------------------------------
=item B<auto_whitelist_file_mode>
(default: 0700)
@@ -982,7 +984,8 @@ Make sure you specify this using the 'x'
to create directories. However, if a file is created, the resulting file will
not have any execute bits set (the umask is set to 0111).
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'auto_whitelist_file_mode',
is_admin => 1,
@@ -998,7 +1001,6 @@ not have any execute bits set (the umask
});
-# -------------------------------------------------------------------------
=item B<user_awl_dsn DBI:databasetype:databasename:hostname:port>
Used by the SQLBasedAddrList storage implementation.
@@ -1006,7 +1008,8 @@ Used by the SQLBasedAddrList storage imp
This will set the DSN used to connect. Example:
C<DBI:mysql:spamassassin:localhost>
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'user_awl_dsn',
is_admin => 1,
@@ -1014,14 +1017,14 @@ C<DBI:mysql:spamassassin:localhost>
});
-# -------------------------------------------------------------------------
=item B<user_awl_sql_username username>
Used by the SQLBasedAddrList storage implementation.
The authorized username to connect to the above DSN.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'user_awl_sql_username',
is_admin => 1,
@@ -1029,14 +1032,14 @@ The authorized username to connect to th
});
-# -------------------------------------------------------------------------
=item B<user_awl_sql_password password>
Used by the SQLBasedAddrList storage implementation.
The password for the database username, for the above DSN.
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'user_awl_sql_password',
is_admin => 1,
@@ -1044,7 +1047,6 @@ The password for the database username,
});
-# -------------------------------------------------------------------------
=item B<user_awl_sql_table tablename>
(default: txrep)
@@ -1055,7 +1057,8 @@ The table name where reputation is to be
=back
-=cut # ...................................................................
+=cut
+
push (@cmds, {
setting => 'user_awl_sql_table',
is_admin => 1,
@@ -1133,8 +1136,6 @@ sub _fn_envelope {
}
-
-# -------------------------------------------------------------------------
=head1 BLACKLISTING / WHITELISTING
When asked by SpamAssassin to blacklist or whitelist a user, the TxRep
@@ -1171,6 +1172,7 @@ In case of dual storage, the black/white
default storage.
=cut
+
######################################################## plugin hooks #####
sub blacklist_address {my $self=shift; return $self->_fn_envelope(@_, 100, "blacklisting address");}
sub whitelist_address {my $self=shift; return $self->_fn_envelope(@_, -100, "whitelisting address");}
@@ -1178,7 +1180,6 @@ sub remove_address {my $self=shift; r
###########################################################################
-# -------------------------------------------------------------------------
=head1 REPUTATION LOGICS
1. The most significant sender identificator is equally as at AWL, the
@@ -1214,6 +1215,7 @@ sub remove_address {my $self=shift; r
IP field) for the standalone IP reputation
=cut
+
###########################################################################
sub check_senders_reputation {
###########################################################################
@@ -1787,8 +1789,6 @@ sub pack_addr {
}
-
-# -------------------------------------------------------------------------
=head1 LEARNING SPAM / HAM
When SpamAssassin is told to learn (or relearn) a given message as spam or
@@ -1806,6 +1806,7 @@ does not detect when you learn the messa
the penalty/bonus score each time the message is fed to the spam learner.
=cut
+
######################################################### plugin hook #####
sub learner_new {
###########################################################################
@@ -1890,7 +1891,6 @@ sub learner_close {
}
-# -------------------------------------------------------------------------
=head1 OPTIMIZING TXREP
TxRep can be optimized for speed and simplicity, or for the precision in
@@ -1902,8 +1902,7 @@ C<user_prefs>. Disabling TxRep will not
re-enabled any time later again.
On many systems, SQL-based storage may perform faster than the default
-Berkeley DB storage, so you should consider setting it up. See the section
-L</SQL-BASED STORAGE> for instructions.
+Berkeley DB storage, so you should consider setting it up.
Then there are multiple settings that can reduce the number of records stored
in the database, hence reducing the size of the storage, and also the processing
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd.pm Sun Feb 18 18:32:04 2018
@@ -45,7 +45,7 @@ An instance should have lifetime of a si
Interface is likely to change.
-See the source code of L<spamd(1)> and L<Mail::SpamAssassin::Spamd::Apache2(3)>.
+See the source code of C<spamd(1)> and C<Mail::SpamAssassin::Spamd::Apache2(3)>.
=head1 AUTHORS
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2.pm Sun Feb 18 18:32:04 2018
@@ -381,10 +381,10 @@ See <http://bugzilla.spamassassin.org/>.
=head1 SEE ALSO
-L<httpd(8)>,
-L<spamd(1)>,
-L<apache-spamd(1)>,
-L<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
+C<httpd(8)>,
+C<spamd(1)>,
+C<apache-spamd(1)>,
+C<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
=cut
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclIP.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclIP.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclIP.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclIP.pm Sun Feb 18 18:32:04 2018
@@ -43,7 +43,7 @@ See <http://bugzilla.spamassassin.org/>
=head1 SEE ALSO
-L<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
+C<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
=cut
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclRFC1413.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclRFC1413.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclRFC1413.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/AclRFC1413.pm Sun Feb 18 18:32:04 2018
@@ -129,7 +129,7 @@ See <http://bugzilla.spamassassin.org/>
=head1 SEE ALSO
-L<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
+C<Mail::SpamAssassin::Spamd::Apache2::Config(3)>
=cut
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/Config.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/Config.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/Config.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Apache2/Config.pm Sun Feb 18 18:32:04 2018
@@ -26,10 +26,10 @@ Mail::SpamAssassin::Spamd::Apache2::Conf
=head1 DESCRIPTION
Provides Apache config directives for configuring spamd. Initializes the
-L<Mail::SpamAssassin> object.
+C<Mail::SpamAssassin> object.
-Note, that the defaults here apply to *this* code; L<apache-spamd.pl(1)>
-sets different ones to be compatible with L<spamd(1)>.
+Note, that the defaults here apply to *this* code; C<apache-spamd.pl(1)>
+sets different ones to be compatible with C<spamd(1)>.
=head1 DIRECTIVES
@@ -84,7 +84,7 @@ push @directives, { # inherited
Enables RFC 1413 (ident) checks incoming connections. Note, that checking
if a *remote* login matches a *local* one is usually pointless. See
-L<Mail::SpamAssassin::Apache2::AclRFC1413(3)> for more details.
+C<Mail::SpamAssassin::Apache2::AclRFC1413(3)> for more details.
Adds a handler:
@@ -162,7 +162,7 @@ push @directives, { # inherited
=item C<SANew key "value">
Additional arguments to C<Mail::SpamAssassin->new()>. Refer to
-L<Mail::SpamAssassin(3)>.
+C<Mail::SpamAssassin(3)>.
=cut
@@ -563,12 +563,12 @@ See <http://bugzilla.spamassassin.org/>.
=head1 SEE ALSO
-L<httpd(8)>,
-L<spamd(1)>,
-L<apache-spamd(1)>,
-L<Mail::SpamAssassin::Spamd::Apache2(3)>,
-L<Mail::SpamAssassin::Spamd::Apache2::AclIP(3)>,
-L<Mail::SpamAssassin::Spamd::Apache2::AclRFC1413(3)>
+C<httpd(8)>,
+C<spamd(1)>,
+C<apache-spamd(1)>,
+C<Mail::SpamAssassin::Spamd::Apache2(3)>,
+C<Mail::SpamAssassin::Spamd::Apache2::AclIP(3)>,
+C<Mail::SpamAssassin::Spamd::Apache2::AclRFC1413(3)>
=cut
Modified: spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Config.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Config.pm?rev=1824686&r1=1824685&r2=1824686&view=diff
==============================================================================
--- spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Config.pm (original)
+++ spamassassin/trunk/spamd-apache2/lib/Mail/SpamAssassin/Spamd/Config.pm Sun Feb 18 18:32:04 2018
@@ -26,14 +26,14 @@ This module uses Getopt::Long to parse a
Returns blessed hash reference, containing coherent set of options.
Dies on error.
-See source and L<spamd(1)> for list of valid options.
+See source and C<spamd(1)> for list of valid options.
=head1 WARNING
This interface is considered experimental and likely to change. Notify the dev
list if you're planning to rely on it.
-Getopt::Long::Configure is used to modify global L<Getopt::Long(3)>
+Getopt::Long::Configure is used to modify global C<Getopt::Long(3)>
configuration. If you don't want C<:bundling> and / or wish to enable /
disable something else for whatever reason... well, keep that in mind.
@@ -45,8 +45,8 @@ See <http://bugzilla.spamassassin.org/>
=head1 SEE ALSO
-L<spamd(1)>,
-L<apache-spamd(1)>
+C<spamd(1)>,
+C<apache-spamd(1)>
=cut