Amavis *should* detect encrypted archive mail and log as “UNCHECKED-ENCRYPTED”.
Disposition of such mail is dependent on CC_UNCHECKED (final destiny) in your
amavisd.conf. There is a setting to rewrite Subject when unchecked disposition
is set to pass.
* a string can be prepended to Subject (
> On 23.11.2020., at 19:30, Joe Acquisto-j4 wrote:
>
> Looking to add AV scanning to an existing SoHo, Postfix/SA setup. At the
> moment prefer to use Sophos AV, Linux version to scan.
Amavis configuration file amavisd.conf has all the recommended settings for SAV
(Sophos AV), specifically
> On Jan 22, 2020, at 11:07 AM, Alessandro De Zorzi wrote:
>
> My final working integration for Antivirus Ikarus with Amavis on Linux
> Debian system:
>
> ### https://www.ikarussecurity.com/
> ['IKARUS scan.server',
> \&ask_daemon,
> ["GET /virusscan?filename={}/../email.txt HTTP/1.0\r\n\
> On Jul 23, 2019, at 3:20 PM, Benedict White
> wrote:
>
> I have just ran some updates on my server (because I had to) and was using
> Amavisd from 2017 (2.11)
>
> I am getting HAM blocked with messages like this:
>
> blocking contents category is (6)
>
> followed by
>
> Jul 22 16:54:3
> On Jul 19, 2019, at 2:56 PM, mabi wrote:
>
> Hello,
>
> I would like to log the typical X-Spam-Status mail header which gets added by
> SpamAssassin to a mail into the amavis log file in order to track the rules
> and their scores which gets triggered by ham and spam mails.
>
> Is this s
> On Jul 9, 2019, at 3:07 AM, Rich Wales wrote:
>
> I'm running amavisd-new version 2.11.0 on my Ubuntu mail server, which I
> recently upgraded to Ubuntu 18.04 LTS.
>
> Up till now, I've been using a locally patched version of MailZu to
> manage the Amavis quarantine. (This server is just f
> On Mar 27, 2019, at 10:11 PM, Nick Howitt wrote:
>
> What is weird is I've been down this route. "grep bayes /etc/* -r" returned
> one commented line in /etc/mail/spamassassin/v320.pre:
>
> # and create a header containing ASN data for bayes tokenization.
>
>
> and that is it. I also
> On Dec 11, 2018, at 2:12 PM, Fred Smith
> wrote:
>
>
> I'm running amavisd-new 2.11.1 and using SQL for lookups.
>
> The problem was discovered when large emails were being bounced when there is
> an SQL entry for the email address that should allow the large mail.
>
> In general I defin
> On Oct 18, 2018, at 16:31, Matus UHLAR - fantomas wrote:
>
> Hello,
>
> I am trying to get rid of annoying "Open relay?" messages and later set up
> DKIM signing, which both I believe are doable by properly setting
> @mynetworks.
>
> the README.lookups says:
>
> @mynetworks_maps = (read_ar
> On Sep 19, 2018, at 14:15, Vitali Quiering wrote:
>
> Do I need amavisd-milter? If yes, why? What’s different besides before or
> after queue?
Using Milters potentially solves your problem. Your receiving front-end Postfix
talks smtpd_milters protocol over HAProxy TCP mode to load-balanced
> On Aug 24, 2018, at 21:56, David Newman wrote:
>
> Replying to my own message: I noticed that Spamassassin sets
> required_score to 5.0 (line 818 in the Pastebin file below), but the
> message headers and debug log show amavisd setting 'required=0' (lines
> 16 and 2445 in the Pastebin file).
> On Jul 25, 2018, at 12:50, Simon Wilson wrote:
>
> Quoting Simon Wilson :
>
>> Hi list, wondering if I can get some help with the below.
>>
>> I have run a small Postfix mail server for many years, with amavisd and
>> spamassassin. We have about 10 users, 95% of the time using only Horde
> On Jul 13, 2018, at 14:47, Andreas Büthe wrote:
>
> The version used is 'amavisd-new 2.11.0-2el7' (CentOS 7 from epel) without
> chroot. I checked basics like the suid bit on /usr/bin/sudo, the filesystem /
> where /usr resides on is not mounted 'nosuid', SELinux is currently disabled
> fo
> On May 31, 2018, at 06:43, Philip wrote:
>
> Afternoon list,
>
> I've got spamassassin set up to read from a MYSQL database. It's working
> nicely but it's not sending 'amavis' across as the user not the email address
> (as the username) of the virtual user. I was wondering if this is th
> On Feb 26, 2018, at 19:36, Dauser Martin Johannes
> wrote:
>
> within amavis:
> ##
>
> A) As those mails are successfully DKIM signed you could do a hard or
> soft whitelist by selecting a custom policy bank based on successful
> DKIM and sender's envelope address (Return-Path: )
> On Jan 19, 2017, at 16:55, Martin Schmid wrote:
>
> I accidently didn't reply to the list before, so here's a little summary:
>
> In general, my setup is working flawlessly with amavis as frontend and xmail
> as backend server.
> Since amavis behaves as a kind of proxy, it also sends the er
> On Jan 19, 2017, at 11:40, Dino Edwards wrote:
>
> He said that he is not using postfix or any other SMTP servers as first
> receiver before Amavis so that can't be it, please see below. So, the way he
> describes it, amavis is listening on port 25 and I'm not sure how this whole
> thing wo
> On Jan 18, 2017, at 15:56, Martin Schmid wrote:
>
> Hello everybody
>
> I'm seeing many connections that try a few commands an then leave an open
> connection until it times out.
> I suspect most of them to try to block connections hich they do with a
> certain success.
>
> I couldn't figu
> On Dec 22, 2016, at 21:35, DaLiV wrote:
>
> amavisd archivers works only on piped in command line content
> as amavisd have such construction:
> sub run_command($$@) {
> .
> my $msg = join(' ', $cmd, @args, "<$stdin_from", "2>$stderr_to");
> .
>
> so not possible to configure behavio
> On Dec 11, 2016, at 07:24, Asif Iqbal wrote:
>
> How do I make sure it is working? After I configured like below, I restarted
> amavisd and postfix and I am seeing a lot of
> ``RelayedOpenRelay'' like below..
You should configure @local_domains_maps and @mynetworks, for amavisd to be
able
On May 22, 2014, at 4:29 AM, Gregory Sloop via amavis-users wrote:
> However, we can't just block every .zip file for example. Some zips from some
> senders are legit.
> Further, I don't want to block mail without generating a bounce reply. [An
> alternative would be rejecting it before accept
Hi,
When running before-queue Postfix content filter and once amavisd-new re-inject
message back to Postfix via SMTP on specific IP:PORT, it returns the positive
SMTP response back to Postfix which looks like this:
250 2.0.0 Ok, id=01187-05, from MTA([127.0.0.1]:10026): 250 2.0.0 Ok: queued as
22 matches
Mail list logo
