Thank you for your answer
> .mailfilters is used by maildrop's embedded mode. Those files should
> not be mixed with delivery mode instructions (the .mailfilter file),
AFAIK.
Okay, I use delivery mode, so it will not work.
>
> As far as I can tell, "include" doesn't support globs, either.
I
Hi,
I try to split my maildrop rules into different files ordered by
filename. Now I would like to execute all these files in batch till one
rule will match and exit maildrop.
The only file, which maildrop executes is .mailfilter in the user's
home. But it should execute all files within
On 02/09/2016 10:55 AM, André Rothe wrote:
> The .mailfilter calls a Bash script, which builds a current list of
> ruleset files, which the .mailfilter includes again.
And if you have two simultaneous deliveries, there is some risk that
mailfilters/list will be empty when one of the maildrop
André Rothe writes:
My solution is now:
.mailfilter
cc "|scripts/buildfilterlist"
include "mailfilters/list"
A directory "mailfilters" in the user's home which contain a lot of
preordered rulesets.
scripts/buildfilterlist
#!/bin/bash
ls -1 mailfilters/* | grep "^.*/[0-9]\{2,\}_.*" | sed -e
On 02/09/2016 07:19 AM, André Rothe wrote:
> My first idea was to include the files witin .mailfilter:
> include "/path/to/my/home/.mailfilters/*"
.mailfilters is used by maildrop's embedded mode. Those files should
not be mixed with delivery mode instructions (the .mailfilter file), AFAIK.
As
