Displaying 20 results from an estimated 200 matches similar to: "Bug: 'noreplicate' database extra field ingnored"
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 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
2
Question about noreplicate flag
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 = username_format=%Lu /etc/dovecot/virtual_passwd
default_fields = uid=vmail gid=vmail
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:
>>
>>
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 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
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 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 =
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
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
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 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
2019 Jun 24
2
Dovecot replication and userdb "noreplicate".
On 24.06.2019 8:21, Aki Tuomi wrote:
> 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
2019 Aug 07
0
Dovecot replication and userdb "noreplicate".
> On 6 Aug 2019, at 23.52, Reio Remma via dovecot <dovecot at dovecot.org> wrote:
>
> service doveadm {
> user = vmail
> }
>
> This seems to have fixed it. Here's hoping for no unforeseen side-effects. :)
>
> I still need allow dovecot_t ssh_exec_t:file { execute execute_no_trans open read }; for selinux, but there are no more errors in maillog and it
2019 Aug 06
0
Dovecot replication and userdb "noreplicate".
On 24.06.2019 16:25, Reio Remma wrote:
> On 24.06.2019 8:21, Aki Tuomi wrote:
>> On 22.6.2019 22.00, Reio Remma via dovecot wrote:
>>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error:
>>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l
>>> vmail backup.host.ee doveadm dsync-server -D -uuser at host.ee
>>>
2019 Aug 06
2
Dovecot replication and userdb "noreplicate".
On 06.08.2019 23:17, Reio Remma via dovecot wrote:
> On 24.06.2019 16:25, Reio Remma wrote:
>> On 24.06.2019 8:21, Aki Tuomi wrote:
>>> On 22.6.2019 22.00, Reio Remma via dovecot wrote:
>>>> Jun 22 16:55:22 host dovecot: dsync-local(user at host.ee)<>: Error:
>>>> Remote command returned error 84: ssh -i /home/vmail/.ssh/vmail.pem -l
>>>>
2018 Mar 10
3
dovecot sha512-crypt database storage
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.
2020 Jul 16
2
Stuck here - help please
Thank you for the reply.
I have done the sync manually with "doveadm sync" command. But, I have not
configured the replication yet.
I am looking at the below webpage for the replication.
https://wiki.dovecot.org/Replication
I am using the dovecot version "2.2.36". I am confused with what needs to
be done after reading that page.
1. They are talking about v2.3.1 and v2.2+.
2020 Jul 16
0
Stuck here - help please
> I have done the sync manually with "doveadm sync" command. But, I have not configured the replication yet.
If you don't tell dovecot where to replicate, nothing gets replicated.
> I am looking at the below webpage for the replication.
>
> https://wiki.dovecot.org/Replication <https://wiki.dovecot.org/Replication>
>
> I am using the dovecot version
2018 Jun 07
4
2.3.1 Replication is throwing scary errors
Still not quite right for me.
Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error:
dsync(lightning.reub.net): I/O has stalled, no activity for 600 seconds
(last sent=mail, last recv=mail (EOL))
Jun 7 15:11:33 thunderstorm.reub.net dovecot: doveadm: Error: Timeout
during state=sync_mails (send=mails recv=recv_last_common)
I'm not sure if there is an underlying replication error