On 9 Feb 2023, at 21:22, Damian wrote:
>
>> I would like to always_bcc to two different recipients, is this possible?
> Surprisingly, amavis does not seem to support it.
I was thinking of “fixing” this by setting always_bcc to a local alias such as
archive@localhost and then expanding this in P
Hi,
I would like to always_bcc to two different recipients, is this possible? If so
what is the recommended way to do so?
Cheers,
Arrigo
Finally managed to capture logs of what is happening:
Sep 1 08:43:15 mailgate-fra-1 amavis[45261]: (45261-01) LMTP [127.0.0.1]:10024
/var/amavisd/tmp/amavis-20220901T084315-45261-5iOqP3Cd: ->
SIZE=389475 BODY=7BIT Received: from
mailgate-fra-1.example.com ([127.0.0.1]) by localhost
(mailgat
On 30 Aug 2022, at 15:27, Damian wrote:
>> Aug 30 12:50:09 mailgate-fra-1 amavis[24524]: (24524-01) truncating a
>> message passed to SA at 414138 bytes, orig 569545
>>
>> [process gets killed after 5m]
>>
>> Aug 30 12:54:48 mailgate-fra-1 amavis[24524]: (24524-01) (!)TempDir removal:
>> tempd
OK, so this is getting surreal.
I went to fetch the email from $TEMPFILE which had caused a stalled Perl
process (i.e. process time > 5m) and, running it individually (on the parts)
using spamassassin on the command line I get:
/var/amavisd/tmp/amavis-20220830T125008-24524-HdayDdgJ/parts
spama
On 29 Aug 2022, at 16:51, Damian wrote:
>
>> I was wondering if anyone is seeing similar behaviour or has any
>> recommendations to debug this further.
> Depending on your mail throughput, you could increase $log_level up to 5 and
> see what is being logged right before the lockup. Additionally
Hi all,
about two weeks ago two of my servers with the heaviest load suddenly started
taking 30-40 minutes to process some messages.
I am running on OpenBSD 7.1 on two 8-core Xeon D-1541 @ 2.10GHz with software
RAID 1 with two SSDs and the standard packages:
amavisd-new-2.12.0p0
postfix-3.5.14
