[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #7 from Jeremy Harris --- That's what I mean by #3 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #6 from Simon Arlott --- I mean extending the "save" data to include the current values of $n0..$n9 at that time in the file. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #5 from Jeremy Harris --- Not if you want multiple "save" commands with possibly different values. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #4 from Simon Arlott --- (In reply to Jeremy Harris from comment #3) > There's only one return from the filtering > code - not multiple calls from the filter to the transport - and for "save" > there is explicity one item of numeric data carried per filename. Extending > that will be messy and error-prone. Should it be extended to provide $n0 to $n9 (and map them to $filter_n*)? That would make it possible to vary maildir_tag in the transport. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #3 from Jeremy Harris --- That's not a good solution, then. There's only one return from the filtering code - not multiple calls from the filter to the transport - and for "save" there is explicity one item of numeric data carried per filename. Extending that will be messy and error-prone. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 --- Comment #2 from Simon Arlott --- (In reply to Jeremy Harris from comment #1) > If a router-called filter could set a variable that was accessible in the > transport, would that cover this use-case? Yes, but for general use the maildir flags should be per "save" command. I didn't want to require a set/save/unset sequence. It's going to be more awkward to strip flags in a string expansion but it'll work for me. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2360] Set maildir flags from a filter
https://bugs.exim.org/show_bug.cgi?id=2360 Jeremy Harris changed: What|Removed |Added See Also||https://bugs.exim.org/show_ ||bug.cgi?id=338 --- Comment #1 from Jeremy Harris --- A supported means for returning values from (non-system) filters seems like it would be a more general feature. I don't see it documented at present; system filters can (limited to the $n0 to $n9 numeric variables) so at least some of the required support is there. If a router-called filter could set a variable that was accessible in the transport, would that cover this use-case? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
