X-Git-Url: https://git.exim.org/users/heiko/exim.git/blobdiff_plain/fdfdba092c42d919d2942c258b297394c41121da..ec798043f663c0ad9174a6a054534f09517c5b03:/doc/doc-misc/WishList

diff --git a/doc/doc-misc/WishList b/doc/doc-misc/WishList
index 119e31e2d..7ea22dd5b 100644
--- a/doc/doc-misc/WishList
+++ b/doc/doc-misc/WishList
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-misc/WishList,v 1.26 2005/03/15 15:46:24 ph10 Exp $
+$Cambridge: exim/doc/doc-misc/WishList,v 1.34 2005/05/31 11:31:30 ph10 Exp $
 
 EXIM 4 WISH LIST
 ----------------
@@ -301,7 +301,8 @@ This would allow special handling of certain errors from certain hosts. In
 particular, it would allow failing of certain 4xx codes.
 
 This is now available for 4xx responses to RCPT commands. Is anything more
-needed?
+needed? Apparently, yes; there's been a request for a similar feature for MAIL
+commands.
 ------------------------------------------------------------------------------
 
 (148) 15-May-2000 S  Warn recipient if message rejected for quota excession.
@@ -1894,5 +1895,70 @@ This is yet another problem caused by duplicating the SMTP code between the
 transport and the callout verification. See item 294 above. Merging the
 transport and the callout code could prevent this kind of thing from happening.
 ------------------------------------------------------------------------------
---- HWM 323 ------------------------------------------------------------------
+
+(324) 04-Apr-05 ? Make -bP show ACLs
+
+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
+triggers on a shortage of main memory.
+------------------------------------------------------------------------------
+
+(327) 06-May-05 ? Break delay if connection drops
+
+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.
+------------------------------------------------------------------------------
+
+(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.
+------------------------------------------------------------------------------
+--- HWM 331 ------------------------------------------------------------------
 ---------------------------- End of WishList ---------------------------------