X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/e05f33e0b79c14608757a60f2f3f8588008355f7..4deaf07d6cdd04468e4bc383945b9e19d7d55aa3:/doc/doc-misc/WishList diff --git a/doc/doc-misc/WishList b/doc/doc-misc/WishList index bee4f328a..3863f1bdd 100644 --- a/doc/doc-misc/WishList +++ b/doc/doc-misc/WishList @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-misc/WishList,v 1.1 2004/10/08 10:38:47 ph10 Exp $ +$Cambridge: exim/doc/doc-misc/WishList,v 1.5 2004/11/02 09:39:44 ph10 Exp $ EXIM 4 WISH LIST ---------------- @@ -630,7 +630,7 @@ This could perhaps be done by extending the local_scan() idea and providing a (15) 01-Jan-02 M More hooks like local_scan() One request has been for a similar hook at logging time. For other SMTP -interactions, maybe a hook into the ACL? See also 79 and 218. +interactions, maybe a hook into the ACL? See also 79 and 218 and 301. ------------------------------------------------------------------------------ (17) 11-Jan-02 M The construction of config.h needs refactoring @@ -1717,11 +1717,71 @@ AUTH during the callout checking, on all types of connection. I suppose that means making TLS available as well. This probably means a rewrite of the code that actually does the callout. Should we use the relevant transport in a new "callout" mode instead of keeping things separate? See also 253. + +And here's another submitted idea: "My actual suggestion is that if this model +is followed, the parent process doesn't have to stop the callout process if it +is taking too long to respond: it can return 450 to the incoming connection +within the 5 minute SMTP command timeout and leave the callout process to +continue, in the hope that it will eventually get a result and store it in the +callout cache in time for the sender's next attempt." ------------------------------------------------------------------------------ (296) 09-Sep-04 S Make deliver_time work for == lines as well as => What about ** lines? ------------------------------------------------------------------------------ ---- HWM 297 ------------------------------------------------------------------ + +(298) 25-Oct-04 S Debugging the daemon process only + +When there are daemon problems (e.g. it dies) it would be helpful to be able to +turn on debugging that did not get passed on to any subprocesses. +------------------------------------------------------------------------------ + +(299) 25-Oct-04 S Options to make Sieve "keep" pass to next router + +Currently, "keep" saves in the mailbox. Probably need two options, for implicit +and explicit keep commands. +------------------------------------------------------------------------------ + +(300) 25-Oct-04 S Option to lock out Sieve or Exim filter + +Currently, if allow_filter is set, either kind of filter is permitted. +------------------------------------------------------------------------------ + +(301) 27-Oct-04 M Use an "ACL" to filter logging + +This idea was for ACL syntax to be able to "accept" or "deny" individual log +lines. This would make it possible to have, for example, per-host logging for +certain things. See also 15 above. +------------------------------------------------------------------------------ + +(302) 28-Oct-04 M Expand pass_router and redirect_router + +Doing this would mean postponing the validity checks till the router was +actually used instead of doing them at start up. It does not seem to be a +facility that will be widely used. +------------------------------------------------------------------------------ + +(303) 28-Oct-04 M Support SQL relay + +This would make it easier for packagers to support "generic SQL" without having +to choose which one. It can be slotted in using a MySQL interface without +modifying Exim, but native support would be nice. +------------------------------------------------------------------------------ + +(304) 02-Nov-04 M A way of seeing the whole message in Perl or ${run + +At present, the headers are available in $message_headers, but only part of +the body is visible. The only way to pass the whole body would be as a file +descriptor because it can be very large. See also (42). +------------------------------------------------------------------------------ + +(305) 02-Nov-04 M A Perl transport + +The suggestion here is that an embedded Perl function takes responsibility for +doing the delivery. I am not at all keen on this. One way of doing it would be +to implement (244), which provides an "on success" string expansion. Then +anyone who wants this could run that on a transport that does nothing. +------------------------------------------------------------------------------ +--- HWM 305 ------------------------------------------------------------------ ---------------------------- End of WishList ---------------------------------