search for: newusers

I think I'm progressing: if I create a brand new user, send her an email, it will not be indexed right away. I need to doveadm rescan / index the Inbox before. At the end of this email, a dovecot's debug log snipset (grep'ed on this user). In it I can read: "Debug: fts: Indexes disabled for namespace '' Can this be a problem ? Thanks doveconf -n output: # 2.2.34

That message is coming from the temporary raw user, not from the actual user. How did you verify that the FTS indexes are not created or updated automatically? Aki On 04.05.2018 12:47, kadafax at gmail.com wrote: > ?Bump. Can someone from dovecot dev team please respond something to my > problem ? I've provided all the possible information, and if not please > tell me. > Or do

?Bump. Can someone from dovecot dev team please respond something to my problem ? I've provided all the possible information, and if not please tell me. Or do you only provide support for your own FTS solution bundled with the paid version of dovecot-pro ? If so, you should clearly state it in the wiki. Thanks Le 19/04/2018 ? 10:30, kadafax at gmail.com a ?crit?: > I think I'm

Le 21/05/2018 ? 11:46, Aki Tuomi a ?crit?: > That message is coming from the temporary raw user, not from the actual > user. > > How did you verify that the FTS indexes are not created or updated > automatically? I send an email containing a specific strings ('thahB8ea' in that case) and search agains it: # doveadm search -u username mailbox INBOX body thahB8ea --> No

dovecot 2.2.34 solr 7.2 I only see new messages after typing on the server "doveadm fts rescan -u username" though I've followed the wiki and added "fts_autoindex = yes" in 90-plugin.conf . Subsequent search for the same pattern always gives the same result, ignoring new emails with that particular pattern. Solr is working correctly and the correct search results comes

can you try turning on pluign { fts_enforced = yes } and repeat your test? Aki On 21.05.2018 13:31, kadafax at gmail.com wrote: > Le 21/05/2018 ? 11:46, Aki Tuomi a ?crit?: >> That message is coming from the temporary raw user, not from the actual >> user. >> >> How did you verify that the FTS indexes are not created or updated >> automatically? > I send an

Help! I have been using dovecot for some years with great success. A little while ago, I changed my mail server from Fedora to CentOS linux. I reinstalled dovecot, and *almost* everything seems to be working, but one thing. There's *one* user I can't get it to work on without a workaround. The user is "newuser" and the uid is 1111 (actual name and number changed to protect

After upgrading to 3.4.0, I can no longer add new users. Any users that were added beforehand work fine. Any users that I attempt to create cannot login (error: NT_STATUS_LOGON_FAILURE). I was able to get one new user account to work (see below), but I cannot add any new users. The server is Ubuntu 9.10 running Samba 3.4.0. I am using: security = user pam password change = yes Updating

On 21/10/15 17:37, Ole Traupe wrote: > I think I finally managed to understand the [homes] part of the man > pages, and what my problem is: > https://www.samba.org/samba/docs/man/manpages/smb.conf.5.html > > The misunderstanding comes from my practice I learned on Windows to > just share the "\\server\home" directory and to create per-user > sub-folders

Dear all, on CentOs7 based linux w. different versions of Samba (4.6.x from CentOS repos, but also Sernet-Samba-4.7.4 and also compiled from source), "wbinfo -i user at domain.tld" returns different results before the first successful authentication of the user. Server joined as member to Active Directory, idmapping via tdb2. On first attempt, the result returns

I have two instances of an openldap-2.4.39 server running with syncrepl in a master-master replication setup. These are Centos 7.1 test servers which have been running for over 2 months now with no problems. Partly the good behavior of the LDAP servers is due to very little exercise. Yesterday I decided to try and see exactly how well replication was working. With server-2 up and running I

I am running Samba version 3.0.9-1.3E.2 on a server that is joined to a windows server 2003 domain using ADS security. The samba server hosts a share called 'files'. I am having problems mounting this share using a new account I set up. getent passwd shows the information for the new account as does wbinfo -u. Mounting the share with the new users account using the net use command

I would expect same permissions as for root mail directory 02770: drwxrws--- 5 newuser mail 4096 Apr 23 19:31 /var/spool/mail/newuser/ Using Dovecot 2.2.34 On 14.05.2018 08:37, Aki Tuomi wrote: > > > On 09.05.2018 12:52, telsch wrote: >> Hello, >> >> the wiki page describe that permission should copied from root mail >> directory >>

Hi we're busy discovering samba4 at the moment. we've installed fedora-ds as ldap backend. all install's configs and provisioning went well.. (no strange errors orso) after fireing it all up we tried to add a user and this is what we got back: ----------------------------------------- Traceback (most recent call last): File "./newuser", line 69, in <module>

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here is a description of what I am trying to do (with Samba 3.0.2a & openldap 2.1.27): I have all my users populated into the LDAP with all the applicable attributes; Users can map drives to a server using LDAP as the authentication backend without issue. Where I am running into problems is bringing up a PDC using Samba w/LDAP. * I added

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I migrated a samba3 with openLDAP to Samba 4 (sernet package 4.13). I can see all migrated users on all DCs and fileservers with "wbinfo -u" and "getent passwd" and all informations for a single user with "getent passwd <username>" and "wbinfo -i <username>". Now, after migration, if I

I use mdbox not maildir: mail_location = mdbox:/var/spool/mail/%u On 15.05.2018 11:53, Aki Tuomi wrote: > Do you have > > mail_location=maildir:~/mail > > or > > mail_location = maildir:/path/to/whatever/%u > > I tested with latest 2.2 that if I use /path/to, I get correct permissions. > > Aki > > > On 15.05.2018 12:43, telsch wrote: >> I

How does everyone handle this case? Users are authenticated by LDAP, and do not have accounts on the IMAP/dovecot server. When a new user is added to LDAP, the home directory (/home/newuser) needs to be created on the IMAP/dovecot server so dovecot can create the mail directories inside it (/home/newuser/mail/). Obviously I can come up with a few custom solutions, utilizing cron, but I feel

Hello, I have a samba server (old - running FC6, samba 3.0.24-11.fc6) that authenticates against AD. This is all configured and has been working fine until this week. A new user has been added to AD, but cannot access the samba drives. All other users can still access samba as normal. net ads testjoin reports OK. wbinfo -a newuser%pass and wbinfo -K newuser%pass both succeed. wbinfo -r

With this settings I don't get the expectet result, still get wrong permissions on new mailboxes. Aki did you also try with %u ? > In /etc/dovecot/conf.d/10-mail.conf follow options are set: > mail_gid = mail > mail_privileged_group = mail > mail_access_groups = mail > mail_location = mdbox:/var/spool/mail/%u On 15.05.2018 13:06, Aki Tuomi