search for: foxxx0

* Thore B?decker <me at foxxx0.de>: > You might need to quote that last argument, otherwise it can get > interpreted by the shell as globbing, which obviously is not what you > want. > > I've been using wildcard arguments enclosed within '' and "" for > various doveadm commands without...

Please provide doveconf -n ---Aki TuomiDovecot oy -------- Original message --------From: Patrick Ben Koetter <p at sys4.de> Date: 25/06/2018 17:21 (GMT+02:00) To: dovecot at dovecot.org Cc: Thore B?decker <me at foxxx0.de> Subject: Re: doveadm: problem listing shared mailboxes using a wildcard * Thore B?decker <me at foxxx0.de>: > You might need to quote that last argument, otherwise it can get > interpreted by the shell as globbing, which obviously is not what you > want. > > I've b...

...ase, which is replicated from the master to a slave node. For the mails I rely on the dovecot builtin replication which has been working great for me thus far. However I noticed something was off when looking through my journal yesterday: dovecot[823]: doveadm: Error: Couldn't lock /var/vmail/foxxx0.de/qwer/.dovecot-sync.lock: safe_mkstemp(/var/vmail/foxxx0.de/qwer/.dovecot-sync.lock) failed: No such file or directory In this case the domain directory /var/vmail/foxxx0.de was already existing on the slave, but dovecot didn't bother to create the user folder before trying to lock it. The...

...as? > > When you made your initial database tables how did you set up the > password field and in MySQL how did you make it? > > I'm trying to figure out what is different about your setup than mine. > > Thanks. > Dave. > > > On 3/10/18, Thore B?decker <me at foxxx0.de> wrote: >> Hey, >> >> using the roundcube password plugin allows you to specify arbitrary >> statements for password_query. >> >> I'm using SHA512-CRYPT too and this is my $config['password_query']: >> >> "UPDATE vhostapi_prod.m...

Hello, I've got dovecot authenticating to a MySQL database. I've got a field varchar(128) called password. Whenever I create a password I use doveadm pw as in: doveadm pw -s sha512-crypt now i'd like to get MySQL to make a dovecot-specific password. My goal is to eventually have roundcube's password plugin working with this MySQL database to change the password. Thanks. Dave.

I'm setting up a dovecot server with private and shared namespaces. My test setup has these mailboxes: # /bin/doveadm mailbox list -u fdl01 at spike.test INBOX/sub01 shared shared/sammel01 at spike.test shared/sammel02 at spike.test INBOX In order to do some post-login scripting foo I'd like to get a list of shared mailboxes the user is currently subscribed to. The doveadm-mailbox man

Aaaaand I forgot to CC the list, sorry for that, it's way too early in the morning :P On 07.06.18 - 07:39, Thore B?decker wrote: > What does the output of these two commands show after that error has > been logged? > > doveadm replicator status > > doveadm replicator dsync-status > > If there are *waiting failed* requests, that never make it "through" >

You might need to quote that last argument, otherwise it can get interpreted by the shell as globbing, which obviously is not what you want. I've been using wildcard arguments enclosed within '' and "" for various doveadm commands without issues so far. On 25.06.18 - 16:03, Patrick Ben Koetter wrote: > # /bin/doveadm mailbox list -u fdl01 at spike.test -s shared*

Hey, you mentioned that dovecot builds fine, but does "make check" also complete successfully with a glibc-2.28 build on a glibc-2.28 system? We have been seeing segfaults during "make check" and it seems the following patch was able to make the testsuite run successfully. Just out of curiosity, could you try this patch and see if this fixes the issues you're

Hi Piotr, On 18.08.20 16:40, Piotr Auksztulewicz wrote: > ----- doveconf -n ------- > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-8-amd64 x86_64 Debian 10.4 It looks like your dovecot version is a bit outdated. There were numerous fixes in the 2.3 series regarding replication, especially with respect to sieve replication. I

Hey all, almost 48h ago I upgraded both my instances to 2.3.1 again to see if the new patches would fix the replication issues for me. So far, the result is: great. I haven't been able to provoke any kind of I/O stall or persisting queued/failed resync requests in my replication setup. Newly added users are replicated instantly upon the first received mails and the home directory gets

Hey all, I've been affected by these replication issues too and finally downgraded back to 2.2.35 since some newly created virtual domains/mailboxes weren't replicated *at all* due to the bug(s). My setup is more like a master-slave, where I only have a rather small virtual machine as the slave host, which is also only MX 20. The idea was to replicate all mails through dovecot and