Re: Dovecot v2.4.0 released

2025-02-07 Thread hi--- via dovecot
It could be due to business model reason, where dovecot sees greater opportunity in reserving certain features to the pro release, they can perhaps allocate more resources as a result and work more on it. As oppose If they leave it in community release it will have less priority to features the

Re: question from a newbie

2025-02-06 Thread hi--- via dovecot
https://doc.dovecot.org/2.4.0/core/plugins/fs_compress.html On 2025-02-06 06:51, Aki Tuomi wrote: fs_compress is not intended to be loaded like that. It's enough to load just mail_compress. Aki On 05/02/2025 23:28 EET hi--- via dovecot wrote: In maildir format, you will find cur folder, i

Re: question from a newbie

2025-02-06 Thread hi--- via dovecot
/fs_driver=compress -o fs/posix/fs_driver=posix -o fs_posix_prefix=/mail/zakaria.website/hi@zakaria.website/ fs get test cur/messagefile Aki On 06/02/2025 14:37 EET hi--- via dovecot wrote: Oh, I didn't mention the first error, probably because I thought it was caused by the latter. When

Re: question from a newbie

2025-02-05 Thread hi--- via dovecot
In maildir format, you will find cur folder, it should contain all emails in inbox and you can open it unless it was compressed and if it was you can use doveadm to decompress it:- e.g. :- doveadm fs get compress zstd:6:posix:prefix=/ "/mail/zakaria.website/hi@zakaria.website/cur/MESSAGEFILENA

Re: Fatal: block_alloc(134217728): Out of memory

2025-02-05 Thread hi--- via dovecot
Check dovecot service status memory usage and since it was started, if its over available RAM, restarting the service every now and then might fix this, if its below RAM limit, it could be other services leaving dovecot without enough RAM, and if it wasnt a bug or misconfiguration in dovecot pe

Re: Bad Signature - iOS email content loading issue

2025-02-05 Thread hi--- via dovecot
Check logs while debug mode enabled? It might provide some insight on the issue thats causing the failure! On 2025-02-05 16:20, Zieseniss Peter via dovecot wrote: Hello All, i hope everyone is well! i have a rather irksome and pressing issue that i can't seem to resolve.. This happens only

Re: Bad Signature - Error in tests for Dovecot 2.4.0 aarch64

2025-02-07 Thread hi--- via dovecot
You might need to upgrade pigeonhole first. I had test failures and gone away when upgraded pigeonhole first. Also, I had test failures as result of outdated bison binary, I used to have 3 and upgraded to 3.8 and everything worked just fine. On 2025-02-07 07:48, Peter via dovecot wrote: When a

Re: [Dovecot-news] Dovecot v2.4.0 released - FTS plugin also released

2025-02-02 Thread hi--- via dovecot
Hi all, I just wanted to say thanks for all your efforts and bringing this looking to be promising release together. I spent the last two days tinkering with old and new configurations. Sadly I had to revert back to 2.3.21😭. Everything worked just fine including compression and sieve and secur

Re: crash on authentication to 2.3.21

2025-02-09 Thread hi--- via dovecot
Try to identify the root problem, enable debug mode in logs, and post all relevant errors, also take backup of the passwd file, and create empty one and try yo add one working user you are 100% their credentials is accurate and check the log result, it could be current passwd file is corrupt. A

Re: [Dovecot] auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied

2025-04-05 Thread hi--- via dovecot
Hi All, I think this bug is back in dovecot 2.4.1. I'm getting:- lmtp(15118): Error: conn unix:/run/dovecot/anvil: net_connect_unix(/run/dovecot/anvil) failed: Permission denied I run following post service start to fix it, I set: chmod 666 /var/run/dovecot/anvil I tried setting mode = 0666 i