similar to: logins fail for virtual users (permission denied, we're not in group 5000)

Displaying 20 results from an estimated 1000 matches similar to: "logins fail for virtual users (permission denied, we're not in group 5000)"

2017 Sep 15
0
logins fail for virtual users (permission denied, we're not in group 5000)
On 15.09.2017 06:21, Paul Schreiber wrote: > I have: > - Ubuntu 17.04 > - Dovecot 2.2.27 (c0f36b0) > - Postfix 3.1.4 > > - regular unix users with mail in /home/bob/Maildir > - virtual users with mail in /var/mail/vhosts/domain.com/bob/ > > The regular users can receive mail as expected. > When virtual users try to log in, it fails. The log shows an error like >
2017 Sep 15
2
logins fail for virtual users (permission denied, we're not in group 5000)
On Fri, Sep 15, 2017 at 2:16 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > check > > doveadm user travler at travler.net # doveadm user travler at travler.net field value userdb lookup: user travler at travler.net doesn't exist > you might be specifying uid/gid in passwd virtual passwd file. Pasword file has lines like this: travler::5000:5000::/var/mail/vhosts/
2019 Oct 01
2
Lost mails with sieve "duplicate" extension in case of failure
Hi! we just experienced the following issue: We have a global sieve_before script using the duplicate extension. require ["duplicate", "imap4flags"]; if duplicate { discard; } Now the storage of our mailbox store got full and lmtp deliveries started to fail. This resulted in logs like this: Sep 25 16:14:56 mail-rc1 dovecot: lmtp(USERNAME): Error:
2017 Mar 05
5
Transitioning away from mail_location = maildir:~
Hi, I have been using this setup for years: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~ I have since learned that mail_home and mail_location should be different. I plan to use this: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~/mail I would like the transition to be transparent for my email clients. I don't want mail/directories/sieve_scripts to
2018 Jan 01
2
sieve - Failed to store into mailbox 'INBOX/${1}': Mailbox doesn't exist: INBOX/${1}
Hello, First of all, happy new year! I?ve recently configured my mail server and was using a simple sieve rule in order to store all my ?user+pattern at example.com? ingoing email to be stored in the INBOX/pattern folder. This setup worked very well. I restarted my server this morning (don?t know if it?s related?) and since Dovecot keep storing my emails in INBOX with following errors: root at
2016 Feb 05
0
Share samba on CentOS 6.5
Dear Sir/Madam, Please allow me ask some things about share samba on CentOS 6.5 My case: data (excel file, linked file) of shared folder need security and not allow deleting except for owner and owning group, My testing configuration: + NTFS permision: chmod 3775 on shared folder, # chmod 3777 fa # ll total 8 drwxrwsrwt 2 fa1 fa 4096 Feb 2 12:41 fa + Samba permission:
2016 Mar 24
0
Share samba on CentOS 6.5
Dear Sir/Madam, Please allow me ask some things about share samba on CentOS 6.5 My case: data (excel file, linked file) of shared folder need security and not allow deleting except for owner and owning group, My testing configuration: + NTFS permision: chmod 3775 on shared folder, # chmod 3777 fa # ll total 8 drwxrwsrwt 2 fa1 fa 4096 Feb 2 12:41 fa + Samba permission:
2017 Mar 01
1
Expunged message reappeared, giving a new UID
Dovecot 2.2.27 dsync-server(account_name): Warning: Maildir /usr/local/vhosts/mail/*******/info/Sent: Expunged message reappeared, giving a new UID (old uid=29787, file=*******) What triggers this replication for ever ?? Thank you George
2009 Nov 13
1
Ownership and permissions for the index directory/filesystem
I recently upgraded from DC 1.1.15 to 1.2.6. The /var/dcindx index root directory is: drwxrwsrwt 3962 root sys 192512 Nov 13 11:56 ./ thus 3777. It appears that the user index directories created under DC1.1 look like this (here for /var/dcindx/cep): drwx--S--- 5 cep sys 256 Nov 13 14:26 cep/ while those created under V1.2 look like: drwx------ 3
2017 May 02
2
migrate Maildir to mdbox
Hi, I replaced HDDs in my home server and reinstalled the OS (Ubuntu 17.04). Since I had some time I reviewed my Dovecot configuration and changed a couple of things, including mailbox format. Now I would like to migrate e-mail (about 20G -- I use this server as an e-mail archive). The Maildir is available on the (old) hard disk. The new dovecot is running. What should I use? Would mbsync work?
2017 Sep 16
0
logins fail for virtual users (permission denied, we're not in group 5000)
Followup: Received help on serverfault.com. Fix was to edit 10-master.conf. In the service auth { ? } section, setting either: extra_groups = vmail or group = vmail ?allows things to work. Is there a better way to fix/configure this? thanks. Paul
2017 May 02
2
migrate Maildir to mdbox
Silly question? Which is preferred? MailDir or Mbox? (directory vs flat file) How would you do this when migrating from an old server to a new one? Thx -Mike > On May 2, 2017, at 1:58 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > Assuming your maildir path is /path/to/mail/Maildir You could do it like this: > > mail_home=/path/to/mail >
2017 Feb 06
0
Dsync migration with shared folders
Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both
2017 Feb 06
0
Dsync migration with shared folders
Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both
2017 Feb 06
0
Dsync migration with shared folders
Hi everyone, We discovered that the migration path from a VPS to our 2XHP replication server environment with shared folders should be: 1) Rsync all domains from the VPS to serverA. Then rsync all domains from ServerA to ServerB. ServerA & ServerB are in a identical state. 2) Create an empty directory for the shared indexes 3) Start dovecot on both machines. If we did not sync both machines
2019 Oct 01
0
Lost mails with sieve "duplicate" extension in case of failure
On 01/10/2019 19:03, Hanno Stock via dovecot wrote: > Hi! > > we just experienced the following issue: > > We have a global sieve_before script using the duplicate extension. > > require ["duplicate", "imap4flags"]; > if duplicate { > discard; > } > > Now the storage of our mailbox store got full and lmtp deliveries > started to fail.
2007 Aug 05
1
rsync always gets index.html
I use to sync several servers with rsync for years now. One strange thing I still havent figured out: while rsync does its job perfectly will, it cant refuse to transfer all files with "index.html" in it, even if the files havent change. example: the following files are the same for years, but every night rsync copies them again:
2012 Dec 19
1
setting mail_home and vacation
Hello! dovecot version 2.1.7 I set up vacation with sieve. We have mboxes and maildirs and in dovecot.conf mail_location = mbox:/var/spool/vhosts/%d/dovecotprivate/%n:INBOX=/var/spool/vhosts/%d/%n Error: User archiv at xyz.de doesn't have home dir set, disabling duplicate database Dec 19 20:37:03 lda(archiv at xyz.de): Error: sieve: sieve script file path ~/.dovecot.sieve is relative to
2017 Mar 01
3
Dovecot + SpamAssassin through dovecot-antispam
Hello, I am new to the list. /Waving at everyone/ I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd user), running as a Postfix transport. I am currently trying to switch it to a dovecot plugin in order to make it interactively work with the email storage (react to mail classification, being able to train it from already received emails, aso.) My problem is now making it
2017 Apr 04
2
Host ... is being updated before previous update had finished
We just had a bunch of backend boxes go down due to a DDoS in our director cluster. When the DDoS died down, our director ring was a mess. Each box had thousands (and hundreds per second, which is a bit much) of log lines like the following: Apr 03 19:59:29 director: Warning: director(10.1.20.10:9090/left): Host 10.1.17.15 is being updated before previous update had finished (up -> down) -