Hi, What are the recommended ways to give access to their .dovecot.sieve.log messages to the users? I am thinking about placing this file into users Maildir/new, or piping to dovecot-lda. -- Regards, Sergey Ivanov -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20180201/384428bd/attachment.sig>
Am 01.02.2018 um 18:01 schrieb Sergey Ivanov:> Hi, > What are the recommended ways to give access to their .dovecot.sieve.log messages to the users? > I am thinking about placing this file into users Maildir/new, or piping to dovecot-lda.or serve the log as "magic folder". If the user delete the message it deletes also the log ... just an idea... Andreas
Andreas, can you explain "magic folder"? The only thing I tried was creating named FIFO .dovecot.sieve.log, and starting mailx user at my.domain.com < .dovecot.sieve.log which need to be done for each user of my domain, and better wrapped in some script which will make it started after each sievec run. -- Regards, Sergey. On Fri, Feb 2, 2018 at 7:23 PM, A. Schulze <sca at andreasschulze.de> wrote:> > > Am 01.02.2018 um 18:01 schrieb Sergey Ivanov: > > Hi, > > What are the recommended ways to give access to their .dovecot.sieve.log > messages to the users? > > I am thinking about placing this file into users Maildir/new, or piping > to dovecot-lda. > > or serve the log as "magic folder". If the user delete the message it > deletes also the log ... > just an idea... > > Andreas >-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180204/e0854ab7/attachment.html>
Answering myself (not yet implemented, but I hope it will work):
Using sieve extprograms extension and global "after" script, I can
read
.dovecot.sieve.log into a sieve variable 'log_content' if this log is
not
empty. I hope this log will be written before "after" script is
called, but
will check if it is true.
Then using sieve "notify" action with mailto:
${user_mailaddress}?body=${log_content}"
--
Sergey.
On Thu, Feb 1, 2018 at 5:01 PM, Sergey Ivanov <seriv at cs.umd.edu> wrote:
> Hi,
> What are the recommended ways to give access to their .dovecot.sieve.log
> messages to the users?
> I am thinking about placing this file into users Maildir/new, or piping to
> dovecot-lda.
>
> --
> Regards,
> Sergey Ivanov
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dovecot.org/pipermail/dovecot/attachments/20180207/7317536a/attachment.html>
On Feb 6, 2018, at 19:53, Sergey Ivanov <seriv at cs.umd.edu> wrote:> Answering myself (not yet implemented, but I hope it will work): > Using sieve extprograms extension and global "after" script, I can read .dovecot.sieve.log into a sieve variable 'log_content' if this log is not empty. I hope this log will be written before "after" script is called, but will check if it is true. > Then using sieve "notify" action with mailto:${user_mailaddress}?body=${log_content}"Did that work? -- This is my signature. There are many like it, but this one is mine.>