-$Cambridge: exim/doc/doc-misc/WishList,v 1.31 2005/05/06 08:28:16 ph10 Exp $
+$Cambridge: exim/doc/doc-misc/WishList,v 1.43 2005/07/14 17:17:25 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
copies to the same address.
------------------------------------------------------------------------------
-(73) 17-Jul-02 M Match a list from within a condition
-
-e.g. ${if matchdomain {$domain}{+domainlist} ...
- ${if matchhost {$sender_host_address}{1.2.3.4/10:2.3.4.5/16}...
-
-Thought needed about how to handle host names. This may be too messy to specify
-cleanly.
-
-22-Apr-04: Implemented for domains, addresses, and local parts. Hosts are
-too messy!
-
-The only sensible approach seems to be to allow IP address arguments only.
-Anything else should be diagnosed as an error. However, if a name appears in
-the list, a PTR lookup should be done. This may require a lot of refactoring
-in the code, because of the current assumption that were are (almost) always
-dealing with THE sending host.
-------------------------------------------------------------------------------
-
(74) 22-Jul-02 M Extend -bV to do more semantic checking
For example, diagnose "local_hosts" that should probably be "+local_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
Currently, "delay=5m" (e.g.) waits for 5 minutes. If we can detect that the
connection has died in the meantime, it would make sense to break the delay.
+However, it doesn't seem possible to detect a dropped connection without trying
+to read from it.
+------------------------------------------------------------------------------
+
+(328) 10-May-05 S After "unseen" routing, pass on header additions/deletions
+
+Currently, when an "unseen" router accepts an address, header additions and
+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. See also 333.
+------------------------------------------------------------------------------
+
+(329) 12-May-05 S Create message ID at MAIL FROM time
+
+Currently, the ID is created only when Exim is about to create the data (-D)
+file for an incoming message. In other words, after it knows it really is going
+to accept the message. Creating the ID earlier would mean that rejection
+messages in the log would be tagged with an ID, and this is seen as desirable
+by some people.
+------------------------------------------------------------------------------
+
+(330) 31-May-05 ? Default interface for -bh and default port for -oMi
+
+I do not think it worth putting effort in here for these reasons: If a host has
+multiple interfaces, there's no easy way to choose one to be the default for
+$interface_address when -bh is used. If the host does not have multiple
+interfaces, chances are the configuration won't be looking at
+$interface_address anyway. If you are setting -oMi, and care about the port, it
+isn't much effort to tack on a port number, though in this case, I suppose a
+default of 25 is "obvious".
+------------------------------------------------------------------------------
+
+(331) 31-May-05 M More than one retry time per host
+
+Consider this example: an attempt to start a TLS connection to a host gets a
+temporary error. This stops *all* connections, both for TLS and otherwise.
+Different retry times for different circumstances are needed to get round this.
+What are the circumstances? TLS/not-TLS is clearly one, but sometimes you don't
+know if you are going to try TLS until you have connected. So this makes sense
+only if require_tls is used. Perhaps the multiple retry times should just be
+per-transport, to avoid these difficulties. If we made all retry keys depend on
+the transport, this would happen automatically.
+------------------------------------------------------------------------------
+
+(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.
+------------------------------------------------------------------------------
+
+(337) 29-Jun-05 S Add "defer" to $recipient_verify_failure
+
+This is for when defer_ok was set when verifying recipients. Since this isn't
+for a failure, we probably also need "ok" for the non-fail case.
+------------------------------------------------------------------------------
+
+(338) 14-Jul-05 M Change to Bind 9 API
+
+Exim uses the original API for calling the DNS resolver. There is a newer API
+available, and noises are being made in some OS that compatibility with the old
+API is going to be dropped. Nevertheless, there are sure to be systems about
+for ages that require the use of the old API. Therefore, we will have to
+implement not only an interface to the new API, but a backwards compatibility
+feature. It would be nice if this was automatic.
------------------------------------------------------------------------------
---- HWM 327 ------------------------------------------------------------------
+--- HWM 338 ------------------------------------------------------------------
---------------------------- End of WishList ---------------------------------
git://git.exim.org / users / jgh / exim.git / blobdiff