similar to: Question about noreplicate flag

Displaying 20 results from an estimated 700 matches similar to: "Question about noreplicate flag"

2020 Feb 17
2
Question about noreplicate flag
On Mon, 17 Feb 2020, Aki Tuomi wrote: > On 17.2.2020 12.48, Bernardo Reino wrote: >> Dear all, >> >> I've just setup replication between two servers. The e-mail accounts >> on both servers intersect but are not the same. >> >> In dovecot.conf (both are identical except one user /var/mail and the >> other uses /srv/vmail) I have: >> >>
2020 Feb 17
2
Question about noreplicate flag
On 17.2.2020 13.09, Bernardo Reino wrote: > On Mon, 17 Feb 2020, Bernardo Reino wrote: > >> On Mon, 17 Feb 2020, Aki Tuomi wrote: >> >>> On 17.2.2020 12.48, Bernardo Reino wrote: >>>> Dear all, >>>> >>>> I've just setup replication between two servers. The e-mail accounts >>>> on both servers intersect but are not the
2020 Feb 17
0
Question about noreplicate flag
On 17.2.2020 12.48, Bernardo Reino wrote: > Dear all, > > I've just setup replication between two servers. The e-mail accounts > on both servers intersect but are not the same. > > In dovecot.conf (both are identical except one user /var/mail and the > other uses /srv/vmail) I have: > > --<<-- > userdb { > ? driver = passwd-file > ? args =
2020 Feb 17
0
Question about noreplicate flag
On Mon, 17 Feb 2020, Bernardo Reino wrote: > On Mon, 17 Feb 2020, Aki Tuomi wrote: > >> On 17.2.2020 12.48, Bernardo Reino wrote: >>> Dear all, >>> >>> I've just setup replication between two servers. The e-mail accounts >>> on both servers intersect but are not the same. >>> >>> In dovecot.conf (both are identical except one
2020 Jun 05
3
Doveadm Backup issues
On Fri, 5 Jun 2020, Francis Augusto Medeiros-Logeay wrote: > Another related question: if backing up on another location on the same > computer, using -A doesn't seem to recreate the structure of the original > Maildir (for example, /var/mail/%d%n). > > Is there a way to do that? If I understand your question correctly (I may be missing context), you can use dsync for that,
2020 Feb 06
2
noreplicate for some users
Hi, I have set up the sync and it is working but I only would like to sync some users. Currently this does not seem to work. Version 2.3.9.2 Relevant Settings: File users: mail at domain.de:{SHA}hash:::t: passdb { driver = passwd-file args = username_format=%u /etc/dovecot/users } userdb { driver = passwd-file args = username_format=%u /etc/dovecot/users default_fields =
2020 Feb 17
0
Question about noreplicate flag
On Mon, 17 Feb 2020, Aki Tuomi wrote: > I wonder if we are doing the noreplicate too late. Can you try adding > one of the non-overlapping users to the other site with noreplicate=y > and see if helps? Well that did it indeed! :) I created the reinob at bbmk.org at the other server (just the line in the passwd file, without creating any directory or anything) and the logs went silent
2018 Mar 12
2
quota-status: Issues with uppercase recipient address
* B. Reino <reinob at bbmk.org> [2018-03-10 23:10:30 +0100]: >On Sat, 10 Mar 2018, Christoph Lukas wrote: > >>Am 10.03.2018 um 12:20 schrieb Aki Tuomi: >>>Change mail_location too >>> >>That did it! >>Thank you very much! >> > >You may also want to correct the sieve directory (it uses %d and %n). > Cheers, changed that as well. Thank
2020 Feb 06
0
noreplicate for some users
I believe the userdb_ prefix is used when you want to provide userdb fields in a passdb context, or in the actual passwd-file file contents (/etc/dovecot/users). In default_fields, you should use the non-prefixed name, i.e. "noreplicate=y" Use `doveadm user -u <username>` to see what userdb fields are returned for a specific user. - Eirik On 2/6/2020 11:36 PM, mail at
2018 Oct 20
2
Bug: 'noreplicate' database extra field ingnored
The 'noreplicate' user database field described in the wiki appears to make no difference as to whether an account gets replicated or not. My sql user query returns a 'noreplicate' field and I can confirm that this is getting set using 'doveadm user', however when I add a new account with noreplicate=true it gets replicated regardless. User query: user_query = SELECT
2018 Apr 04
2
issue with sieve forwarding after upgrade to 0.5.1
Thank you for your reply. I use FreeBSD so no changes on the OS before and after the dovecot/pigeonhole updates. > On 4 Apr 2018, at 08:54, B. Reino <reinob at bbmk.org> wrote: > > Hello, > > The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. > > (if you need help with that ask again..
2020 Jun 07
0
Doveadm Backup issues
On 05 Jun 2020, at 17:09, Bernardo Reino <reinob at bbmk.org> wrote: > USERS=$(cat /etc/dovecot/virtual_passwd | cut -d: -f1) Is that a standard file? It's not one I have. I would use (not that I have, but it seem like the way to get a list of users) USERS=$( doveadm user '*' ) -- You start a conversation you can't even finish it You're talkin' a lot, but
2018 Jul 15
3
Letsencrypt certificate for repo.dovecot.org expired May 14th..
Dear Aki, I think the renewal failed again. The SSL certificate expired Saturday, 14 July 2018. This affects (at least) the repo.dovecot.org website and debian repository. Thanks, Bernardo. On 2018-05-15 08:15, Aki Tuomi wrote: > On 15.05.2018 09:14, B. Reino wrote: >> Dear all, >> >> Just in case you've missed it, the certificate for repo.dovecot.org >> just
2019 Jun 22
2
Dovecot replication and userdb "noreplicate".
Hello! I finally took the time and spent two days to set up replication for my server and now I have a question or two. I initially set noreplicate userdb field to 1 for all but a test user, but I could still see in the logs that all mailboxes were trying to connect to the other server via SSH. Is that normal? Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error: Remote
2018 Sep 03
3
online conversion using replication?
On Mon, 3 Sep 2018, Sami Ketola wrote: >> On 3 Sep 2018, at 4.18, Daniel Miller <dmiller at amfes.com> wrote: >> >> That works for a one-time migration, or perhaps via a cron-job, but what I want is basically a constant one-way backup and it seems replication could do it more elegantly & efficiently. >> > > So you want real-time archiving? What we have done
2018 Oct 22
0
Bug: 'noreplicate' database extra field ingnored
On 20.10.2018 7.29, Phil wrote: > The 'noreplicate' user database field described in the wiki appears to > make no difference as to whether an account gets replicated or not. > My sql user query returns a 'noreplicate' field and I can confirm that > this is getting set using 'doveadm user', however when I add a new > account with noreplicate=true it gets
2020 Sep 21
3
At a loss with antispan and imap_sieve
On Mon, 21 Sep 2020, Ferenc wrote: > Thanks for your quick reply! I tried /tmp/debug.log, world-writeable, > but no dice. > >> https://doc.dovecot.org/configuration_manual/howto/antispam_with_sieve > > I followed the setup here. I think it works up until the external script > is called (pipe :copy "sa-learn-ham.sh"). That's why I tried echo hi >>
2020 Jul 17
2
Stuck here - help please
Hi Gerald, Thank you for the details. As per your suggestion, I have made the changes to dovecot.conf file. Still I don't see any replication is happening. Please see the dovecot.conf file. I do not see "/etc/dovecot/conf.d/12-replication.conf" in my servers. So I had put everything in the dovecot.conf file only. Please see the complete data in it below. The below data is in
2018 Oct 17
0
Replication 'noreplicate' field usage
I've set up replication as per the wiki under 2.3.3 and in my SQL user query I am returning a 'noreplicate' field, this is a boolean and returns true for all users at the moment. However when I do "doveadm replicator status '*'" it lists all users in my database suggesting it is trying to sync all users regardless of the noreplicate field. ``` user_query = SELECT
2019 Jun 24
0
Dovecot replication and userdb "noreplicate".
On 22.6.2019 22.00, Reio Remma via dovecot wrote: > Hello! > > I finally took the time and spent two days to set up replication for > my server and now I have a question or two. > > I initially set noreplicate userdb field to 1 for all but a test user, > but I could still see in the logs that all mailboxes were trying to > connect to the other server via SSH. Is that