https://bugs.exim.org/show_bug.cgi?id=2359
Jeremy Harris changed:
What|Removed |Added
Status|NEW |WAIT_FIX_CONFIRMATION
--
You are receiving
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://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://bugs.exim.org/show_bug.cgi?id=2358
--- Comment #2 from Jeremy Harris ---
It depends how complex you want it; for the simplest case place this class
of messages in an alternate named queue, set up the queue-runner to run M
times per hour and have a queue_run_stop router triggering after
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
https://bugs.exim.org/show_bug.cgi?id=423
--- Comment #24 from Simon Arlott ---
I attached patches for this yesterday.
I had to tweak some of the messages to make them work properly. Some of the
addr->user_messages don't fit as addr->messages because they assume a prefix
sentence will be
On Thu, 27 Dec 2018, admin--- via Exim-dev wrote:
https://bugs.exim.org/show_bug.cgi?id=2358
--- Comment #2 from Jeremy Harris ---
It depends how complex you want it; for the simplest case place this class
of messages in an alternate named queue, set up the queue-runner to run M
times per
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/ ##
https://bugs.exim.org/show_bug.cgi?id=338
Jeremy Harris changed:
What|Removed |Added
See Also||https://bugs.exim.org/show_
|
https://bugs.exim.org/show_bug.cgi?id=2360
Bug ID: 2360
Summary: Set maildir flags from a filter
Product: Exim
Version: 4.91
Hardware: All
OS: All
Status: NEW
Severity: wishlist
Priority: medium
https://bugs.exim.org/show_bug.cgi?id=2359
--- Comment #1 from Jeremy Harris ---
[jgh: edited to hide identifying info]
Created attachment 1160 [details]
First shot at a fix.
Hello,
exim (4.92 rc2) built against gnutls >= 3.6.5 supports TLS 1.3. However while
incoming connections seem to
https://bugs.exim.org/show_bug.cgi?id=2360
Jeremy Harris changed:
What|Removed |Added
See Also||https://bugs.exim.org/show_
|
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
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
https://bugs.exim.org/show_bug.cgi?id=2359
Git Commit changed:
What|Removed |Added
CC||g...@exim.org
--- Comment #2 from Git Commit ---
15 matches
Mail list logo
