Autor: Michael Kefeder Data: Para: exim-dev Assunto: [exim-dev] possible bug: sieve filter not working when router uses
data instead of file
Hi List,
I started to play a little bit with Exim 4.41 and filters. I use a setup
where account data is stored in a mysql database, and i wanted to store
the filters there too. Thats why i used the following router and
transport to enable filters per user:
does not and produces the following output to the exim_main.log file:
2004-08-23 22:04:20 1BzL3D-0004XA-4W == save inbox <localpart@???>
R=xams_forward T=xams_address_file defer (-21): appendfile: file or
directory name "inbox" is not absolute
It thought it maybe is a configuration issue and started to fiddle
around a lot, but when i changed the router to point to a .forward file
instead of using "data" the very same sieve filter from above works.
To sum it up again:
- router using data with Exim-filter works
- router using file = .forward with Exim-filter works
- router using data with Sieve-filter does not work
- router using file = .forward with Sieve-filter works
Maybe it is technically impossible to use the data directive for
sieve-filters or something but i did not find anything about that in the
docs? I just wanted to tell you my experiences and would be very happy
if sieve filters work with data too, therefore i'm crossing my fingers
that it _is_ a bug that can be fixed ;-)
Also I don't know how to nicely write sieve scripts for maildir - using
the full path to the maildir is quite clumsy and also not obvious to
users from outside (a.k.a. customers, they have no idea of my servers
directory layout ;)). I think I'm missing something obvious here, but
all sieve examples i've found so far seem to be for mbox or cyrus-imap
as mailstore and they use fileinto "inbox.subdir"; - Is there something
similar available for maildir? Any example scripts for sieve+maildir out
there? I'm just curious about that, if that question doesn't fit here
simply ignore it ;)
Thanks in advance for any useful hints
Mike
p.s.: I hope posting to exim-dev is ok for this mail, because i think it
is a bug i'm describing here.