Displaying 20 results from an estimated 6000 matches similar to: "Postfix/Dovecot permissions for new mailboxes"
2018 May 15
2
Postfix/Dovecot permissions for new mailboxes
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
>>
2018 May 15
2
Postfix/Dovecot permissions for new mailboxes
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
2018 May 15
2
Postfix/Dovecot permissions for new mailboxes
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
2018 May 16
1
Postfix/Dovecot permissions for new mailboxes
Yes, this settings work as i expected, but i didn't found documentation for
mail_home=
Thanks
On 15.05.2018 20:10, Aki Tuomi wrote:
>
> Well, that's not what I asked you to try...
>
> try
>
> mail_home=/var/spool/mail/%u
> mail_location=mdbox:~/
>
> Aki
>
>> On 15 May 2018 at 20:03 telsch <telsch at gmx.de> wrote:
>>
>>
>>
2018 May 15
0
Postfix/Dovecot permissions for new mailboxes
Well, that's not what I asked you to try...
try
mail_home=/var/spool/mail/%u
mail_location=mdbox:~/
Aki
> On 15 May 2018 at 20:03 telsch <telsch at gmx.de> wrote:
>
>
> 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
2018 May 15
0
Postfix/Dovecot permissions for new mailboxes
I have to correct myself. I tested with sdbox now too, and it seems that
using
mail_location=sdbox:~/Mail
produces the expected behaviour. mdbox uses same code as sdbox for this,
so it should work fine.
Aki
On 15.05.2018 13:01, telsch wrote:
> I use mdbox not maildir:
>
> ????mail_location = mdbox:/var/spool/mail/%u
>
> On 15.05.2018 11:53, Aki Tuomi wrote:
>> Do you have
2018 May 15
0
Postfix/Dovecot permissions for new mailboxes
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 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
>
>
2018 May 14
0
Postfix/Dovecot permissions for new mailboxes
On 09.05.2018 12:52, telsch wrote:
> Hello,
>
> the wiki page describe that permission should copied from root mail
> directory
> ????https://wiki2.dovecot.org/SharedMailboxes/Permissions
>
> The permissions for the root mail directory are set to 2770:
> ????drwxrws--- 36 root mail 4096 Apr 15 02:30 /var/spool/mail/
>
> But newly created mailboxes get following
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
2010 Mar 31
2
Shared mailboxes unix permissions
Hello Timo,
I'm running dovecot-1.2.11/Maildir and plan to migrate to single UID mailboxes
some day, but for now, I've got "system" users and I'm testing permissions
handling in order to set up shared mailboxes.
The private namespace mailboxes location is
location = maildir:/courriel/boites/%u:CONTROL=/courriel/meta/%u:INDEX=/var/dovecot-test/indexes/%1u/%u
I've
2017 Mar 03
1
Dovecot + SpamAssassin through dovecot-antispam
On 2017-03-03 10:26, Bernard wrote:
> No help there?
> ---
> Bernard
>
> On 01/03/2017 11:27, Bernard wrote:
>> 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
2017 Mar 03
1
Dovecot + SpamAssassin through dovecot-antispam
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 3 Mar 2017, Bernard wrote:
> On 01/03/2017 11:27, Bernard wrote:
>> 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
2018 Apr 19
2
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
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
2018 May 21
2
Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"
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
2013 Aug 29
2
Bizarre permissions problem
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
2011 Jul 14
1
Problem adding new users after upgrade to 3.4.0
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
2018 Mar 11
1
wbinfo -i output different before 1st authentication
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
2015 Oct 21
2
Can't get 'root preexec' to run
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
2004 Mar 31
2
Problem w/ Samba 3 & LDAP
-----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
2014 Nov 06
1
new users not seen with getent passwd
-----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