Am 18.10.2018 um 15:36 schrieb Christian Rößner:
>
>
>> Am 09.10.2018 um 18:58 schrieb pgndev :
>>
>> The discussed 'facts' here include:
>>
>> amavisd is not actively maintained
>> it's a 1-persoon project, & the author's non-responsive to comms
>> it's perl
>> spam admin's a
Am 01.02.2018 um 18:14 schrieb Matus UHLAR - fantomas:
> The config is perl, you can do whatever you want and perl allows.
>
Did not know that, and I dont know perl either.
So I could theoretically include configs in a catalogue?
>
>>> Yes. The debian package for example already
As a guess, it was probably scanning a big attachment.
ObAdvice: *don't* use kill -9.
HTH
T.
On 08.06.2017 20:59, Curtis NPC wrote:
> Ok, I was premature in that. I was worried that several amavis processes
> were going to start up again.
> Eventually that process that I described disappeared.
On 31.05.2017 16:56, Nikolaos Milas wrote:
> On 31/5/2017 1:28 μμ, Dominic Raferd wrote:
>
>> For this you need an antivirus tool. Clamav in its standard form is
>> pretty useless IMHO but it is rather more effective with the
>> sanesecurity addon signatures.
>
> I do have sanesecurity addon
is:
>>> Good evening all
>>>
>>> We have been running Postfix/Cyrus/Amavis on CentOS for over 10 years.
>>>
>>> Now we are faced with upgrading from CentOS 5 due to EOL. Choices
>>> are CentOS 6 and 7. Comments as to best choice would be greatly
&
ong.
Also watch "top" in a second window during the test to see which process
is causing the CPU load.
And third, it looks like the delay is happening when Amavis is
forwarding the mail to the MTA on localhost:10025 so you should check
your Postfix log, too, correlating it with the Amavis lo
en matter because the time is consumed by clamscan before it even
starts scanning.
HTH
T.
--
Tilman Schmidt
cardtech
Card & POS Service GmbH
Richard-Byrd-Straße 37
50829 Köln
On 09.11.2016 20:57, @lbutlr wrote:
> On Nov 8, 2016, at 2:49 AM, Tilman Schmidt <tschm...@cardtech.de> wrote:
>> On 02.11.2016 10:46, Indunil Jayasooriya wrote:
>>>
>>> pls try below command with less
>>>
>>>
>>> less /etc/amavisd.conf
On 02.11.2016 10:46, Indunil Jayasooriya wrote:
>
> pls try below command with less
>
>
> less /etc/amavisd.conf |grep -i sa_spam_subject_tag
Argh. Useless use of less is even worse than useless use of cat.
Just do
grep -i sa_spam_subject_tag /etc/amavisd.conf
HTH
Tilman
On 27.05.2016 10:07, A. Schulze wrote:
>
> Olivier CALVANO:
>
>>> kernel:BUG: soft lockup - CPU#5 stuck for 24s! [/usr/sbin/amavi:32636]
>
> I would not blame amavis on errors starting with "kernel:BUG"
Why not?
On 12.05.2016 01:48, Daniel Funke wrote:
> I tried:
>
> $policy_bank{'IN_PRE_QUEUE'} = {
> syslog_ident => 'amavis-prequeue',
> sql_clause => { 'sel_policy' => "SELECT * FROM amavisd_select_policy
> WHERE policy_bank='IN_PRE_QUEUE' AND users.email IN (%k)" },
> }
>
> And here
On 06.05.2016 00:41, Bill Measday wrote:
> Could someone please explain to me in setting up banned_filename_re in
> amavisd.conf why some entries have an "i" on the end.
>
> For example:
>
> qr'^\.(exe-ms|dll)$', # banned file(1) types,
> rudimentary
>
> doesn't, but
>
>
On 28.04.2016 03:42, @lbutlr wrote:
> On Apr 26, 2016, at 8:07 AM, Tilman Schmidt <tschm...@cardtech.de> wrote:
>> Running Postfix with amavisd-new and quarantining attachments seems to
>> produce an unfortunate interaction when mail with a banned attachment
>> arriv
On 26.04.2016 17:46, Mark Martinec wrote:
>
> The "text/plain,.exe" means the declared MIME part was text/plain,
> but the file(1) utility decided that it is some kind of executable.
>
> Your sample (decoded and given to a file(1) utility) here reports:
>
> Python script, Non-ISO
Running Postfix with amavisd-new and quarantining attachments seems to
produce an unfortunate interaction when mail with a banned attachment
arrives for an unknown recipient:
Amavis checks the mail for banned attachments before checking whether
the recipient exists.
If $warnbannedrecip = 1 it then
On 26.04.2016 13:38, Olivier Nicole wrote:
> Tilman Schmidt <tschm...@cardtech.de> writes:
>
>> That's cute: when I got my copy of that message back from the list
>> processor it was also flagged as containing a text/plain,.exe
>> attachment. So whatever it is that l
16 matches
Mail list logo
