Re: dovecot replicator not replicating automatically?

Hi. I need to learn how to debug properly. I forgot to uncomment some of the user params in the sync that i had commented earlier before the replication plugin was loaded. All is working now. Thanks all for the help. regards Norman King Compass Foundation sysadmin/tech support Phone,

Re: dovecot replicator not replicating automatically?

Hi! In order for replication to trigger, you need - load the replication plugin - use dovecot-lda / lmtp to deliver mail If you have done these both, please provide doveconf -n and output of mail_debug=yes logs. Aki > On 29/10/2020 19:10 Norman King wrote: > > > Thanks for that tip. > I

Re: dovecot replicator not replicating automatically?

Thanks for that tip. I loaded the replication plugin but still have the same issue. Anything else i can check? regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 supp...@compassfoundation.io Website

Re: dovecot replicator not replicating automatically?

> On 29. Oct 2020, at 17.24, Norman King wrote: > > Hello all. > > I'm trying to set up the dovecot replicator plugin to automatically replicate > mail between 2 servers. > > The servers are both using iredmail with dovecot as the imap server. > > I have everything working if i run dovecot

dovecot replicator not replicating automatically?

Hello all. I'm trying to set up the dovecot replicator plugin to automatically replicate mail between 2 servers. The servers are both using iredmail with dovecot as the imap server. I have everything working if i run dovecot replicator replicate \* all accounts update. But if an account

Re: Support of INDEXPVT in Dovecot 2.3 with replication

Thanks Aki :) Am 29.10.20 um 13:47 schrieb Aki Tuomi: > At the moment the correct way to use shared folders in a replication pair is > to access them with imapc from the other pair. Can you please elaborate a bit more? In 2.2 I could understand how that works, as INDEXPVT was not replicated,

Re: Support of INDEXPVT in Dovecot 2.3 with replication

At the moment the correct way to use shared folders in a replication pair is to access them with imapc from the other pair. Aki > On 29/10/2020 14:43 Ralf Becker wrote: > > > In reference to an earlier mail from me, I'd like to ask: > > Have there been any changes in regard to INDEXPVT and

Support of INDEXPVT in Dovecot 2.3 with replication

In reference to an earlier mail from me, I'd like to ask: Have there been any changes in regard to INDEXPVT and replication or are there any plans in that direction? Thanks :) Ralf On 03.08.20 at 11:20 Ralf Becker wrote: > So far the only thing we noticed: private seen flags on shared user >

Re: dovecot quota-warning detection mail

Let me just add, of course you should play around with some test entries. You don't want problems with dovecot finding the home directory, users suddenly seeing an empty mailbox, or LMTP delivering to the wrong place. Just in case this isn't obvious :-) On 10/29/20 2:08 PM, Gedalya wrote: > Very

Re: dovecot quota-warning detection mail

Very good. See https://doc.dovecot.org/configuration_manual/authentication/passwd_file/ You can add the "user" field as an "extra field" In users.auth, just add in the end "user=-...@ddd.example.com" to match the respective entry in /etc/dovecot/users Good luck! On 10/29/20 2:02 PM, 森川

Re: dovecot quota-warning detection mail

Perhaps if you share some information about your passdb / userdb authentication setup, I or others might be able to help further. On 10/29/20 12:51 PM, 森川 孝司 wrote: > Gedalya-san > > Thank you for the information. > > It seems to be difficult... > > morikawa > -Original Message- > From:

Re: dovecot quota-warning detection mail

Aha. Then it's not a straightforward case of just adding the domain name to the same username, you need to transform the username too. Dovecot's userdb / authdb allows you to return a "user" field, which sets a new username for dovecot to use. Depending on what you use as your authentication

Re: dovecot quota-warning detection mail

It should only affect users who authenticate with a username only, without a domain. The only effect is to add the domain name to the username. You could perhaps test, by logging in as just "user" and then as "u...@example.co.jp" and make sure everything behaves the same. If everything behaves

RE: dovecot quota-warning detection mail

OK. "passdb/userdb" Setting part $ dovecot -n (Excerpt from change) - passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users.auth driver = passwd-file } userdb { args =