> On 29/07/2025 09:25 EEST Aki Tuomi via dovecot wrote:
>
>
> > On 29/07/2025 00:58 EEST Ákos Szőts via dovecot wrote:
> >
> >
> > Hi All,
> >
> > In Dovecot 2.4.1 if I start doveadm force-resync with a non-existent
> > mailbox that end
> On 29/07/2025 00:58 EEST Ákos Szőts via dovecot wrote:
>
>
> Hi All,
>
> In Dovecot 2.4.1 if I start doveadm force-resync with a non-existent
> mailbox that ends in a slash, the command crashes:
>
> gdb -ex run --args doveadm force-resync -A test/
>
Tha
Hi All,
In Dovecot 2.4.1 if I start doveadm force-resync with a non-existent
mailbox that ends in a slash, the command crashes:
gdb -ex run --args doveadm force-resync -A test/
Thread 1 (Thread 0x7f9e5cc4a980 (LWP 442) "doveadm"):
#0 fs_list_next_root (ctx
Hi,
are there anywhere recommendations or 'best practices' for compiling
dovecot-2.4.x at IBMs AIX7.3?
With some own patches i can compile it, but one unexpected result is
# /usr/local/bin/doveadm mailbox list -u
/usr/local/bin/doveconf: invalid option -- u
What's wrong?
--
M
> On 27/07/2025 14:26 EEST jlh via dovecot wrote:
>
>
> Hi all
>
> In 2.3, I could use doveadm from the docker image as a standalone tool, but
> this no longer works in 2.4:
>
> $ docker run --rm -ti dovecot/dovecot:2.3-latest doveadm
Hi all
In 2.3, I could use doveadm from the docker image as a standalone tool, but
this no longer works in 2.4:
$ docker run --rm -ti dovecot/dovecot:2.3-latest doveadm
usage: doveadm [-Dv] [-f ] []
altmove [-u |-A] [-S ] [-r]
[...snip...]
$ docker run --rm -ti
Hello,
I'm getting a fatal error when I try to run the authCacheFlush command via
the doveadm HTTP API.
Example of the call:
curl -u user:password -X POST [1]http://localhost:9010/doveadm/v1 -H
"Content-Type: application/json" -d
'[["authCacheFlush&q
* Aki Tuomi via dovecot:
> try creating /etc/dovecot/conf.d/ssl.conf and put the ssl config
> there, then have !include_try /etc/dovecot/conf.d/*.conf and chmod
> 0600 ssl.conf?
That's a neat workaround for the time being. Thank you, Aki.
-Ralph
___
do
Thanks, that works well for my situation.
I fear it'll be far less clear-cut for doveadm though. (But probably it was
always true that some subcommands would work and some not depending on invoking
user's privilege, and there weren't guardrails against such issues, is that
right
anyway).
>
> >The technical reason might be that dovecot.conf is parsed for each
> doveadm invocation?
>
> This is borne out by the manpage:
> "All standalone programs, such as dovecot(1), will first get their settings
> by executing doveconf, unless they can get the set
loosening permissions on private key file(s) or
invoking dovecot-lda as root are suboptimal to say the least (the latter would
probably break my virtual mailbox config anyway).
>The technical reason might be that dovecot.conf is parsed for each
doveadm invocation?
This is borne out by the manpage:
&q
The following came as a nasty surprise while testing Dovecot 2.4.1-4:
alice@host $ doveadm mailbox list -u $(whoami)
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf
line 61: cert_file: open(/path/to/cert.pem) failed: Permission denied
Unprivileged user Alice does not
Hi,
I’m looking for guidance on how to use doveadm sync with flags -f (full
synchronization) and -s. (stateful synchronization)
After reading the doveadm-sync man page it seems one should do the following:
(omitting -u -l -N flags for clarity)
1. First sync: doveadm sync -f
2. Second sync
Kamil Jońca via dovecot writes:
[...]
>
> %doveadm search -u kjonca mailbox .EXPUNGED|head -n 1
> 08ac303413c11168864d2a00a6f72b09 30802
its even more weird for me:
(there is only one email in z/1 mailbox)
--8<---cut here---start->8---
kjonca
On 6. May 2025, at 11.47, Kamil Jońca via dovecot wrote:
>
> Timo Sirainen via dovecot writes:
>
> [...]
>>
>> Looks like unless you explicitly specify "mailbox" parameter, it's skipping
>> the list=no namespaces. Pretty sure v2.3 worked the sam
Timo Sirainen via dovecot writes:
[...]
>
> Looks like unless you explicitly specify "mailbox" parameter, it's skipping
> the list=no namespaces. Pretty sure v2.3 worked the same way. You could just
> bypass the "doveadm search" step?
>
I am afraid not.
en = yes
> inbox = no
> list = no
> prefix = .EXPUNGED/
> separator = /
> }
>
> %doveadm search -u kjonca mailbox .EXPUNGED|head -n 1
> 08ac303413c11168864d2a00a6f72b09 30802
> %doveadm fetch -u kjonca text mailbox-guid 08ac303413c11168864d2a00a6f72b09
> uid 30802
&
Tim Dickson via dovecot writes:
> don't send the output to head -n1 and you'll get more than one line if
> the data is there :-)
>
Could you please elaborate?
head -n 1 is to get only one message ids (and it works - as you could
see)
but trying to fetch this message fails (and this command is n
h = ~/Mail/expunged/
mailbox_list_layout = fs
hidden = yes
inbox = no
list = no
prefix = .EXPUNGED/
separator = /
}
%doveadm search -u kjonca mailbox .EXPUNGED|head -n 1
08ac303413c11168864d2a00a6f72b09 30802
%doveadm fetch -u kjonca text mailbox-guid 08ac303413c11168864d2a00a6
debian package
2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf
I have namespace:
namespace expunged {
mail_driver = maildir
mail_path = ~/Mail/expunged/
mailbox_list_layout = fs
hidden = yes
inbox = no
list = no
prefix = .EXPUNGED/
separator = /
}
%doveadm search -u kjonca
Hi!
The following command segfaults on Dovecot 2.4:
#> doveadm proxy kick foo bar
Segmentation fault (core dumped)
Giving only one user (doveadm proxy kick foo) works:
#> doveadm proxy kick foo
0 connections kicked
It does not matter if the users actually exist on the server (so the
> On 25/03/2025 10:10 EET Michael Goth via dovecot wrote:
>
>
> Hi!
>
> The following command segfaults on Dovecot 2.4:
>
> #> doveadm proxy kick foo bar
> Segmentation fault (core dumped)
>
>
> Giving only one user (doveadm proxy kick foo) wo
> On Feb 18, 2025, at 05:59, Doug via dovecot wrote:
>
> My experience was very similar when I originally set up doveadm backup from
> my production machine to my backup machine. My mailbox was the only one on
> the system that failed. I discovered the root cause was a cron job r
My experience was very similar when I originally set up doveadm backup from
my production machine to my backup machine. My mailbox was the only one on
the system that failed. I discovered the root cause was a cron job running
on the backup machine delivering its output to my email. The result was
> On Feb 17, 2025, at 23:11, Doug Hardie wrote:
>
> 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
> 'I
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)&
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 me
}/%{user | username }/home/sieve
}
Looks like %variables aren't really working right with Sieve / doveadm
combination. It gives an error:
Error: sieve: sieve_file_storage settings: Failed to parse configuration:
Failed to expand sieve_script_path setting variables: Unknown variable 'use
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 per
re
}
sieve_script after {
path = /vmail/sieve/junk-spam.sieve
type = after
}
On 2/17/2025 3:19 AM, Timo Sirainen wrote:
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 ba
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(
You don't necessarely enable imap_metadata for this, just having attribute dict
is enough.
can you rm -rf the backup and try again with doveadm -D?
Aki
> On 16/02/2025 23:47 EET Asai via dovecot wrote:
>
>
> After spending several hours troubleshooting this, it seems like
After spending several hours troubleshooting this, it seems like doveadm
backup is broken somehow. At least on my system.
I can't even run doveadm backup -u user maildir:/dest on an empty target
director without it throwing an error.
Is anyone else having this problem?
Thanks,
Asai
dsync(u...@domain.tld): Debug: brain M: Syncing mailbox
77727820079bdd584f28773ea8bd: UIDNEXT changed: 12170 -> 1
Feb 15 18:33:44 dsync(u...@domain.tld): Debug: doveadm-sieve: Iterating
Sieve mailbox attributes
Feb 15 18:33:44 dsync(u...@domain.tld): Debug: sieve: Pigeonhole version
2.4.
I am using doveadm backup to backup mailfiles to a second drive. That works
just fine. However, the sieve files are not backed up. I couldn't find
anything in the backup documentation that addresses sieves. Is there a way to
back those up also?
--
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: Exporting mailbox INBOX failed:
Mailbox attribute iteration f
On 13/02/2025 19:30 EET Sean McBride via dovecot
wrote:
On 12 Feb 2025, at 13:52, Michael Slusarz wrote:
>> It says here https://www.dovecot.org/bugreport-mail/ that bug
reports should go to this list. Does that apply to suggestions too?
Assumin
On 12 Feb 2025, at 13:52, Michael Slusarz wrote:
>> It says here https://www.dovecot.org/bugreport-mail/ that bug reports should
>> go to this list. Does that apply to suggestions too? Assuming so...
>
> Best practice these days is to file a bug report (or MR) to GitHub.
I guess that web page
GitHub.
https://github.com/dovecot/ shows the various Dovecot components.
We are actively working on improving our various websites, so this updated
recommendation will (eventually) work its way on the pages somewhere.
> The docs here are very good:
>
> https://doc.dovecot.org/main/co
Hi all,
It says here https://www.dovecot.org/bugreport-mail/ that bug reports should go
to this list. Does that apply to suggestions too? Assuming so...
The docs here are very good:
https://doc.dovecot.org/main/core/man/doveadm-pw.1.html
but it's always nice to have examples of cu
Hello again,
After taking more time trying to undestand the output of `doveadm sync
-s`, i found out that the comamnd is unusable when called for multiple
users (using -A, -F, or -u options).
I found several issues:
- The command output a state for every user. This makes sense, however
Hello,
With the removal of the replication plugin in next releases, i'm trying
to setup automatic synchronization using doveadm sync between my master
and my replica.
I managed to make the full sync work from my replica using the following
comamnd `sync -A -N -R -f tcp:master-fqdn:
Hello,
What is the best way to backup (migrate) sieve rules?
I tried:
"doveadm backup -u somebox@somedomain maildir:/backup_dir"
"doveadm backup -u somebox@somedomain remote:newmailserver.somedomain"
Messages are copied but sieve rules are not.
dovecot --version: 2.3.21.1
dov
I get the following output (edited)
>>> :~$ sudo doveadm mailbox list -A
doveadm(nobody): Error: mkdir(/home/vmail/mailboxes//nobody) failed:
Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +w
perm: /home/vmail/mailboxes/, dir owned by 1001:1001 mode=0755)
dovead
Poldi via dovecot skrev den 2025-01-23 08:11:
I'm using Dovecot 2.3.21 (47349e2482) on Ubuntu and have convigured
virtual mail users.
Everything is working finem but a few doevadm commands fail
sudo doveadm mailbox list
returns
doveadm(root): Error: chdir(/root/) failed: Permission d
I'm using Dovecot 2.3.21 (47349e2482) on Ubuntu and have convigured virtual
mail users.
Everything is working finem but a few doevadm commands fail
sudo doveadm mailbox list
returns
doveadm(root): Error: chdir(/root/) failed: Permission denied (euid=1001(vmail)
egid=1001(vmail) missi
If doveadm has no such feature, one could think about writing a shell script
that queries all Maildir (sub)folders and runs the doveadm acl add for each
entry.
But I guess someone else must have had this task before me, so I hoped there is a
"standard approach".
A more portable app
> Please see
> https://doc.dovecot.org/2.3/configuration_manual/acl/#acl-inheritance-and-default-acls
Thank you for your quick response!
I've already read that page multiple times but I'm still not sure what I could
do.
If doveadm has no such feature, one could think about
> On 17/12/2024 13:40 EET r.barclay--- via dovecot wrote:
>
>
> Hello,
>
> I have a shared mailbox (e.g. "i...@example.org") and want to give a new user
> (e.g. "john@example.org") access.
>
> I can use:
> doveadm acl add -u i...@
Hello,
I have a shared mailbox (e.g. "i...@example.org") and want to give a new user
(e.g. "john@example.org") access.
I can use:
doveadm acl add -u i...@example.org INBOX user=john@example.org create
delete expunge insert lookup post read write write-deleted write
ther Dovecot's developers intend for
this to work or not. If they do, I am happy to try to help fix
whatever is happening.
It might be worth noting: sometimes doveadm sync does the right thing.
In particular, I haven't had any trouble when moving emails that
have been around for a whi
>>>>> "falsifian" == falsifian writes:
> "John Stoffel" wrote:
>> >>>>> "James" == James Cook via dovecot writes:
>>
>> > Moving mail files between Maildir mailboxes often confuses doveadm
>> > sync
"John Stoffel" wrote:
> >>>>> "James" == James Cook via dovecot writes:
>
> > Moving mail files between Maildir mailboxes often confuses doveadm
> > sync: I end up with copies in both the original and new maildir.
> > Exact details
>>>>> "James" == James Cook via dovecot writes:
> Moving mail files between Maildir mailboxes often confuses doveadm
> sync: I end up with copies in both the original and new maildir.
> Exact details and script to reproduce follow.
Are you accessing your Maildi
Hi,
Moving mail files between Maildir mailboxes often confuses doveadm
sync: I end up with copies in both the original and new maildir.
Exact details and script to reproduce follow.
I can work around this by running doveadm move, but it does not fit well with
my workflow, which is based on
> On 09/09/2024 18:47 EEST Kevin Kelker via dovecot wrote:
>
>
> Hi,
>
>
> is there any chance to open the doveadm http api to handle more than one
> client at a time if the requests are read-only commands that have
> no risk of breaking something when they run
Hi,
is there any chance to open the doveadm http api to handle more than one client
at a time if the requests are read-only commands that have
no risk of breaking something when they run simultaneously?
We have a scenario of using it only for getQuota to visualize a live-status of
the mailbox
Hi!
Seems like this is a bug, we'll take a look. Thank you for reporting it.
Aki
> On 14/08/2024 19:00 EEST Jasper Spaans via dovecot
> wrote:
>
>
> Hi,
>
> I'm trying to parse the output of `doveadm -f json who`[0] and am running
> into a small issue w
Hi,
I'm trying to parse the output of `doveadm -f json who`[0] and am running into
a small issue when it returns data about multiple users: the stream that is
emitted in that case is not valid json.
dovecot -version tells me dovecot 2.3.21 (47349e2482), more specifically, this
is the ve
On 18/07/2024 14:41, Rachel Roch via dovecot wrote:
When attempting a doveadm backup, e.g. :
doveadm -D backup -Ru user tcp:foo.example.com:12345
Hi Rachel
maybe that should be with tcps
doveadm -D backup -Ru user tcps:foo.example.com:12345
John
When attempting a doveadm backup, e.g. :
doveadm -D backup -Ru user tcp:foo.example.com:12345
I am getting the following error :
Error: SSL handshake failed: SSL_accept() failed: error:0A00010B:SSL
routines::wrong version number
There is nothing wrong with my SSL config because, e.g. openssl
Hi
Did you also run the "doveadm auth test quo" with debugging?
These commands with -D are giving different results to before. I'm not
sure how to explain that.
If you do a new test with and without the debugging parameter, can you
confirming that the debugging parameter
I did. Do not know why all those dlopen() failed, but as i’m told to
ignore those messages, i did ;-)
BTW: home dir is wrong now. I swear i didn’t change anything ...
root@bywater ~ # doveadm -D user qno
Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm
Debug: Skipping
On 12/07/2024 21:47, Christian H. Kuhn via dovecot wrote:
Hi all,
next step with my auth problem with dovecot.
I want to authenticate a system user. The user exists, can log in, can
sudo -i etc.pp. SASL with sql passdb and userdb works fine.
root@bywater /etc/dovecot/conf.d # doveadm user
Hi all,
next step with my auth problem with dovecot.
I want to authenticate a system user. The user exists, can log in, can
sudo -i etc.pp. SASL with sql passdb and userdb works fine.
root@bywater /etc/dovecot/conf.d # doveadm user qno
field value
uid 1001
gid 1001
home/home
https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/
As indicated in the documentation above, in case of configuration with the
director, the doveadm commands must be executed from the director itself.
However, if I try to run the command "doveadm -D mailbox list -u
u...@exampl
synchronization.
I want to synchronize only from server A to server B, but not in the opposite
direction. Is it sufficient on server A to set
service doveadm {
inet_listener {
port = 12345
}
}
doveadm_password = secret
and server B to set
doveadm_port = 12345
server B, but not in the opposite
direction. Is it sufficient on server A to set
service doveadm {
inet_listener {
port = 12345
}
}
doveadm_password = secret
and server B to set
doveadm_port = 12345
doveadm_password = secret
? In other words, when a doveadm client
old backend (Maildir format) to the new
(mdbox format).
For the migration I use the "doveadm backup" command and everything works fine.
The problem I'm having is that I can't kick the user (if logged in).
Once the migration is done (as indicated
https://doc.dovecot.org/3.0/man/do
way to achieve that?
If not, can I just dump all the files together and make dovecot
recreate the indexes?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Will doveadm-import automatically dete
f not, can I just dump all the files together and make dovecot
> > recreate the indexes?
> > _______
> > dovecot mailing list -- dovecot@dovecot.org
> > To unsubscribe send an email to dovecot-le...@dovecot.org
>
> Will doveadm-im
way to achieve that?
If not, can I just dump all the files together and make dovecot
recreate the indexes?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Will doveadm-import automatically dete
x27;t help, still the backup jobs abort in the middle of the transfer,
now with complete different error messages.
On the destination server i started it with the following command ( the
corresponding user folder & files is deleted under /var/spool/vmail and
/var/indexes )
/usr/bin/doveadm -
On 4/27/24 12:31, Aki Tuomi via dovecot wrote:
Yeah. Backup command, without -R backs to location, not from location.
Mailman archive is athttps://www.dovecot.org/mailman3/mailman3/lists/
Aki
___
dovecot mailing list --dovecot@dovecot.org
To unsu
doveadm service on the old server and then
call
"doveadm backup -Ru username tcp:host:port"
on the new server? So the reason that doveadm deleted everything
yesterday was that I forgot the -R option?
"The doveadm backup command forces the destination
On 4/26/24 14:04, Aki Tuomi wrote:
We have migration guide, see
https://doc.dovecot.org/admin_manual/migrating_mailboxes/
Aki
regarding this guide:
I am supposed to set up doveadm service on the old server and then call
"doveadm backup -Ru username tcp:host:port"
on the new serv
This is the magic incantation I use:
#> doveadm -o mail_fsync=never -R -u u...@foo.bar imapc:
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
>
> Sure it's my own fault - no discussion about that, but seriously? How
> dangerously unintuitive it that?
>
I don't really get what is going on with remote host. How is a host name even
relevant other than setting up the initial connection. I don't even see it in
my storage mail files.
_
On 26/04/2024 14:46 EEST Nils via dovecot
wrote:
Sure it's my own fault - no discussion about that, but seriously? How
dangerously unintuitive it that?
I found it when I was searching for a good practice to migrate a mail
server with rsync and I
Sure it's my own fault - no discussion about that, but seriously? How
dangerously unintuitive it that?
I found it when I was searching for a good practice to migrate a mail
server with rsync and I mistakably assumed it works in the same
direction as rsync.
Luckily i have a backup from all ma
Hi,
It would be great if doveadm index could terminate non-zero in the case
of index corruption, that way the tool can be used as a way to determine
and remove corrupted indexes. Example:
othala [13:56:24] ~ # doveadm index -u lumi_james INBOX
doveadm(lumi_james): Error: Corrupted
doveadm -o plugin/quota= ...
Aki
On 17/04/2024 10:25 EEST Ralf Becker via dovecot
wrote:
Noone an idea?
No longer been able to restore mailboxes seems a little scary ...
Ralf
Am 12.04.24 um 14:07 schrieb Ralf Becker via dovecot
dovecot doveadm -Dv import -u p...@xyz.de -s mdbox:$(pwd)/pbs-2024-03-
19/mdbox INBOX mailbox 'projekte/8-BZ/*'
I'm getting the following error:
Apr 12 10:52:18 doveadm(p...@xyz.de): Error: quota: Unknown namespace: INBOX/
I also tried restoring in a (not existing) restore folder: Res
Dovecot version is 2.3.20 and I try to restore a folder hierarchy from an older
snapshot of the mailbox (folders in question have been deleted):
sudo -u dovecot doveadm -Dv import -u p...@xyz.de -s mdbox:$(pwd)/pbs-2024-03-
19/mdbox INBOX mailbox 'projekte/8-BZ/*'
I'm getting the
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.
On 31/03/2024 13:33 EEST Marc wrote:
Subject: Re: [Dovecot] [dovecot-2.1.15] mdbox corruption,
doveadm force-
resync can't repair it (throws segfault)
Are you sure it is not something else, your message is even
> Subject: Re: [Dovecot] [dovecot-2.1.15] mdbox corruption, doveadm force-
> resync can't repair it (throws segfault)
>
Are you sure it is not something else, your message is even empty.
___
dovecot mailing list -- dovecot@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
> On 19/02/2024 22:17 EET Ryan Ford wrote:
>
>
> Hello,
> Would you be able to show what you did in order to make this command
> unsubscribe as well? The link provided with the answer, no longer works.
>
> Thank you, Ryan
>
doveadm ma
Hello,
Would you be able to show what you did in order to make this command
unsubscribe as well? The link provided with the answer, no longer works.
Thank you, Ryan
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot
...@domain-2.it)
The usedb lookup works perfectly, and dovecot correctly creates the mailboxes
in the form /home/domain/name.surname/arbitr...@domain-1.it/Maildir and
/home/domain/name.surname/arbitr...@domain-2.it/Maildir
The doveadm auth login arbitr...@domain-1.it command perfectly works, allowing
.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 2/10/2024 7:24 AM, Kirill A. Korinsky wrote:
Greeetings,
I do have a cron script which runs doveadm NOT mailbox Junk SEEN SINCE 30d
Everything
Greeetings,
I do have a cron script which runs doveadm NOT mailbox Junk SEEN SINCE 30d
Everything works well with one exception, if user removes email when it's
running, it may lead to an email from cron like:
doveadm(...): Error: fetch(hdr) failed for box=virtual.All uid=145266:
Me
because of 'over quota'.
Here is an example:
# doveadm quota get -u i...@domain.abc
Quota name Type Value Limit %
User quota STORAGE 16798 16777216 0
User quota MESSAGE 628 - 0
Domain quota STORAGE 32282 67108864 0
Domain quota MESSAGE 645 - 0
[root@vmi792826 ~]# doveadm b
Hello,
After adding `mechanisms = plain login` to passdb (passwd-file),
`doveadm -D sync -u e...@example.com -d -N -l 30 -U` failed with
```
Jan 26 06:49:22 doveadm(e...@example.com): Error:
remote(server2.example.com:61526): doveadm(1.1.1.1,e...@example.com):
auth-master: passdb lookup(e
Hi Timo,
thanks for your quick answer.
On 23.01.2024 00:18, Timo Sirainen wrote:
>> When doveadm server receives at lot of connects on port 5 the http
>> service on
>> port 50001 is not responding until load on port 5 drops to zero.
>> It seems like doveadm-
Hi,
> On 22. Jan 2024, at 20.00, Achim Stahlberger
> wrote:
>
> Hello,
>
> we see this problem when doveadm-server is under load.
>
> We enabled doveadm http api with this config:
>
> service doveadm {
> inet_listener {
>port = 5
> }
&g
Hello,
we see this problem when doveadm-server is under load.
We enabled doveadm http api with this config:
service doveadm {
inet_listener {
port = 5
}
inet_listener http {
port = 50001
ssl = no
}
}
When doveadm server receives at lot of connects on port 5 the http
g of the destination folder. The folder is then
> freshly created via doveadm, but is unfinished because the backup jobs aborts
> on the > messages mentioned above. If i don't delete the destination folder,
> the backup job gives me a clearer error message:
>> doveadm(user3)<
hink I'm on the right track here, since I removed the following
>> from /etc/dovecot/conf.d/auth-sql.conf.ext
>>
>> #userdb {
>> # driver = static
>> # args = uid=mail gid=mail home=/var/mail/%d/%n
>> #}
>>
>> So now my error is as follo
1 - 100 of 1076 matches
Mail list logo
