Carsten,
i changed the options, but it didn't help.
Jun 20 22:59:31 my-postfix postfix/smtpd[6067]: timeout after DATA
(759117 bytes) from mail.foobar.org[111.222.111.222]
so in master.cf it looks like this:
188.xx.xx.xx inet n - - - - smtpd
-o smtpd_sasl_auth
Hello Mark,
i changed the options, but it didn't help.
Jun 20 22:59:31 my-postfix postfix/smtpd[6067]: timeout after DATA
(759117 bytes) from mail.foobar.org[111.222.111.222]
so in master.cf it looks like this:
188.xx.xx.xx inet n - - - - smtpd
-o smtpd_sasl_
Andrei,
I'm running amavisd-new-2.8.0 (20120630) on 9.1-RELEASE-p14 with perl
v5.16.3. I am using amavisd-new for mail filtering and DKIM
signatures. I have setup 4 domains with 4 different keys a while ago.
Today when I went back to that mail server and issued "amavisd
testkeys" I get one pass
Mathias,
I configured that if an attachment from a mail exceeds its decoding
depth goes to the quarantine with:
$final_destiny_by_ccat{+CC_UNCHECKED} = D_DISCARD;
$quarantine_to_maps_by_ccat{+CC_UNCHECKED} = ['banned-quarantine'];
$quarantine_method_by_ccat{+CC_UNCHECKED} =
$banned_files_quara
Christian wrote:
Hi, from my point of view the default value should be 1 but I've
tested both configuration parameter,
thats why this line is still part of my configuration even if its
disabled.
The $allowed_added_header_fields{lc('X-Amavis-OS-Fingerprint')} is on by
default.
The X-Amavis-O
Am Freitag, den 20.06.2014, 20:48 +0200 schrieb Mark Martinec:
>
> It is the SpamAssassin that is calling Net::DNS which expects
> file resolve.conf to reside in /etc by default.
>
> Moreover, if your version of Net::DNS is 0.76 or later, there is
> a compatibility issue with SpamAssassin. You ne
ben,
i’ve set log_level = 5; while installing/configuring, and see the
following logged during start:
Jun 10 20:06:13 server amavis[4190]: INFO: SA version: 3.4.0,
3.004000, no optional modules: auto::NetAddr::IP::full6
auto::NetAddr::IP::Util::inet_n2dx auto::NetAddr::IP::Util::inet_n2ad
auto:
Stefan,
today I updated my server to use some new systemd services, such as
systemd-networkd [1] and systemd-resolved [2]. Using systemd-resolved I
have to symlink /etc/resolve.conf to /run/systemd/network/resolv.conf.
Amavis-new seems to have a problem with this configuration because
these
me
Bruce Pennypacker wrote:
I just set up amavisd 2.9.0 on a CentOS server running postfix 2.6.6.
For
the most part things appear to be working properly, however I'm having
an
issue where spams with a bad header are making it through.
We resolved this issue with Bruce offline,
the rest is mainl
Carsten,
i am using amavis with postfix by sending mails to amavis via
smtpd_proxy_filter.
But amavis runs in a timeout, and i don`t know why.
Until now, it appears only with one single message, but I am afraid,
that this could happen more often in the future.
Jun 19 20:02:15 my-postfix post
amavis17,
I would like to contribute a patch to correctly parse the output of
unrar
v5. Without this, mail with rar attachments arrive as ***UNCHECKED***
and
in the logs are found lines like this:
amavis[18309]: (18309-18) (!)do_unrar: can't parse info line for ...
The output of unrar v ch
Hi
I configured that if an attachment from a mail exceeds its decoding depth goes
to the quarantine with:
$final_destiny_by_ccat{+CC_UNCHECKED} = D_DISCARD;
$quarantine_to_maps_by_ccat{+CC_UNCHECKED} = ['banned-quarantine'];
$quarantine_method_by_ccat{+CC_UNCHECKED} = $banned_files_quarantine_me
12 matches
Mail list logo
