Re: Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]

2015-05-15 Thread Reuben Farrelly
On 8/05/2015 11:04 PM, Reuben Farrelly wrote: On 8/05/2015 6:10 PM, Teemu Huovila wrote: On 05/07/2015 02:32 PM, Reuben Farrelly wrote: On 7/05/2015 7:49 AM, Timo Sirainen wrote: On 06 May 2015, at 13:52, Reuben Farrelly wrote: On 4/05/2015 11:06 PM, Teemu Huovila wrote: Also is there a wa

Re: Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]

2015-05-08 Thread Reuben Farrelly
On 8/05/2015 6:10 PM, Teemu Huovila wrote: On 05/07/2015 02:32 PM, Reuben Farrelly wrote: On 7/05/2015 7:49 AM, Timo Sirainen wrote: On 06 May 2015, at 13:52, Reuben Farrelly wrote: On 4/05/2015 11:06 PM, Teemu Huovila wrote: Also is there a way to restrict replication users aside from a cr

Re: Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]

2015-05-08 Thread Teemu Huovila
On 05/07/2015 02:32 PM, Reuben Farrelly wrote: > On 7/05/2015 7:49 AM, Timo Sirainen wrote: >> On 06 May 2015, at 13:52, Reuben Farrelly wrote: >>> >>> On 4/05/2015 11:06 PM, Teemu Huovila wrote: > Also is there a way to restrict replication users aside from a crude hack > around system f

Additional userdb variables in passwd [was Re: Dovecot Replication - Architecture Endianness?]

2015-05-07 Thread Reuben Farrelly
On 7/05/2015 7:49 AM, Timo Sirainen wrote: On 06 May 2015, at 13:52, Reuben Farrelly wrote: On 4/05/2015 11:06 PM, Teemu Huovila wrote: Also is there a way to restrict replication users aside from a crude hack around system first and last UIDs? You can set the userdb to return an empty mail