Dovecot's acl plugin can prevent deletion of messages,it works very well!
I want:
Some ips can delete messages, other ips can not delete messages,can anyone help
me?
h...@cndns.com
On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot
wrote:
>
> * Amir Caspi via dovecot, 12.08.19 22:01
>
>> [~]# doveadm mailbox status -u cepheid firstsaved Junk
>> Junk firstsaved=1563154976
>>
>> I can't tell how that timestamp corresponds to a human-readable date,
>> however.
>
>
* Amir Caspi via dovecot, 12.08.19 22:01
> [~]# doveadm mailbox status -u cepheid firstsaved Junk
> Junk firstsaved=1563154976
>
> I can't tell how that timestamp corresponds to a human-readable date, however.
[zlatko@disclosure:~]$ date -d @1563154976
Mon Jul 15 03:42:56 CEST 2019
HTH,
Thomas
Hello!
Does it update the remote ip for you if you already have a row for a
user? I'm experimenting with a similar feature and it seems to be
updating only the login time. I think it figures the other fields are
all part of the primary key and therefore not supplied to ON DUPLICATE
KEY
On Aug 12, 2019, at 12:18 AM, Sami Ketola via dovecot
wrote:
>
> "1. What's the first mail's saved-timestamp?
> doveadm fetch -u user date.saved mailbox Junk 1
Well... this is giving me strange results. For myself, when I run this
command, I get:
[~]# doveadm fetch -u cepheid date.saved
On 12 Aug 2019, at 00:18, Sami Ketola wrote:
> "1. What's the first mail's saved-timestamp?
> doveadm fetch -u user date.saved mailbox Junk 1
>
> 2. That timestamp should also be the same in dovecot.list.index:
> doveadm mailbox status -u user firstsaved Junk"
>
> can you check that
Hi there!
I can't get ACL working for master users. Login as master user works fine
though, and I am able to access any mailbox using the
auth_master_user_separator "*", tested e.g. via Python's imaplib:
>>> import imaplib
>>> imap = imaplib.IMAP4_SSL('imap.example.com')
>>>
> On 10 Aug 2019, at 3.15, @lbutlr via dovecot wrote:
>
> On 8 Aug 2019, at 13:03, Amir Caspi wrote:
>> IMHO the setting should apply regardless of protocol, but is that actually
>> the case in practice?
>
> It seems to be broken.
>
> I have
>
> namespace inbox {
> inbox = yes
> location
