X-Git-Url: https://vcs.fsf.org/?p=exim.git;a=blobdiff_plain;f=doc%2Fdoc-misc%2FWishList;h=4d10b94d39f885685688724807fa532859170225;hp=c42118bfdc7c62cf50bad9dbd14b3e402af23d0c;hb=75faf2411c4a910c57bd09e93dbb02e7279c05a7;hpb=596875b36050036d49d3160f91d04c9e70eb60af

diff --git a/doc/doc-misc/WishList b/doc/doc-misc/WishList
index c42118bfd..4d10b94d3 100644
--- a/doc/doc-misc/WishList
+++ b/doc/doc-misc/WishList
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-misc/WishList,v 1.25 2005/03/15 15:36:41 ph10 Exp $
+$Cambridge: exim/doc/doc-misc/WishList,v 1.27 2005/03/30 08:23:11 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.
@@ -1714,7 +1715,7 @@ include sockets as well as TCP/IP connections. Also, people want to make use of
 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.
+"callout" mode instead of keeping things separate? See also 253 and 323.
 
 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
@@ -1887,5 +1888,12 @@ address. The wish is for options to control these numbers.
 
 (322) 15-Mar-05 M Add a /defer_ok option to verify=reverse_host_lookup
 ------------------------------------------------------------------------------
---- HWM 322 ------------------------------------------------------------------
+
+(323) 15-Mar-05 M Make callouts use smtp_data from the smtp transport
+
+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 ------------------------------------------------------------------
 ---------------------------- End of WishList ---------------------------------