That looks like base64 encoding to me. Possibly your sieve script is parsing
the output and truncating the data before handing it off to base64.
Doug
> -Original Message-
> From: Peter via dovecot
> Sent: Tuesday, April 9, 2024 2:03 PM
> To: dovecot@dovecot.org
> Subject: Re: Strange
This is ... bug like.
The user moves a folder inside another, the resulting path exceeds the maximum
length, the folder's content is no longer accessible, the user complains.
Double trouble. The user proceeded to move the parent folder. Most subfolders
moved as requested. Those whose path
Thanks for the advise.
Yes, the mails are automatically created. Unfortunately, the software
that generates them are out of our control.
I supposed that it is a base64 code, but if I try to manually pass the
text into 'base64 -d' - nothing usable goes out (you can try yourself
with the
> -Original Message-
> From: Peter via dovecot
> Sent: Tuesday, April 9, 2024 5:18 AM
> To: dovecot@dovecot.org
> Subject: Strange problem with sieve
>
> Hello,
>
> I use Dovecot 2.3.20 on FreeBSD 13.2 (in jail) as a part of iRedMail
> installation.
>
> Some mailboxes are configured
Hello James,
I get the exact same error when trying to compile Dovecot 2.3.21 on both Mac OS
Monterey 12.7.3 and Mac OS Ventura 13.6.4.
dbox-storage.c:296:32:error:no member named 'st_atim' in 'struct stat'
last_temp_file_scan = stats.st_atim.tv_sec;
Hello,
I use Dovecot 2.3.20 on FreeBSD 13.2 (in jail) as a part of iRedMail
installation.
Some mailboxes are configured for automatic mails processing using sieve
(execute :pipe) and a custom binary (started by script). The system was
configured and was working correctly during several weeks.
We haven't found any specific bugs with lib-ssl-iostream so far, but we did
find istream-multiplex bug that could cause hangs with doveadm-doveadm
connections. Could be worth testing if it helps:
https://github.com/dovecot/core/commit/bbe546bc637a6ac5c9e91fc8abefce62e4950d07
> On 30. Dec 2022,