Name: | exim-greylist |
---|---|
Version: | 4.94 |
Release: | 2.el7 |
Architecture: | x86_64 |
Group: | System Environment/Daemons |
Size: | 6502 |
License: | GPLv2+ |
RPM: | exim-greylist-4.94-2.el7.x86_64.rpm |
Source RPM: | exim-4.94-2.el7.src.rpm |
Build Date: | Sun Apr 11 2021 |
Build Host: | e6972c51f22143c1aedc6b512cce9746 |
Vendor: | Oracle America |
URL: | https://www.exim.org/ |
Summary: | Example configuration for greylisting using Exim |
Description: | This package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional. |
- Fixed cname handling in TLS certificate verification Resolves: rhbz#1942583
- New version Resolves: rhbz#1842590 - Used Exim maintainers keyring for GPG verification - Dropped CVE-2020-12783 patch (upstreamed) - Used better workaround for rhbz#1791878 Resolves: rhbz#1842633
- Fixed out-of-bounds read in the SPA authenticator Resolves: CVE-2020-12783
- Enabled spf2 and opendmarc support Resolves: rhbz#1829076
- Rebased to 4.93 Resolves: rhbz#1827425
- New version Resolves: rhbz#1756656 Resolves: CVE-2019-16928
- New version Resolves: CVE-2019-15846
- New version Resolves: rhbz#1742312
- New version - De-fuzzified patches
- Enabled DANE support Resolves: rhbz#1693202 - De-fuzzified support-proxies patch