-$Cambridge: exim/doc/doc-misc/WishList,v 1.34 2005/05/31 11:31:30 ph10 Exp $
+$Cambridge: exim/doc/doc-misc/WishList,v 1.40 2005/06/21 14:14:55 ph10 Exp $
EXIM 4 WISH LIST
----------------
The problem with header_remove followed by header_add is that you can't refer
to the previous value of the header when adding a replacement. This could be
-solved with a replace_header option.
+solved with a replace_header option. See also Exim 4/333.
------------------------------------------------------------------------------
(43) 15-Oct-98 M Sender rewrite *after* SMTP incoming checks
Dave Lewney
John Holman
-Such as "return-receipt-to". See also 41.
+Such as "return-receipt-to". See also 41. See also Exim 4/333.
------------------------------------------------------------------------------
(90) 21-Apr-99 M change wild prefix/suffix greediness
A separate but related issue is the effect of headers added by "unseen"
directors. These are documented in chapter 19 as not being accumulated. Should
-any change be made?
+any change be made? See also Exim 4/333.
------------------------------------------------------------------------------
(155) 16-Jun-2000 M Special handling for certain hosts
feature would use a regex to match whole lines and replace them. It could be
useful for patching up syntactically invalid lines from crappy clients, before
the syntax check kicks in. (It might also be useful for hiding local host names
-in Received: headers.)
+in Received: headers.) See also 333.
------------------------------------------------------------------------------
(58) 26-Jun-02 ? Extend PAM support
"I'd like to be able to give Exim a list of headers that must be removed
from the message at arrival, before data_acl processing (and before the
-rcpt_acl warn headers are added to the message)."
+rcpt_acl warn headers are added to the message)." See also 333.
------------------------------------------------------------------------------
(63) 28-Jun-02 S Access to ACL-added headers in ACLs
"I'd like also to be able to look at the already added headers by a
rcpt_acl when still checking rcpt_acl (either later in the acl for the same
-RCPT TO or for another RCPT TO)."
+RCPT TO or for another RCPT TO)." See also 333.
------------------------------------------------------------------------------
(65) 28-Jun-02 M Expand fallback hosts
------------------------------------------------------------------------------
(160) 19-May-03 M Remove headers using wild cards
+
+See also 333.
------------------------------------------------------------------------------
(162) 28-May-03 M/L Use of real numbers in filters, expansions, and options
------------------------------------------------------------------------------
(212) 31-Oct-03 M specify headers lines in HELO ACL to be added to all msgs
+
+See also 333.
------------------------------------------------------------------------------
(214) 05-Nov-03 S Put the wild part of local part prefix/suffx in variables
(237) 02-Feb-04 M Add_header in ACLs because "message" is overloaded
-This would be useful for verbs where "message" is an error message.
+This would be useful for verbs where "message" is an error message. See also
+333.
------------------------------------------------------------------------------
(238) 05-Feb-04 S ${address to handle multiple addresses
will be required.
This can now be done fairly generally from local_scan(), and at the start and
-after the Received: block from an ACL. Is anything more needed?
+after the Received: block from an ACL. Is anything more needed? See also 333.
------------------------------------------------------------------------------
(271) 02-Jun-04 L Callouts at routing time
(314) 15-Feb-05 M Multiple headers_{add,remove} for routers
If headers_{add,remove} could be specified multiple times, it would be easier
-for those people that construct configs using .ifdef or .include, etc.
+for those people that construct configs using .ifdef or .include, etc. See also
+333.
------------------------------------------------------------------------------
(315) 15-Feb-05 M String variables for use in filters.
solutions with a similar requirement."
------------------------------------------------------------------------------
-(320) 03-Mar-05 T Options to control daemon retry binding
-
-Currently the daemon tries 10 times at 30-second intervals to listen on an IP
-address. The wish is for options to control these numbers.
-------------------------------------------------------------------------------
-
(321) 07-Mar-05 S Run an ACL on a sync error
... and possibly "accept" or "deny" it.
This is in the Bugzilla as #10.
------------------------------------------------------------------------------
-(325) 28-Apr-05 ? Support for quotas over 2G in appendfile.
-
-Things get bigger far more quickly than I ever imagine...
-------------------------------------------------------------------------------
-
(326) 03-May-05 ? Queue-only on memory shortage
This is bugzilla #17. The idea is to have something like queue_only_load that
deletions stick with that address, and the "clone" address that continues to be
routed starts off without any additions or removals. This request is for an
option to select other actions: retain header actions with the clone only, or
-pass them on to both addresses.
+pass them on to both addresses. See also 333.
------------------------------------------------------------------------------
(329) 12-May-05 S Create message ID at MAIL FROM time
per-transport, to avoid these difficulties. If we made all retry keys depend on
the transport, this would happen automatically.
------------------------------------------------------------------------------
---- HWM 331 ------------------------------------------------------------------
+
+(332) 03-Jun-05 S A "receive time taken" log selector
+
+This suggestion is to at an RT= item to the <= line, giving the time it
+actually took to receive the message.
+------------------------------------------------------------------------------
+
+(333) 06-Jun-05 L Re-think and re-implement header handling
+
+There are a number of items related to headers above. Better facilities for
+handling headers at ACL time are needed. The whole way in which Exim handles
+headers should be re-planned and re-implemented in a more consistent manner.
+
+These are the main previous items:
+
+Exim 3 Wish List: 41, 85, 149, 187.
+Exim 4 Wish List: 55, 62, 63, 160, 212, 237, 270, 314, 328.
+------------------------------------------------------------------------------
+
+(334) 07-Jun-05 M Support for messages larger than 2G
+
+This is probably a longish-term thing at the moment. Quotas over 2G are now
+supported, but not individual messages; no doubt one day this will be wanted.
+------------------------------------------------------------------------------
+
+(335) 14-Jun-05 T Re-arrange default configuration
+
+A small niggle which might be worth fixing is the ordering of the ACL in the
+default configuration file. The relay_from_hosts and authenticated clauses
+would be better off before the dnslists examples. However, this should be left
+until a x.x0 release, because of the documentation implications.
+------------------------------------------------------------------------------
+
+(336) 16-Jun-05 M Show recipient(s) after header check failure
+
+The mainlog line for "There is no valid sender in any header line" shows the
+sending host and the envelope sender, but does not show any recipients. There
+has been a request to show recipients. Presumably this should be on some new
+log selector, and it must have a cutoff maximum number of recipients. NOTE: the
+data in the reject log does show the envelope recipients as part of its
+additional data.
+------------------------------------------------------------------------------
+--- HWM 336 ------------------------------------------------------------------
---------------------------- End of WishList ---------------------------------
git://git.exim.org / exim.git / blobdiff