| Name : perl-Mail-SpamAssassin-Plugin-SAGrey
| |
| Version : 0.02
| Vendor : Mageia_Org
|
| Release : 13.mga8
| Date : 2020-02-12 06:34:22
|
| Group : Development/Perl
| Source RPM : perl-Mail-SpamAssassin-Plugin-SAGrey-0.02-13.mga8.src.rpm
|
| Size : 0.01 MB
| |
| Packager : umeabot < umeabot>
| |
| Summary : The SAGrey plugin for SpamAssassin
|
Description :
Mail::SpamAssassin::Plugin::SAGrey is a SpamAssassin plugin that provides a
limited amount of greylisting functionality using SpamAssassin\'s existing
services.
SAGrey is two-phased, in that it first looks to see if the current score of
the current message exceeds the user-defined threshold value (as set in one
of the cf files), and then looks to see if the message sender\'s email and IP
address tuple are already known to the auto-whitelist (AWL) repository. If the
message is spam and the sender is unknown, SAGrey assumes that this is one-time
spam from a throwaway or zombie account, the SAGREY rule fires, adds 1.0 to the
current message score, and optionally creates a header field in the message
itself. The rulename or header field can then be used to perform additional
greylisting functions (EG, having your delivery or transfer agent defer
delivery), or the score by itself can be used to penalize the message.
This model has two benefits over MTA-specific greylisting mechanisms: first, it
only subjects probable-spam to greylisting (instead of making everybody be
deferred, which has known problems), and it repurposes the existing
spamassassin history database (meaning no additional databases need to be
maintained). Another benefit is that it can still work at the MTA level if
your MTA can call spamassassin while the transfer is active and then defer
delivery based on the presence of header-field data (postfix 2.x will not do
this unfortunately, since the header checks don\'t provide a DEFER verb), but
can also be used in other models (such as delivery routines).
|
RPM found in directory: /vol/rzm3/linux-mageia/distrib/8/armv7hl/media/core/release |
