search for: user11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 24 Feb 2014, Charles Marcus wrote: > On 2/24/2014 10:13 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: >> >> What changes are made by default, that are not implemented by the MTA >> admin? > > Sorry, I don't understand the question (language thing I'm sure). Doesn't matter with

...ate mask = 0775 directory mask = 02775 force directory mode = 0775 path = /mnt/samba/ read only = No veto oplock files = /*.DAT/*.dat/ situation: More than 10 users have files open in there, doing their work mostly inside the subfolder \\server\daten\Daten (yes, ugly path ... anyway) "user11" incidentally clicks "rename" on that folder "Daten", deletes the whole name in the process, doesn't *remember* that it was "Daten" and types "Klienten" (german for "clients", doesn't matter here, just to be precise), hits OK or Save...

Am 28.08.18 um 19:00 schrieb Rowland Penny via samba: > I have never tried it, but you could probably do it, if you use Windows > ACL's, where there is 'delete subfolders & files' and you can deny this. > You would probably have to ignore the Unix attrs with 'acl_xattr:ignore > system acls = yes' We will test that with a separate testing share asap. Thanks.

...doveadm(user09 at domain1.example.org): Debug: auth input: user=user09 at domain1.example.org proxy host=10.129.3.190 proxy_refresh=86400 10 / 94doveadm(user10 at domain1.example.org): Debug: auth input: user=user10 at domain1.example.org proxy host=10.129.3.190 proxy_refresh=86400 doveadm(user11 at domain1.example.org): Debug: auth input: user=user11 at domain1.example.org proxy host=10.129.3.191 proxy_refresh=86400 doveadm(user12 at domain1.example.org): Debug: auth input: user=user12 at domain1.example.org proxy host=10.129.3.193 proxy_refresh=86400 doveadm(user13 at domain1.exam...

I had our production systems running on rc23, however we ran into problems when the server was under heavy load. Eventually, the server would begin to freeze all imap connection after authentication (according to the logs). A user would connect, authentication would succeed, and then the connection would sit until timing out. No error logs were produced. Upgrading to rc24 did not

...ing3] path = /string3 read only = Yes write list = user3,user4,user5 create mask = 0760 force create mode = 0760 [home] path = /path/home read only = No [string4] path = /path read only = Yes write list = user9,user10,user11 [string5] revalidate = yes browseable = no writeable = yes valid users = @string5, at string6, at string7 path = /path/path [string11] path = /path/path2/path3 writeable = yes valid users = @string9,string9 browseable = no...

I recently upgradeded dovecot on one of our servers from version 1.0.10 to version 1.1.3. Ever since, we've been seeing occasional errors similar to this sequence (with the username and IP addresses elided): Sep 30 00:09:56 alcor dovecot: pop3-login: Login: [4954], XXXX, NNN.NNN.NN.NNN Sep 30 00:09:56 alcor dovecot: wrapper[5006]: pop3, XXXX, NNN.NNN.NN.NNN Sep 30 00:09:56 alcor

...have Groups of servers, for example: CUSTOMERservers (serverA, serverB, ...,serverK) ADMINISTRATIVEservers (serverL,server, serverM, ...,serverP) DATABASEservers (serverQ, serverR,, ..., serverZ) We have groups of users: ITusers (user1, user2, ... user11) CUSTOMERSUPPORTusers (user12,user13, ..., user14) DBAuser (user15,user16) We would to be able to say: on servergroup {CUSTOMERservers} ensure usergroup {ITusers, CUSTOMERSUPPORTusers} are present. on servergroup {DATABASEservers} ensure usergroup {DBAuse...