I tried the backup again tonight. I am now getting a new error:
mail# doveadm backup -f -u doug remote:checkout
dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Warning: Deleting mailbox 'INBOX':
UID=92440 GUID=1465118975.V4eI7cfa32M232845.mail is missing locally
dsync-remote(doug)<1c8BDo4xtGe74wAA+d
On Mon, 2025-02-17 at 15:49 +0200, Timo Sirainen wrote:
On 16. Feb 2025, at 17.03, Ken Wright via dovecot
wrote:
mysql localhost {
user = something
password = MYPASSWORD
dbname = something
}
..
According to the logs,
I am using doveadm backup to backup the mail server's files for a specific
user. This is a test environment for the backup machine. All it does is sit
there until I run backup on the mail server. However, I am encountering an
issue occasionally where backup throws the following message:
Warn
[https://api.zakaria.website/users/hi@zakaria.website/
18c6ac51852b0fd2b88b95a6f0f931ab/316c09b3eb7d1b0f3816e0.png]
On 2025-02-17 18:51, Michael Slusarz wrote:
>> On 02/13/2025 8:18 AM MST Zakaria via dovecot
dovecot.org> wrote:
>>
>>
>> Hi Dovecot Mailing List members,
>>
>> I just struggled to un
> On 02/13/2025 8:18 AM MST Zakaria via dovecot wrote:
>
>
> Hi Dovecot Mailing List members,
>
> I just struggled to understand the plugin events and wondered if anyone
> can help on this.
>
> I wanted to capture the event when I mark message as not spam move event
> as well as when I mo
Thank you, Timo, that fixed the problem.
Asai
On 2/17/2025 9:03 AM, Timo Sirainen wrote:
On 17. Feb 2025, at 16.26, Asai via dovecot wrote:
sieve_script personal {
active_path = /vmail/%{user | domain }/%{user | username }/
home/.dovecot.sieve
driver = file
path = /vmail/%{user | domain }
Hi
Finally released 1.9.1 to catch-up with 2.4.x and git recent changes
Same "simplistic" approach
- You get what you search for, no approximation/elastic/stemming, any language
- No config required by default
- Drastically reduced storage required / Drastically improved indexing/
searching speed
Thanks Timo,
OK, I'll give that a try, I should point out that the Sieve filters are working
as they should be for general delivery, outside of doveadm backup.
Asai
On 2/17/2025 9:03 AM, Timo Sirainen wrote:
On 17. Feb 2025, at 16.26, Asai via dovecot wrote:
sieve_script personal {
active_pat
[https://api.zakaria.website/users/hi@zakaria.website/
7e34b3f8e1244ee5106da6c8e7eb358e/31f5bf93944ea6e04af8b6.png]
Thanks for the update.
On 2025-02-17 12:43, Joan Moreau via dovecot wrote:
> Hi
>
> Finally released 1.9.1 to catch-up with 2.4.x and git recent changes
>
> Same "simplistic" approac
Hi Timo, here's the config, the sieve section is at the bottom. Also,
note that due to upgrading Dovecot over the years, we have an odd "home"
folder situtation, where it's actually IN the main maildir folder,
rather than being its parent.
[root@server5 ~]# doveconf -n
# 2.4.0 (daeb6bc59c): /e
On 17. Feb 2025, at 12.46, Timo Sirainen via dovecot
wrote:
> Also I've attached a patch that allows using auth-workers with PostgreSQL
> with Dovecot v2.4. Maybe it'll be in v2.4.1.
>
> passdb sql {
> use_worker = yes
> }
Well, attachments don't seem to work on this list, so here's inline pa
On 17. Feb 2025, at 13.01, Timo Sirainen via dovecot
wrote:
>
> On 17. Feb 2025, at 12.46, Timo Sirainen via dovecot
> wrote:
>> Also I've attached a patch that allows using auth-workers with PostgreSQL
>> with Dovecot v2.4. Maybe it'll be in v2.4.1.
>>
>> passdb sql {
>> use_worker = yes
>>
Simple sha512 without multiple rounds is very fast and is not the cause of auth
slowness. But did you mean CRYPT-SHA512 instead?
If the problem isn't due to password hashing, I wonder why it is so slow. Is
the PostgreSQL library really being that slow? Would be interesting to get perf
traces fr
On 15. Feb 2025, at 4.06, Asai via dovecot wrote:
>
> Greetings,
>
> On 2.3 I was able to run the following command, but now on 2.4 I'm getting
> the following error:
>
> doveadm backup -u u...@domain.tld maildir:/mnt/backups/daily/domain.tld/user
>
> dsync(u...@domain.tld): Error: brain M: E
Hello,
I have a doubt:
is the lua function "auth_userdb_iterate" expected to always return the
whole list of users no matter what, or it should evaluate if a specific
virtual domain is provided as req argument and only list the users in
that specific domain?
And should the returned user lis
You are right, we are using sha512 and are discussing mass migrating to
sha256 if there is no other way to improve performance of the auth service
itself. but I'm afraid this will increase productivity by a maximum of two
times and the most loaded of the servers will restore the connection pool
aft
What IO do you mean? Service in memory, postgres too, how simple sql query
can be related to IO?
I think it depends on the processor, but seriously, each of our servers
have 10+K users. 48 per second is very low performance in this case. No
packet loss and I talk about the server restart situation
17 matches
Mail list logo
