Alright, now I've read some more chapters of the manual. It seems like I
could provide the absolute maildir path in the 'directory' option of the
'appendfile transport' as well. I'm not currently doing that, which
means that the value must be provided by the 'redirect router', that
currently has it in its 'data' option.
So I guess I should move the maildir database query from the router to
the transport so I can provide the Sieve script in the router's data option.
But what if the user/mailbox has no script? Then 'data' is empty and the
router declines altogether. Should I provide the maildir path as
fallback if no script is available? Or could I use a system-provided
default script that does nothing special?
And will the 'fileinto' command in a Sieve script just place the message
in that subdirectory of the maildir root that is specified in the transport?
Yves
________________________________________
Von: Jeremy Harris
Gesendet: Sa, 2017-05-27 15:29 +0200
On 27/05/17 14:03, Yves Goergen wrote:
I'm already through these chapters. The problem is that the 'data'
statement is already used for the maildir location in my case. I can't
use it for the filter contents.
Do a separate lookup for the delivery location, in your appendfile
transport.
And chapter 1 requires local files in
user home directories which I said I don't have for virtual users.
It doesn't say "requires", it says "usually".
Another question is how the managesieve service can be integrated in
this.
Can't help with that.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
