Yves Goergen wrote:
To be honest, I can't follow you. I see that I have inconsistent
permissions (but all the same owner and group). I did use a different
mail server software in the past, but that's long ago and I can't even
remember when I switched to Dovecot. I think it was Courier-IMAP before
In an effort to analyse this, I think I have found the cause for the
inconsistent permissions.
mkdir -p -m 700 "/var/mail/virtual/$1/$2/.Trash/cur"
will create .Trash/cur with mode 700. But if .Trash doesn't already
exist, it will be created with some default mode which is not 700.
mkdir
I've looked up the mode letters and tried this command:
chmod go-rx .Trash
The Trash subdirectories already have the same mode as the mailbox
directory. With the changed mode on .Trash, the deletion did work. So I
guess my maildirs were created with the wrong mode. I'm using this
script to cr
To be honest, I can't follow you. I see that I have inconsistent
permissions (but all the same owner and group). I did use a different
mail server software in the past, but that's long ago and I can't even
remember when I switched to Dovecot. I think it was Courier-IMAP before.
Maildirs for ne
0b4a77c09cb4c18c49177e4ad76e0b62e3ec5ae0
Yves Goergen wrote:
The issue still exists. Can anybody explain to me why dovecot creates
IMAP folders with the wrong filesystem permissions?
On a lark, I looked through my dirs @ permissions. Shorted lines a bit
so they'd fit w/o extra lines between them using:
(get rid of text before permiss
https://wiki.dovecot.org/Authentication/Policy is the correct link.
---Aki TuomiDovecot oy
Original message From: Aki Tuomi Date:
21/05/2018 19:19 (GMT+02:00) To: Marc Perkel ,
dovecot@dovecot.org Subject: Re: Dovecot blacklist?
Or you can implement a policy server yourself
Or you can implement a policy server yourself. :)The protocol is not
complicated, json over http. See https://wiki.dovecot.org/Auth/Policy
---Aki TuomiDovecot oy
Original message From: Aki Tuomi Date:
21/05/2018 19:13 (GMT+02:00) To: Marc Perkel ,
dovecot@dovecot.org Subjec
https://github.com/PowerDNS/weakforced cn be used for this.
---Aki TuomiDovecot oy
Original message From: Marc Perkel Date:
21/05/2018 19:09 (GMT+02:00) To: dovecot@dovecot.org Subject: Dovecot
blacklist?
Just wondering if there is an easy way to have dovecot do a blacklist
Just wondering if there is an easy way to have dovecot do a blacklist
lookup as a negative authentication so that if the IP is on a blacklist
then authentification fails even if they get the password right.
If this works I have a blacklist everyone can use.
You forgot to cc the list.
ssl_ca is used only for validating client certificates.
---Aki TuomiDovecot oy
Original message From: Marc Perkel Date:
21/05/2018 18:25 (GMT+02:00) To: Aki Tuomi Subject:
Re: SSL error after upgrading to 2.31
On 05/21/2018 07:54 A
Does ssl_cert file contain intermediates?
---Aki TuomiDovecot oy
Original message From: Marc Perkel Date:
21/05/2018 16:32 (GMT+02:00) To: dovecot@dovecot.org Subject: SSL error after
upgrading to 2.31
After upgrading to 2.31 I'm getting this
error. Not sure what
After upgrading to 2.31 I'm getting this error. Not sure what I'm doing
wrong.
No (No signatures could be verified because the chain contains only one
certificate and it is not self signed.)
ssl = yes
ssl_cert =
Le 21/05/2018 à 12:38, Aki Tuomi a écrit :
> can you try turning on pluign { fts_enforced = yes } and repeat your test?
Same (wrong) result:
1. Send an email with "too6Ouka" in the body
2. Search against "too6Ouka":
# doveadm search -u username mailbox INBOX body too6Ouka
--> No result
3. Force
can you try turning on pluign { fts_enforced = yes } and repeat your test?
Aki
On 21.05.2018 13:31, kada...@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 inde
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 ag
On 27.04.2018 16:51, Webert de Souza Lima wrote:
> Hey Aki Tuomi, how are you doing?
>
> I have tried many ways for getting 2.2.35 pre-built installed via
> 'apt-get install' in Debian Jessie and Stretch using the official repos.
> The reason I prefer to install pre-built instead of compiling it
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, kada...@gmail.com wrote:
> Bump. Can someone from dovecot dev team please respond something to my
> problem ?
On 06.05.2018 13:13, André Rodier wrote:
> Hello again,
>
> I have created a parser script, a little bit more advanced than the
> one provided with Dovecot. The main feature is probably to index
> documents inside zip/rar/tgz archives...
>
> I am using Ansible, swaks and doveadm to run automatic
I guess you have had different version(s) or setting(s) in the past, and
you can probably fix this by setting perms to same as the new folders.
Aki
On 21.05.2018 11:46, Yves Goergen wrote:
> I couldn't find anything relevant between all the debug log lines. Is
> that in /var/log/mail.log?
>
> He
I couldn't find anything relevant between all the debug log lines. Is
that in /var/log/mail.log?
Here's the lines I think are related to creating and deleting the folder:
May 21 10:36:14 mond2 dovecot: imap(yg@.de): Debug: Namespace :
/var/mail/virtual/.de/yg/.Test doesn't exist yet,
22 matches
Mail list logo