High-Performance E-Mail Virus Scanner
Amavisd-new is a high-performance interface between mailer (MTA) and
content checkers: virus scanners or SpamAssassin. It talks to the MTA
via (E)SMTP, LMTP. It works with the
following MTAs:
- postfix
- sendmail (sendmail-milter)
- exim
- Sources inherited from project SUSE:SLE-15-SP4:GA
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout SUSE:SLE-15-SP4:Update/amavisd-new && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| activate_virus_scanner.diff | 0000000900 900 Bytes | |
| amavis-v2.12.1.tar.bz2 | 0000874339 854 KB | |
| amavis.service | 0000001588 1.55 KB | |
| amavisd-new-2.10.1-myhostname.patch | 0000001153 1.13 KB | |
| amavisd-new-no-berkeleydb.patch | 0000000668 668 Bytes | |
| amavisd-new-rpmlintrc | 0000000312 312 Bytes | |
| amavisd-new.changes | 0000078845 77 KB | |
| amavisd-new.spec | 0000007567 7.39 KB | |
| sysconfig.amavis | 0000000571 571 Bytes | |
| system-user-vscan.conf | 0000000088 88 Bytes |
Latest Revision
Stefan Weiberg (suntorytimed)
committed
(revision 2)
- amavisd-new should require packets perl-IO-stringy and perl-Net-LibIDN
(bsc#1193291)
- Added hardening to systemd service(s). Modified:
* amavis.service
- Package amavisd-milter in a separate package
- Add perl(Convert::BinHex) to required packages
- Disable BerkeleyDB in configuration
+ amavisd-new-no-berkeleydb.patch
- update to version 2.12.1
* Generate DKIM record comment line including the 's=' (selector) tag
instead of an 'i=' (identifier) tag when using "amavisd showkeys".
* Make sure generated Authentication-Results follow RFC specification.
* Prevent re-encoding of notification templates.
* Compare inode numbers as strings.
* Resolve MySQL invalid utf8mb4 clause.
- cleanup spec
* align (Build)Requires and Recommends with upstream
* rework creating vscan user (new system-user in Tumbleweed)
- update to version 2.12.0
* Upstream changed to GitLab
* Introduce Rspamd client extension
With this extension, Amavis can use Rspamd either running on the same
server or remotely. Connections are made using HTTP/HTTPS depending on
configuration, the latter requiring a HTTPS-capable proxy (like NGINX or
Apache) for Rspamd, which does not natively support HTTPS. Basic
authentication with name/password pairs is also available.
Comments 0