-$Cambridge: exim/doc/doc-misc/WishList,v 1.51 2005/10/03 09:11:42 ph10 Exp $
+$Cambridge: exim/doc/doc-misc/WishList,v 1.56 2005/11/15 09:27:25 ph10 Exp $
EXIM 4 WISH LIST
----------------
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
The natural syntax for this would be to use a regex, like this:
${lookup regex{/some/file regex}{found-string}{not-found-string}}
------------------------------------------------------------------------------
---- HWM 343 ------------------------------------------------------------------
+
+(344) 10-Oct-05 M Make debug_print work in authenticators
+------------------------------------------------------------------------------
+
+(345) 14-Oct-05 M Standardize rejection messages
+
+"The parsing for rejection lines is a bit of a mess, and fairly
+unmaintainable. Do you think it would be possible to standardise
+rejection/refusal log messages? How about something like:
+
+(<ID>|16 Spaces) *< (Connection|MAIL|RCPT|HELO|EHLO|DATA) rejected (from
+<Address>)?: <Reason> (\(<Detail>\))?"
+------------------------------------------------------------------------------
+
+(346) 20-Oct-05 S Set $domain and $local_part in retry matching
+
+Currently, these variables are unset. Make it like rewrite matching.
+------------------------------------------------------------------------------
+
+(347) 15-Nov-05 M Arrange to expand data from wildlsearch
+
+This would allow keys that are regular expressions to set up numerical
+variables that are included in the data. This has to be done inside the lookup
+code, because of caching. Probably means we have to invent ewildlsearch and
+enwildlsearch.
+------------------------------------------------------------------------------
+--- HWM 347 ------------------------------------------------------------------
---------------------------- End of WishList ---------------------------------