Commit | Line | Data |
---|---|---|
aa2b5c79 | 1 | $Cambridge: exim/doc/doc-misc/WishList,v 1.48 2005/08/30 09:19:33 ph10 Exp $ |
e05f33e0 PH |
2 | |
3 | EXIM 4 WISH LIST | |
4 | ---------------- | |
5 | ||
6 | Even when it was first released, Exim 4 had a Wish List because not all the | |
7 | things suggested for it were implemented. The list has not stopped growing... | |
8 | ||
9 | Another reason it is so long is that I have retained some items from the Exim 3 | |
10 | Wish List that never got implemented, but which seem reasonable possibilities | |
11 | for later addition to Exim 4. | |
12 | ||
13 | I have guessed at the amount of work involved, and categorized the items as | |
14 | Tiny, Small, Medium, Large, or Unknown. The guesses are not based on any | |
15 | detailed investigation, so must be taken as very rough. | |
16 | ||
17 | ||
18 | ------------------------------------------------------------------------------ | |
19 | ------------------------------------------------------------------------------ | |
20 | ----- Retained from the Exim 3 Wish List ------ | |
21 | ------------------------------------------------------------------------------ | |
22 | ------------------------------------------------------------------------------ | |
23 | ||
24 | (10) 13-Jul-98 M more flexibility for pipe returns | |
25 | Ben Smithurst | |
26 | ||
27 | The ability to specify more precisely what happens concerning the return code | |
28 | from the pipe and the presence/absence of STDOUT/STDERR is requested. The | |
29 | particular configuration that was requested was: | |
30 | ||
31 | > if the command exited EX_OK, *and* produced nothing on STDOUT or | |
32 | > STDERR, it succeeded... | |
33 | > if the command exited EX_TEMPFAIL, defer, regardless of | |
34 | > STDOUT/STDERR... | |
35 | > otherwise freeze the message (this will get my attention by way of | |
36 | > freeze_tell_mailmaster)... | |
37 | ------------------------------------------------------------------------------ | |
38 | ||
39 | (11) 17-Jul-98 G support for DSN | |
40 | Andy Mell | |
41 | ||
42 | It is unclear to me how this should work in the presence of aliases and | |
43 | forwarding. Local deliveries would have to explicitly configured as deliveries | |
44 | or relaying or whatever. A substantial amount of code is probably needed. | |
45 | ||
46 | Jeffrey Goldberg | |
47 | I have nothing to add except to say that for many of the reasons you've | |
48 | stated, I don't think that DSN is coherent enough to be worth the effort | |
49 | to implement. | |
50 | ||
51 | Another comment: | |
52 | ||
53 | I thought the RFC was pretty clear on this. In a nutshell, if the | |
54 | delivery rewrites the envelope from address, it's considered a | |
55 | terminal delivery (i.e. delivery to a mailing list exploder), otherwise | |
56 | treat it as a forwarding operation (the /etc/aliases case). I would | |
57 | treat a .forward expansion as a final delivery event (it got to the | |
58 | user as far as the MTA is concerned). | |
59 | ||
60 | Yes, we need the DSN syntax. We also require the complete semantics of | |
61 | NOTIFY=SUCCESS,FAILURE for our application to work. | |
62 | ||
63 | Electronic Bill Presentment is really going to push the need for | |
64 | DSN support in MTAs. We just don't want to get stuck in a situation | |
65 | where we're faced with a non-DSN-aware MTA when we go to install | |
66 | our bill/statement engine, thus our interest in what the MTA vendors | |
67 | are planning to do about DSN. | |
68 | ------------------------------------------------------------------------------ | |
69 | ||
70 | (41) 14-Oct-98 M Find a way of modifying header lines | |
71 | Oliver Smith | |
72 | ||
73 | The problem with header_remove followed by header_add is that you can't refer | |
74 | to the previous value of the header when adding a replacement. This could be | |
4990831e | 75 | solved with a replace_header option. See also Exim 4/333. |
e05f33e0 PH |
76 | ------------------------------------------------------------------------------ |
77 | ||
78 | (43) 15-Oct-98 M Sender rewrite *after* SMTP incoming checks | |
79 | Andreas Edler | |
80 | ||
81 | The anti-relaying check happens after the sender has been rewritten; there are | |
82 | times when it would be helpful to do the check on the original sender, not on | |
83 | the rewritten one. Quite how to configure this I'm not sure. | |
84 | ||
85 | A related suggestion (from Steve Sargent) is to retain the original sender | |
86 | address and make it accessible somehow. | |
87 | ------------------------------------------------------------------------------ | |
88 | ||
89 | (46) 20-Oct-98 L SMTP protocol hooks | |
90 | Malcolm Ray | |
91 | ||
92 | "But there are enough broken SMTP implementations to make me wonder whether | |
93 | there isn't a case for providing hooks for tweaking the SMTP transport's | |
94 | protocol exchange. Something which would allow me to say things like 'if, when | |
95 | talking to lame.example.com, you get a 251 response to a MAIL command, rewrite | |
96 | the response to 501 before continuing'." | |
97 | ------------------------------------------------------------------------------ | |
98 | ||
99 | (50) 13-Nov-98 M A "Focus" option for eximon | |
100 | Frank Elsner | |
101 | ||
102 | This is the opposite of "Hide"; it just displays a certain subset. Hmm. Could | |
103 | something clever be done with regular expressions? | |
104 | ------------------------------------------------------------------------------ | |
105 | ||
106 | (61) 22-Dec-98 M Send failed error messages to somebody | |
107 | Harald Meland | |
108 | ||
109 | With sendmail, the failed error message is made into a error message, | |
110 | with both envelope sender and recipient set to MAILER-DAEMON. The | |
111 | original, bogus-envelope-sender message is then available to whoever | |
112 | receives MAILER-DAEMON's mail. A more flexible approach would be to | |
113 | specify a specific recipient. | |
114 | ------------------------------------------------------------------------------ | |
115 | ||
116 | (81) 01-Mar-99 M Addition of Content-MD5 support | |
117 | Martin Hamilton | |
118 | ||
119 | Martin supplied a suggested patch at | |
120 | http://www.net.lut.ac.uk/~martin/antispam/exim-hacks/ | |
121 | ------------------------------------------------------------------------------ | |
122 | ||
123 | (85) 15-Mar-99 M ability to rewrite addresses in non-standard headers | |
124 | Dave Lewney | |
125 | John Holman | |
126 | ||
4990831e | 127 | Such as "return-receipt-to". See also 41. See also Exim 4/333. |
e05f33e0 PH |
128 | ------------------------------------------------------------------------------ |
129 | ||
130 | (90) 21-Apr-99 M change wild prefix/suffix greediness | |
131 | Ben Smithurst | |
132 | ||
133 | Currently, when prefix or suffix containing * is set on a director, and the | |
134 | fixed part occurs more than once in a local part, the length of the prefix or | |
135 | suffix is maximized. For example, with suffix = -* and a local part of | |
136 | foo-bar-baz the suffix is taken as bar-baz, leaving the local part as foo. | |
137 | An option is proposed to invert this rule. | |
138 | ------------------------------------------------------------------------------ | |
139 | ||
140 | (91) 26-Apr-99 S make queue_run_in_order to newest first | |
141 | "Andreas M. Kirchwitz" | |
142 | ||
143 | The tidiest thing would be to have queue_run_order={random,oldest,newest}, | |
144 | and make queue_run_in_order obsolete. | |
145 | ------------------------------------------------------------------------------ | |
146 | ||
147 | (93) 04-May-1999 L fallback_transport | |
148 | ||
149 | This would be a generic transport option, specifying a different transport to | |
150 | be used if the first one failed. Failed hard, or failed soft? Or an option? | |
151 | And if failed hard, is a bounce message sent as well, or not? There are uid | |
152 | issues. Remote delivery would have to be done always in a subprocess so that | |
153 | the main process could retain privilege in case the fallback transport was | |
154 | local. That could be conditional. That's why this is labelled "Large". Some of | |
155 | the things people want to do with this can be done by variations in the | |
156 | routers, e.g. use $message_age to switch routers. | |
157 | ------------------------------------------------------------------------------ | |
158 | ||
159 | (94) 13-May-1999 M message to go with -Mg | |
160 | Dave Holland | |
161 | Alan Thew | |
162 | ||
163 | So the admin can pass back a reason. | |
164 | ------------------------------------------------------------------------------ | |
165 | ||
166 | (99) 28-May-1999 M header to list failures for syntax_errors_to | |
167 | mark david mcCreary | |
168 | ||
169 | "I use the syntax_errors_to feature to email a copy of the error message. | |
170 | It would be helpful to have the X-Failed-Receipients header in there, | |
171 | identifying which addreses(s) are the problem, so that I don't have to | |
172 | parse the body of the email message to figure out which addresses." | |
173 | ------------------------------------------------------------------------------ | |
174 | ||
175 | (100) 04-Jun-1999 S admin_users option, like trusted_users | |
176 | Paul Mansfield | |
177 | ------------------------------------------------------------------------------ | |
178 | ||
179 | (102) 21-Jun-1999 M expanded basic variables | |
180 | Julian King | |
181 | ||
182 | Oh, and a wishlist entry, qualify_domain, and preferably other variables | |
183 | can be set with a $lookup in the first part of the exim configuration | |
184 | file, perhaps by an equivalent to backticks in shell script ("`command`")? | |
185 | ------------------------------------------------------------------------------ | |
186 | ||
187 | (105) 28-Jun-1999 M MIME-format bounce messages | |
188 | Paul Makepeace | |
189 | ||
190 | "Is there any work going/gone on/planned to enable exim to report delivery | |
191 | status notifications using RFC1892 multipart/report MIME messages? It would be | |
192 | great to have errors reported in a message/rfc822 attachment." | |
193 | ||
194 | Jeffrey Goldberg | |
195 | "I like plain bounces, so would hope that if you do this, that it be | |
196 | configurable. I think that even for those who want it, it shouldn't be very | |
197 | high on the wish list priority." | |
198 | ||
199 | Other suggestions: toggle for bounces/warnings; override max_return for | |
200 | certain addresses; use plain text if original not MIME. See Paul's hack | |
201 | for background of what to do. | |
202 | ||
203 | Nigel suggests using a specially named autoreply transport to generate bounces; | |
204 | people could then replace this with another transport (e.g. pipe) if they want | |
205 | to customize it themselves. | |
206 | ||
207 | Eli Chen posted an unconditional patch for 3.32 that does some of this work. | |
208 | That could form a basis. | |
209 | ------------------------------------------------------------------------------ | |
210 | ||
211 | (107) 12-Jul-1999 S defer transport at given load level | |
212 | Marc Haber | |
213 | ||
214 | ------------------------------------------------------------------------------ | |
215 | ||
216 | (108) 16-Jul-1999 S remote sort by numbers of recipients | |
217 | mark david mcCreary | |
218 | ||
219 | In the absence of remote_sort, sort remote domains by the number of recipients | |
220 | in each. | |
221 | ------------------------------------------------------------------------------ | |
222 | ||
223 | (114) 11-Nov-1999 S List of possible outgoing interfaces | |
224 | ||
225 | Allow the smtp "interface" option to be a list: try them in turn until one | |
226 | is found to work. Also allow masks to specify a range of addresses. | |
227 | ------------------------------------------------------------------------------ | |
228 | ||
229 | (123) 23-Dec-1999 L Use AUTH + TURN for dial-in hosts | |
230 | Andrew Tverdokhleb | |
231 | ||
232 | The way to do this would be to have Exim deliver messages into per-host | |
233 | directories in, say, BSMTP format. Accept TURN if authenticated, and cause it | |
234 | to run a helper program that is passed the socket in order to deliver the mail. | |
235 | Provide a helper program! | |
236 | ------------------------------------------------------------------------------ | |
237 | ||
238 | (125) 04-Jan-2000 L Use shared memory segment for queue list | |
239 | Theo Schlossnagle | |
240 | ||
241 | The idea is that a queue-runner that finds no existing shared segment should | |
242 | create one (if configured - possibly some fixed size) and all Exim processes | |
243 | should maintain a list of messages in it, thereby saving on directory scans | |
244 | when there are lots of messages. This needs a lot of careful thought to try to | |
245 | eliminate any possibility of data loss. The interlocking could be quite tricky. | |
246 | Further posters suggested using a db file to hold the list. See also 127. | |
247 | ------------------------------------------------------------------------------ | |
248 | ||
249 | (129) 14-Jan-2000 L Dynamically loadable lookup modules | |
250 | Steve Haslam | |
251 | ||
252 | Suggested patch provided. | |
253 | ------------------------------------------------------------------------------ | |
254 | ||
255 | (131) 17-Jan-2000 T Facility for assuming existence for EACCES | |
256 | Peter Radcliffe | |
257 | ||
258 | The opposite option for "+" in require_files: assume existence if cannot | |
259 | peer into the directory (+ assumes non-existence). | |
260 | ------------------------------------------------------------------------------ | |
261 | ||
262 | (131) 29-Feb-2000 M? Control total number of outgoing SMTP calls | |
263 | Brian White | |
264 | ||
265 | This is for hosts with slow connections. Could some modification of | |
266 | serialize_hosts be used for this? Or maybe use a semaphore? They seem to | |
267 | be quite widely available. | |
268 | ------------------------------------------------------------------------------ | |
269 | ||
270 | (132) 01-Mar-2000 S Lookup host name from outgoing interface | |
271 | Vadim Vygonets | |
272 | ||
273 | Instead of primary_hostname, look up the name for the interface that is being | |
274 | used for sending. Suggested patch supplied, but this should be an option of the | |
275 | smtp transport. | |
276 | ------------------------------------------------------------------------------ | |
277 | ||
278 | (133) 06-Mar-2000 S Filter option not to log "previously sent" | |
279 | Bruce Bowler | |
280 | ||
281 | This is when using the "log" option of the autoreply driver. | |
282 | ------------------------------------------------------------------------------ | |
283 | ||
284 | (134) 09-Mar-2000 S Option to remove attachments when bouncing | |
285 | ------------------------------------------------------------------------------ | |
286 | ||
287 | (136) 13-Mar-2000 S/M Option for aliasfile to suppress "me too" | |
288 | ||
289 | Could be tricky determining who "me" is. | |
290 | ------------------------------------------------------------------------------ | |
291 | ||
292 | (143) 08-May-2000 S Make quota_warn_threshold into a list | |
293 | David Carter | |
294 | ||
295 | So several warnings could be generated as the mailbox got bigger and bigger. | |
296 | ------------------------------------------------------------------------------ | |
297 | ||
298 | (146) 15-May-2000 M Allow SMTP error codes in retry rules | |
299 | ||
300 | This would allow special handling of certain errors from certain hosts. In | |
301 | particular, it would allow failing of certain 4xx codes. | |
302 | ||
303 | This is now available for 4xx responses to RCPT commands. Is anything more | |
75faf241 PH |
304 | needed? Apparently, yes; there's been a request for a similar feature for MAIL |
305 | commands. | |
e05f33e0 PH |
306 | ------------------------------------------------------------------------------ |
307 | ||
308 | (148) 15-May-2000 S Warn recipient if message rejected for quota excession. | |
309 | Heinz Ekker | |
310 | ||
311 | Maybe not all that small, because the possibility of retrying must be taken | |
312 | into account. | |
313 | ------------------------------------------------------------------------------ | |
314 | ||
315 | (149) 19-May-2000 L Make added headers visible in filters and other places | |
316 | Hans Morten Kind | |
317 | ||
318 | Headers added by directors/routers are not visible in subsequent processing. | |
319 | This is a request to make them visible. What about removed headers? This could | |
320 | be tricky to specify, hence the L. | |
321 | ||
322 | A separate but related issue is the effect of headers added by "unseen" | |
323 | directors. These are documented in chapter 19 as not being accumulated. Should | |
4990831e | 324 | any change be made? See also Exim 4/333. |
e05f33e0 PH |
325 | ------------------------------------------------------------------------------ |
326 | ||
327 | (155) 16-Jun-2000 M Special handling for certain hosts | |
328 | mark david mcCreary | |
329 | ||
330 | A means of changing the transport depending on the host name/IP of the most | |
331 | preferred MX record so that all domains that route to certain hosts can be | |
332 | handled specially. Maybe this could be a variable that is available in the | |
333 | expansion of the "transport" option. | |
334 | ------------------------------------------------------------------------------ | |
335 | ||
336 | (158) 29-Jun-2000 S Configure "From" in bounces | |
337 | Ben Parker | |
338 | ||
339 | Cf Reply-To. | |
340 | ------------------------------------------------------------------------------ | |
341 | ||
342 | (159) 07-Jul-2000 M Keep messages for fixed time | |
343 | Gary Palmer | |
344 | ||
345 | An option to keep messages on the queue for a specified time, even if all their | |
346 | destination hosts have timed out. | |
347 | ------------------------------------------------------------------------------ | |
348 | ||
349 | (164) 17-Aug-2000 S sender_unqualified_auth_hosts | |
350 | ||
351 | To allow authenticated hosts to send unqualified addresses. Presumably it | |
352 | needs received_... as well. | |
353 | ------------------------------------------------------------------------------ | |
354 | ||
355 | (167) 05-Sep-2000 L Support for ODBC | |
356 | ||
357 | This would allow access to databases that don't have native support built into | |
358 | Exim. See http://www.openlinksw.com/info/docs/rel3doc/unix/odbcsdk.htm | |
359 | ------------------------------------------------------------------------------ | |
360 | ||
361 | (168) 06-Sep-2000 M Deliver messages that alias to nothing to a given address | |
362 | Dr ZP Han | |
363 | ||
364 | If other people are managing alias lists, and one is empty, bounce that | |
365 | delivery to a given address rather than freezing the message. Use the errors_to | |
366 | address? | |
367 | ------------------------------------------------------------------------------ | |
368 | ||
e05f33e0 PH |
369 | (173) 18-Sep-2000 S A way of doing lsearches with EOL terminated keys |
370 | Jason Robertson | |
371 | ||
372 | This is for looking up things like subject contents. Probably need an option to | |
373 | exim_dbmbuild to make them into DBM files. | |
374 | ------------------------------------------------------------------------------ | |
375 | ||
e05f33e0 PH |
376 | (181) 10-Nov-2000 S Compile-time options for ignoring Sendmail options |
377 | ||
378 | So that new ones could be accommodated easily. | |
379 | ------------------------------------------------------------------------------ | |
380 | ||
381 | (183) 04-Dec-2000 L dns_means_nonexist_after | |
382 | Dave C. | |
383 | ||
384 | In other words, wait a bit before giving up. This needs a mechanism for | |
385 | remembering, which is not currently available. To be borne in mind for the | |
386 | future. | |
387 | ------------------------------------------------------------------------------ | |
388 | ||
389 | (184) 04-Dec-2000 M Log more details of local caller | |
390 | J. Nick Koston | |
391 | ||
392 | "I was wondering if it was possible for exim to log the parent pid's cwd and | |
393 | exe when it is called from a script/invoked by actually running /usr/sbin/exim | |
394 | or /usr/sbin/sendmail." Question: is this information actually/easily | |
395 | available to Exim? Needs investigation. | |
396 | ------------------------------------------------------------------------------ | |
397 | ||
398 | (186) 19-Dec-2000 S A simple utility to reset a retry time | |
399 | Marc Haber | |
400 | ||
401 | Basically, to do what exim_fixdb "delete" can do, but straightforwardly. There | |
402 | could be an interface from eximon. | |
403 | ------------------------------------------------------------------------------ | |
404 | ||
405 | (187) 02-Jan-2001 M Wildcarding in headers_remove | |
406 | Tamas TEVESZ | |
407 | ||
408 | What I'd like to see is it to handle globs (or regexps, but i'm not sure this | |
409 | latter would worth the hassle), in a way like: | |
410 | ||
411 | headers_remove = "X-*:Additional-header" | |
412 | ------------------------------------------------------------------------------ | |
413 | ||
e05f33e0 PH |
414 | (190) 03-Jan-2001 M Multiple message operations in eximon |
415 | ------------------------------------------------------------------------------ | |
416 | ||
417 | (195) 19-Mar-2001 T TCP window size | |
418 | ||
419 | TCP window size for receiving/sending, SMTP client/server. | |
420 | ------------------------------------------------------------------------------ | |
421 | ------------------------------------------------------------------------------ | |
422 | ||
423 | ||
424 | ||
425 | ------------------------------------------------------------------------------ | |
426 | ------------------------------------------------------------------------------ | |
427 | ----- Things that didn't make it into Exim 4 ------ | |
428 | ------------------------------------------------------------------------------ | |
429 | ------------------------------------------------------------------------------ | |
430 | ||
431 | . An option to send messages to postmaster when ignore_errmsg_errors_after | |
432 | times out. | |
433 | ||
434 | . When an address is being routed, its constituents are in $local_part and | |
435 | $domain, but there is currently no variable that contains the whole thing. It | |
436 | could be put into $recipient, but that risks confusion with $recipients | |
437 | (which is available in system filters). Maybe $address could be used? | |
438 | ||
439 | . The ability to relay to host X without knowing all the domains that host X | |
440 | might have. At ACL time, one would need to verify the recipient, and determine | |
441 | that it routed to host X. | |
442 | ||
e05f33e0 PH |
443 | . People want to change the wording of messages; can we find an efficient way |
444 | of allowing this? (Maybe put all messages into a separate module?) The problem | |
445 | is not in the messages themselves, but in the values that get inserted into | |
446 | messages. Would have to invent a new kind of function that used identified | |
447 | values rather than positional ones. Use GNU gettext? | |
448 | ||
449 | . Invent lf_hosts for those that may use LF without CR. Any other RFC | |
450 | things we need to worry about? | |
451 | ||
452 | . A user would really like to see something similar, perhaps with | |
453 | "ID=$authenticated_id", similar to "helo=" and "ident=" in the default received | |
454 | header. BUT there are security issues. Maybe give it as a commented out option | |
455 | in the default configuration? | |
456 | ||
457 | . Consider expanding further options that take integer values. What about | |
458 | smtp_xxx options for different limits at different times of day (for example)? | |
459 | What about tls_advertise_hosts (so can look at incoming IP/port)? | |
460 | ||
461 | . How about a "hold hosts" option (cf hold_domains) to hold delivery to certain | |
462 | hosts? | |
463 | ||
464 | . Allow user filters to use "headers add", but probably not remove. Or maybe | |
465 | just implement "allow" options for both of these features. | |
466 | ||
467 | . Have the return from pipe in a variable, so that (e.g. error_message_file) | |
468 | can make use of it. | |
469 | ||
470 | . Implement randomize for ldap/sql servers. | |
471 | ||
472 | . Add an option for ETRN that says "wait for the command to finish, and use its | |
78d6ddf8 PH |
473 | stdout as the SMTP response." // A serialized ETRN now does the waiting, but |
474 | there is as yet no way to use the status. // | |
e05f33e0 PH |
475 | |
476 | . -odsomething for "ignore retry when doing immediate delivery". | |
477 | ||
478 | . Add an option to the smtp transport to make it treat 5xx on connection as if | |
479 | it were 4xx. Or possible add a sophisticated "after command X, treat xxx as | |
480 | yyy". | |
481 | ||
e05f33e0 PH |
482 | . Global option to enable initgroups() for exim uid. Default off. |
483 | ||
484 | . When verifying a sender, should it be rewritten with any T rewrites, because | |
485 | it would be so rewritten if it actually was a recipient in a message? | |
486 | ||
487 | . Sean Witham wants a way of defining macros that are not privileged, and a | |
488 | sort of #ifdef structure that allows for different configurations in the same | |
489 | file. | |
490 | ||
491 | . Allow :fail: to specify that 551 be used instead of 550. Maybe allow a code | |
492 | at the start, optionally? What about :defer:? | |
493 | ||
494 | . SMTP timeout in middle of receiving message: log sender address if known, and | |
495 | possibly message_id if known. | |
496 | ||
497 | . Make -brw show rewrites for transports too. | |
498 | ||
499 | . Have the MTA log destinations that have timed-out on a ident request and | |
500 | no longer send rfc1413_queries to them. Add an option for how not to cache | |
501 | these entries. | |
502 | ||
503 | . Options and/or a utility to enable non-privileged users to view the queue | |
504 | (e.g. -bpp), manipulate their own messages, etc. | |
505 | ||
e05f33e0 PH |
506 | . A generalized "From" escaping scheme that also escapes >From so that the |
507 | whole thing can be reversed. | |
508 | ||
509 | . There was a request for the \dns_again_means_nonexist\ option not to be | |
510 | instantaneous, but to operate only after the DNS has been giving "try again" | |
511 | for some time. Use the misc hints database. | |
512 | ||
513 | ||
514 | ||
515 | ------------------------------------------------------------------------------ | |
516 | ------------------------------------------------------------------------------ | |
517 | ----- The Exim 4 Wish List ------ | |
518 | ------------------------------------------------------------------------------ | |
519 | ------------------------------------------------------------------------------ | |
520 | ||
521 | (1) 01-Jan-02 U Use of dynamically loaded libraries. | |
522 | ||
523 | People want Exim to use dynamically loaded modules for a variety of reasons. | |
524 | When I started to create Exim, I never expected anything other than source | |
525 | distribution; the RPMs and inclusions in OS distributions caught me by | |
526 | surprise. I know very little about the mechanics of dynamic loading, but I'm | |
527 | aware that not all operating systems support it. I'm also aware that not all | |
528 | people support it! | |
529 | ||
530 | Furthermore, a way round this might be to supply more hooks along the lines of | |
531 | local_scan(). Then people can write their own dynamic loaders if they want. | |
532 | ------------------------------------------------------------------------------ | |
533 | ||
534 | (3) 01-Jan-02 U Test for over-quota at SMTP time | |
535 | ||
536 | This is a hard one, because the only way to test for over quota is to try to | |
537 | deliver a message, certainly if system quotas are being used. And also, the | |
538 | only available size at RCPT time is the SIZE option, though of course the test | |
539 | could be run at DATA time. I think maybe we leave this one to an external | |
540 | program, and require people to use ${run} to access the data. Let someone else | |
541 | figure out how to extract the current mailbox size! | |
542 | ||
543 | One suggestion is to implement | |
544 | ||
545 | ${file_size:/path/to/file} | |
546 | ${directory_size:/path/to/directory} | |
547 | ||
548 | so that explicit checks can be done. It may be necessary to have four | |
549 | operators, two being based on the block count, and two showing the "visible" | |
550 | size. Directory scanning is expensive; is there any scope for caching? It would | |
551 | seem not (you don't often get two addresses to the same user). | |
552 | ------------------------------------------------------------------------------ | |
553 | ||
e05f33e0 PH |
554 | (6) 01-Jan-02 S Option to disable the use of -t |
555 | Dave C. | |
556 | ||
557 | Would require work so that Exim itself doesn't use -t. | |
558 | ------------------------------------------------------------------------------ | |
559 | ||
560 | (7) 01-Jan-02 M Avoid showing LDAP passwords in log lines for LDAP errors | |
561 | John W Baxter | |
562 | ||
563 | May be tricky, because at the higher levels, the format of the query is not | |
78d6ddf8 PH |
564 | understood. // There is now a fudge that works in some cases. See ChangeLog |
565 | 4.51/PH/10. // | |
e05f33e0 PH |
566 | ------------------------------------------------------------------------------ |
567 | ||
e05f33e0 PH |
568 | (9) 01-Jan-02 S Headers as well as body in file for autoreply |
569 | Florian Laws | |
570 | ------------------------------------------------------------------------------ | |
571 | ||
572 | (10) 01-Jan-02 T Make "true" and "false" valid expansion conditions | |
573 | ||
574 | This might help with "and" and "or" when one of the sub-conditions is, for | |
575 | example, a lookup. | |
576 | ------------------------------------------------------------------------------ | |
577 | ||
578 | (11) 01-Jan-02 S Allow a filter to include another file. | |
579 | ------------------------------------------------------------------------------ | |
580 | ||
581 | (12) 01-Jan-02 M Support for different SQL servers per query | |
582 | ||
583 | In other words, the global mysql_servers etc. is too restrictive. | |
584 | ------------------------------------------------------------------------------ | |
585 | ||
586 | (14) 01-Jan-02 M? Support for Sendmail milters | |
587 | ||
588 | This could perhaps be done by extending the local_scan() idea and providing a | |
589 | "standard" module which interfaced to milter. | |
590 | ------------------------------------------------------------------------------ | |
591 | ||
592 | (15) 01-Jan-02 M More hooks like local_scan() | |
593 | ||
594 | One request has been for a similar hook at logging time. For other SMTP | |
0cf417c5 | 595 | interactions, maybe a hook into the ACL? See also 79 and 218 and 301. |
e05f33e0 PH |
596 | ------------------------------------------------------------------------------ |
597 | ||
598 | (17) 11-Jan-02 M The construction of config.h needs refactoring | |
599 | ||
600 | This has been hacked about substantially since the original implementation. | |
601 | Given that there is a program (buildconfig), the messing around with the | |
602 | environment could be abolished. Also, the distinction between "yes" and "no" | |
603 | isn't always properly made (tests for #ifdef don't care about the value). | |
604 | ------------------------------------------------------------------------------ | |
605 | ||
606 | (18) 24-Jan-02 S Make $value retain its value after a top-level expansion | |
607 | ||
608 | This was specifically for use in filter files. Currently it reverts to empty | |
609 | as a consequence of save/restore for every lookup. It might be confusing to | |
610 | do otherwise, however. | |
611 | ------------------------------------------------------------------------------ | |
612 | ||
613 | (19) 29-Jan-02 L Use of multiple DBM libraries | |
614 | ||
615 | The problem is how to handle conflicting function names. Much research is | |
616 | needed. | |
617 | ------------------------------------------------------------------------------ | |
618 | ||
619 | (20) 29-Jan-02 S Make system filter refreeze after manual thaw | |
620 | ||
621 | Currently, a "freeze" in a system filter doesn't freeze after a manual thaw. | |
622 | ------------------------------------------------------------------------------ | |
623 | ||
624 | (21) 12-Feb-02 S Expand return_size_limit | |
625 | Joachim Wieland | |
626 | ||
627 | Is this really worth it? A per-transport value is also suggested - that would | |
628 | mean remembering the value with each failed address and taking a minimum or | |
629 | a maximimum (which?). | |
630 | ------------------------------------------------------------------------------ | |
631 | ||
632 | (24) 21-Feb-02 ? A way of testing TLS using -bh | |
633 | ------------------------------------------------------------------------------ | |
634 | ||
635 | (27) 06-Mar-02 M Distinguishing between different temporary callout errors | |
636 | ||
637 | The request was to distinguish between a 4xx error and a failure to connect. | |
638 | Problem is: how to cope when there is more than one host? Maybe only if ALL | |
639 | fail to connect. An option like /callout_no_connect_ok. | |
640 | ------------------------------------------------------------------------------ | |
641 | ||
642 | (30) 12-Mar-02 S Add "recipients" precondition to routers. | |
643 | ||
644 | This would avoid having to use "condition". (See also requirement for $address | |
645 | mentioned above.) However, it would also require adding a caching feature, and | |
646 | probably $recipient_data (cf $domain_data). | |
647 | ------------------------------------------------------------------------------ | |
648 | ||
649 | (31) 21-Mar-02 S Variables that indicate 8-bit message and 8-bit host, and | |
650 | a way of using them to suppress a transport filter | |
651 | ||
652 | A variable that is set if the message contains 8-bit characters, and another | |
653 | that is set during the smtp transport if the host supports 8-bit. Then we also | |
654 | need a condition that's expanded in the transport to control whether the filter | |
655 | is run or not (e.g. transport_filter_condition). | |
656 | ------------------------------------------------------------------------------ | |
657 | ||
658 | (32) 22-Mar-02 M More info about callout fails for header sender verify | |
659 | ||
660 | When there's a callout failure for an envelope address, the error message | |
661 | contains details (by default) of the callout commands. This doesn't happen | |
662 | for addresses in the header because there may be more than one of them, and | |
663 | deciding how to give that information is tricky. Can we do better? | |
664 | ------------------------------------------------------------------------------ | |
665 | ||
666 | (33) 25-Mar-02 S Option to assume nomatch in dnslist lookups that time out | |
667 | ||
668 | Currently this causes a DEFER. | |
669 | ------------------------------------------------------------------------------ | |
670 | ||
671 | (34) 26-Mar-02 S Access to DNS lookup functions via local_scan() API | |
672 | ||
673 | This would make local_scan() writers lives easier for DNS usage. | |
674 | ------------------------------------------------------------------------------ | |
675 | ||
676 | (36) 02-Apr-02 ? A way of throttling, but allowing, relaying that would | |
677 | otherwise be denied | |
678 | ||
679 | This was suggested in connection with anonymizing messages. The "wait" command | |
680 | in ACLs goes some way towards this. Is it enough? | |
681 | ------------------------------------------------------------------------------ | |
682 | ||
683 | (41) 17-Apr-02 T Make config.samples available as a directory for ftp | |
684 | ||
685 | This is so that people can browse individual samples directly. | |
686 | ------------------------------------------------------------------------------ | |
687 | ||
688 | (42) 23-Apr-02 T An option not to flatten newlines in $message_body. | |
689 | ||
690 | Or maybe better to provide $message_body_nl so as to have both. | |
691 | ------------------------------------------------------------------------------ | |
692 | ||
693 | (43) 23-Apr-02 T An option to treat 4xx as 5xx from STARTTLS | |
694 | ||
695 | This would make Exim retry in clear unless the host is in hosts_require_tls. | |
696 | ------------------------------------------------------------------------------ | |
697 | ||
698 | (44) 24-Apr-02 ? Use errors_to for timeouts after redirect syntax errors | |
699 | ||
700 | A syntax error in redirection data (with skip_syntax_errors false) causes a | |
701 | defer. Eventually, the address may time out. This suggestion is that, when it | |
702 | does, the bounce is sent to errors_to rather than to the sender. | |
703 | ------------------------------------------------------------------------------ | |
704 | ||
705 | (45) 13-May-02 T smtp_etrn_serialize_id = .... | |
706 | ||
707 | The default behaviour would be equivalent to | |
708 | ||
709 | smtp_etrn_serialize_id = $smtp_command_argument | |
710 | ------------------------------------------------------------------------------ | |
711 | ||
712 | (47) 16-May-02 S Access to all addresses in batched local delivery | |
713 | Miquel van Smoorenburg | |
714 | ||
715 | In a batched local delivery with more than one recipient, there's no way to | |
716 | access the list of recipients for doing custom things, such as stuffing them | |
717 | all into a header. (BSMTP is the only approach; not everybody can use it.) | |
718 | Suggested patch supplied. | |
719 | ------------------------------------------------------------------------------ | |
720 | ||
721 | (48) 21-May-02 M Support for ATRN (server and client) | |
722 | Brian Candler | |
723 | ||
724 | Server: If Exim had the ability to accept an ATRN command and then simply | |
725 | invoke an external program, passing the SMTP stream on stdin and stdout and | |
726 | the authenticated id as a parameter, that would do the job nicely. | |
727 | ||
728 | Client: We need a variant of 'exim -bs' which would connect to a specified | |
729 | host, send AUTH/ATRN, and then accept incoming messages as usual. | |
730 | ------------------------------------------------------------------------------ | |
731 | ||
fc9c2317 | 732 | (50) 22-May-02 S? Add comment (duplicate address) to Envelope-To: |
e05f33e0 | 733 | |
fc9c2317 PH |
734 | This is just to minimize the confusion some people have. However, it is not |
735 | trivially easy to decide which to label as duplicates because of complications | |
736 | with redirection. I'm not convinced it will actually reduce confusion. | |
e05f33e0 PH |
737 | ------------------------------------------------------------------------------ |
738 | ||
739 | (51) 07-Jun-02 S Option to use another address in callout MAIL FROM | |
740 | ||
741 | This would be an address to try if MAIL FROM:<> failed. Is this actually going | |
742 | to be helpful? See also 101. | |
743 | ------------------------------------------------------------------------------ | |
744 | ||
745 | (53) 11-Jun-02 S Make local_scan() dynamically loadable | |
746 | ||
747 | David Woodhouse sent a patch. There's a more sophisticated one from Marc | |
748 | Merlin. (See also Peter Benie's comments.) But should the base Exim have all | |
749 | this in it? | |
750 | ------------------------------------------------------------------------------ | |
751 | ||
752 | (54) 11-Jun-02 S Ignore -Ac if called as mailq | |
753 | ||
754 | I am not sure if this makes sense. This flag requests a listing of a different | |
755 | mail queue, but Exim doesn't work like that. Is is not better for people to be | |
756 | aware of this? | |
757 | ------------------------------------------------------------------------------ | |
758 | ||
759 | (55) 13-Jun-02 M Rewriting whole header lines | |
760 | Dave C. | |
761 | ||
762 | Current rewriting rules apply to individual addresses in header lines. This | |
763 | feature would use a regex to match whole lines and replace them. It could be | |
764 | useful for patching up syntactically invalid lines from crappy clients, before | |
765 | the syntax check kicks in. (It might also be useful for hiding local host names | |
4990831e | 766 | in Received: headers.) See also 333. |
e05f33e0 PH |
767 | ------------------------------------------------------------------------------ |
768 | ||
769 | (58) 26-Jun-02 ? Extend PAM support | |
770 | ||
771 | Apparently PAM can do challenge-response authentication. The Exim interface | |
772 | can't handle this. Investigate and think about how to do this. | |
773 | ------------------------------------------------------------------------------ | |
774 | ||
775 | (59) 26-Jun-02 M A "custom" authenticator | |
776 | ||
777 | ... that is simply a front end to external code. For example, there may be | |
778 | an external API that hides the user password and does CRAM-MD5 when passed the | |
779 | details of the challenge and response. | |
780 | ------------------------------------------------------------------------------ | |
781 | ||
782 | (60) 27-Jun-02 S Make trusted_users a local part list | |
783 | ||
784 | So that it can use lsearch etc. | |
785 | ------------------------------------------------------------------------------ | |
786 | ||
787 | (62) 28-Jun-02 S Remove headers before DATA ACL | |
788 | Patrice Fournier | |
789 | ||
790 | "I'd like to be able to give Exim a list of headers that must be removed | |
791 | from the message at arrival, before data_acl processing (and before the | |
4990831e | 792 | rcpt_acl warn headers are added to the message)." See also 333. |
e05f33e0 PH |
793 | ------------------------------------------------------------------------------ |
794 | ||
795 | (63) 28-Jun-02 S Access to ACL-added headers in ACLs | |
796 | Patrice Fournier | |
797 | ||
798 | "I'd like also to be able to look at the already added headers by a | |
799 | rcpt_acl when still checking rcpt_acl (either later in the acl for the same | |
4990831e | 800 | RCPT TO or for another RCPT TO)." See also 333. |
e05f33e0 PH |
801 | ------------------------------------------------------------------------------ |
802 | ||
803 | (65) 28-Jun-02 M Expand fallback hosts | |
804 | ||
805 | See also 174 of the Exim 3 list. | |
806 | ------------------------------------------------------------------------------ | |
807 | ||
808 | (66) 01-Jul-02 M Use Berkeley DB 4 concurrent access features | |
809 | ||
810 | This might give better performance on very busy sites by reducing the | |
811 | contention for access to hints databases. Rob Butler points out that this could | |
812 | also be useful to allow updates of other DB files used by Exim to happen | |
813 | concurrently. Another thing to think about with BDB is the possible use of | |
814 | B-trees. | |
815 | ------------------------------------------------------------------------------ | |
816 | ||
817 | (68) 01-Jul-02 S Add sender host to delivery line | |
818 | ||
819 | "Would it be possible to have a "sending_host_on_delivery" option that | |
820 | logs the IP of the sending host in the => line?" Also requested was amount of | |
821 | data transmitted for a non-delivery attempt. | |
822 | ------------------------------------------------------------------------------ | |
823 | ||
824 | (69) 03-Jul-02 T Log selector to log whoson checs | |
825 | Matt Bernstein | |
826 | ||
827 | "I'd quite like a log_selector option which could spot you'd done a whoson | |
828 | lookup in your DATA ACL and maybe log it as W=user." | |
829 | ------------------------------------------------------------------------------ | |
830 | ||
831 | (70) 09-Jul-02 S A way of changing the RCPT address in an accept router | |
832 | ||
833 | So as to avoid duplication problems when sending multiple addresses in multiple | |
834 | copies to the same address. | |
835 | ------------------------------------------------------------------------------ | |
836 | ||
e05f33e0 PH |
837 | (74) 22-Jul-02 M Extend -bV to do more semantic checking |
838 | ||
839 | For example, diagnose "local_hosts" that should probably be "+local_hosts". | |
840 | ------------------------------------------------------------------------------ | |
841 | ||
842 | (75) 23-Jul-02 S Reference option on command line | |
843 | ||
844 | The idea here is that a spam scanner that re-injects a message can supply a | |
845 | reference on the command line that gets logged with R=. | |
846 | ------------------------------------------------------------------------------ | |
847 | ||
848 | (78) 30-Jul-02 S Expand queue_only (and/or queue_only_file) | |
849 | ||
850 | The requirement is to make it possible to queue messages if certain conditions | |
851 | are met (e.g. messages from certain local users). See also 93. | |
852 | ||
853 | This control can now be achieved in the ACL - is this still needed? | |
854 | ------------------------------------------------------------------------------ | |
855 | ||
856 | (79) 31-Jul-02 S Additional info for log lines | |
857 | ||
858 | An option to set an expanded string to be added to <= lines. And also for the | |
859 | other delivery lines? See also 15. | |
860 | ------------------------------------------------------------------------------ | |
861 | ||
862 | (84) 09-Aug-02 S Make interfaces available in a variable | |
863 | ||
864 | Something like $local_interfaces. Maybe limit the max length. | |
865 | ------------------------------------------------------------------------------ | |
866 | ||
867 | (85) 12-Aug-02 S/M Notice database connection failures | |
868 | ||
869 | The small version of this just removes a server from the list within a single | |
870 | Exim process when a connection to it fails. The bigger project would use the | |
871 | retry database - but that has implications for bottlenecking and may not be | |
872 | helpful. See also item 109. Another suggestion is to randomize the order in | |
873 | which database servers are tried (randomize_database_servers). And another is | |
874 | to measure response times and remember which server is fastest. | |
875 | ------------------------------------------------------------------------------ | |
876 | ||
877 | (87) 12-Aug-02 M Partial lookups for query-style lookups | |
878 | ||
879 | The suggestion is to allow the lookup to contain a keystring (same syntax as | |
880 | single-key lookups) which is then permuted and place in a suitable variable | |
881 | each time - $permuted_key or something. | |
882 | ------------------------------------------------------------------------------ | |
883 | ||
884 | (88) 20-Aug-02 S Allow special retrying for forced defer | |
885 | ||
886 | See also 146 in Exim 3 wish list above. | |
887 | ------------------------------------------------------------------------------ | |
888 | ||
889 | (89) 20-Aug-02 S Also allow retry rules on routers and transports | |
890 | ------------------------------------------------------------------------------ | |
891 | ||
892 | (90) 23-Aug-02 M Macros with arguments, a la C | |
893 | ||
894 | I don't like this, because of the cost of frequent interpretation. | |
895 | ------------------------------------------------------------------------------ | |
896 | ||
897 | (93) 27-Aug-02 S queue_only_condition | |
898 | Peter A. Savitch | |
899 | ||
900 | queue_only_condition global option, expanded string. This contain | |
901 | condition, which if evaluated to `no' or `false' or `0', behaves like | |
902 | queue_only (queue_only_load ?). Don't know what to do is the string | |
903 | expansion fails with DEFER (either force queueing or continue with | |
904 | immediate delivery). Another option can control Exim behaviour if the | |
905 | expansion fails. Don't know how the name for it ;-) See also 78. | |
906 | ||
907 | This control can now be achieved in the ACL - is the new feature now needed? | |
908 | ------------------------------------------------------------------------------ | |
909 | ||
910 | (95) 27-Aug-02 S Log all parents as a router option | |
911 | ||
912 | So that specific addresses can be logged like this. Should there be more log | |
913 | selector options per router? Per transport? | |
914 | ------------------------------------------------------------------------------ | |
915 | ||
916 | (99) 28-Aug-02 L Test pre-conditions in order given | |
917 | ||
918 | This would get round certain problems with require_files. However, it is | |
919 | totally incompatible, and therefore an "Exim 5" wish. | |
920 | ------------------------------------------------------------------------------ | |
921 | ||
922 | (101) 02-Oct-02 M Callout and <> rejections | |
923 | ||
924 | Some people don't want to fail the callout if the MAIL FROM:<> command is | |
925 | rejected. Think of a way of handling this tidily. See also 51. | |
926 | ------------------------------------------------------------------------------ | |
927 | ||
928 | (102) 03-Oct-02 M Log option to suppress message-id logging | |
929 | ||
930 | M because it would involve a change to eximstats. | |
931 | ------------------------------------------------------------------------------ | |
932 | ||
933 | (106) 09-Oct-02 S Appendfile to create directory not as user | |
934 | ||
935 | Arrange for the setup entry to appendfile to create the directory under some | |
936 | other uid (and with given owners/permissions?) | |
937 | ------------------------------------------------------------------------------ | |
938 | ||
939 | (109) 15-Oct-02 M Remember when LDAP (etc) servers are down | |
940 | ||
941 | The idea would be to use some kind of retry rule, just like for hosts. | |
942 | See also 85. | |
943 | ------------------------------------------------------------------------------ | |
944 | ||
945 | (110) 18-Oct-02 M errors_to for pipe command in filter | |
946 | ||
947 | To work in the same was as errors_to for deliver commands. | |
948 | ------------------------------------------------------------------------------ | |
949 | ||
950 | (113) 15-Nov-02 M support for XMLRPC | |
951 | ||
952 | Patch supplied for 4.10 by Joel Vandal. | |
953 | ------------------------------------------------------------------------------ | |
954 | ||
955 | (114) 04-Dec-02 M local_scan: return message on accept | |
956 | ||
957 | (This actually dates from earlier.) The problem with this is that the string | |
958 | currently passes into $local_scan_data. Thus, an incompatible change of some | |
959 | sort would be required. Possibly a global that local_scan can set? | |
960 | ------------------------------------------------------------------------------ | |
961 | ||
962 | (118) 10-Dec-02 S access to Perl from local_scan | |
963 | ------------------------------------------------------------------------------ | |
964 | ||
965 | (119) 12-Dec-02 M ability to specify additional headers in an autoreply | |
966 | ||
967 | This is so that vacation messages etc can have MIME headers that specify, for | |
968 | example, the character set. | |
969 | ------------------------------------------------------------------------------ | |
970 | ||
971 | (125) 02-Jan-03 M Per-host daemon logging | |
972 | ||
973 | "So what I would like is an option like debug_hosts, that allows to specify | |
974 | an hostlist, and if the current incoming/outgoing hosts matches, creates a | |
975 | logfile like $hostname_(in|out).log in my logdirectory." | |
976 | ------------------------------------------------------------------------------ | |
977 | ||
978 | (127) 06-Jan-03 M Different messages for different callout failures | |
979 | ||
980 | The real requirement here is to detect when a callout "MAIL FROM:<>" failed, so | |
981 | that a specific warning about that can be sent, different to the message when a | |
982 | callout "RCPT TO:" fails. I think this is in fact now mostly done. | |
983 | ------------------------------------------------------------------------------ | |
984 | ||
985 | (129) 09-Jan-03 M Keep track of DNSBL timeouts, and refrain from calling | |
986 | ||
987 | If so configured, keep track of DNSBL timeouts in a hints record, and don't | |
988 | retry that DNSBL for a while after (a sufficient number of) timeouts. It is | |
989 | effectively disabled for a while. Log enable/disable, of course. Another | |
990 | thought is an option not to apply +defer_unknown unless *all* DNSBL lookups in | |
991 | a list defer. | |
992 | ------------------------------------------------------------------------------ | |
993 | ||
994 | (130) 09-Jan-03 M A number of LDAP-related things | |
995 | Peter A. Savitch | |
996 | ||
997 | OpenLDAP 2.1 is going to be more popular (2.1.9 is available with many | |
998 | bug fixes). TLS-enabled LDAP is an interesting and usefull thing. | |
999 | I can try to implement some things and send the patches, like with | |
1000 | ldapi. | |
1001 | ||
1002 | How do You see: | |
1003 | ||
1004 | 1) The propagation of TLS options (key, certificate, CA certificate) | |
1005 | to the OpenLDAP library. | |
1006 | ||
1007 | 2) (was dereferencing; done in 4.23). | |
1008 | ------------------------------------------------------------------------------ | |
1009 | ||
1010 | (131) 09-Jan-03 S Additional variables | |
1011 | Peter A. Savitch | |
1012 | ||
1013 | $root_uid Why? | |
1014 | ||
1015 | (Some that were previously here are done) | |
1016 | ||
1017 | $smtp_accept_count -- used for acl_smtp_connect | |
1018 | ||
1019 | $queue_runners -- children of the listening daemon could use this | |
1020 | value for controlling the number of queue runners | |
1021 | ||
1022 | I don't like either of these because they cannot be real-time values. They | |
1023 | would be snapshots of the values at the time the process was forked from the | |
1024 | daemon, and I fear they would just be confusing. For processes that were not | |
1025 | forked from the daemon they couldn't be set at all. | |
1026 | ------------------------------------------------------------------------------ | |
1027 | ||
1028 | (131) 09-Jan-03 S Additional options | |
1029 | Peter A. Savitch | |
1030 | ||
1031 | exim_processes_max | |
1032 | exim_file_descriptors_max | |
1033 | queue_run_condition -- to deprecate queue_run_max, better system | |
1034 | load control | |
1035 | ||
1036 | Given Exim's distributed nature, I'm not at all sure how the first two of these | |
1037 | can usefully be implemented. | |
1038 | ------------------------------------------------------------------------------ | |
1039 | ||
1040 | (132) 16-Jan-03 M Option for when a transport filter fails (crashes) | |
1041 | ||
1042 | Freezing is one obvious option. Currently, Exim just retries. Another user | |
1043 | wanted to retry without the filter, but that is much harder. | |
1044 | ------------------------------------------------------------------------------ | |
1045 | ||
1046 | (136) 24-Jan-03 M Make "personal" available as a condition for use in routers | |
1047 | ------------------------------------------------------------------------------ | |
1048 | ||
1049 | (138) 28-Jan-03 M A variable containing what was matched in a host list | |
1050 | ||
1051 | Or, presumably, other lists. This is so that ACL messages can say things like | |
1052 | "your host name matches xxxx". Note: not the same as $domain_data. Also, this | |
1053 | could be tricky with lookups and things that match in files. | |
1054 | ------------------------------------------------------------------------------ | |
1055 | ||
1056 | (143) 06-Mar-03 L Ability to have multiple authenticators of same type | |
1057 | ||
1058 | For example, to have two PLAIN authenticators; if the first fails, try the | |
1059 | second. | |
1060 | ------------------------------------------------------------------------------ | |
1061 | ||
1062 | (144) 07-Mar-03 T ACL control = local_scan_skip to skip the local scan | |
1063 | ||
1064 | A bigger project would be control = local_scan <xxx> where xxx could select | |
1065 | different local_scan functions (possibly by dynamic loading). | |
1066 | ||
1067 | This can now be simulated using the fact that ACL variables are preserved, | |
1068 | so it doesn't look as it once did. | |
1069 | ------------------------------------------------------------------------------ | |
1070 | ||
1071 | (145) 07-Mar-03 T Export string_cat() to local_scan() | |
1072 | ------------------------------------------------------------------------------ | |
1073 | ||
1074 | (147) 17-Mar-03 T Option to treat 5xx as 4xx if received on initial connection | |
1075 | ||
1076 | This issue is controversial. That may be a good reason for not changing | |
1077 | anything. | |
1078 | ------------------------------------------------------------------------------ | |
1079 | ||
1080 | (153) 25-Apr-03 S A way of making log_as_local apply to the smtp transport | |
1081 | ||
1082 | Either an option on the transport, or log_remote_as_local for the router. | |
1083 | Messy, either way. Maybe log_local_as_local and log_remote_as_local, and | |
1084 | deprecate log_as_local? | |
1085 | ------------------------------------------------------------------------------ | |
1086 | ||
1087 | (154) 01-May-03 M Teergrubing at the CR/LF level | |
1088 | ||
1089 | It is believed that the most effective way to teergrube is to insert a delay | |
1090 | between transmitting CR and LF in the SMTP response. Furthermore, this is also | |
1091 | the best place to test for bad synchronization (i.e. at the last possible | |
1092 | time). | |
1093 | ------------------------------------------------------------------------------ | |
1094 | ||
1095 | (155) 01-May-03 S "control=no_pipelining" for connect and EHLO ACLs | |
1096 | ||
1097 | Yet more flexibility! Maybe this should be a more general control for what is | |
1098 | sent in response to EHLO. | |
1099 | ------------------------------------------------------------------------------ | |
1100 | ||
1101 | (156) 06-May-02 M Finer-grained synchronisation checking | |
1102 | ||
1103 | On operating systems that can be asked whether any sent bytes have not yet been | |
1104 | ACK'd at the TCP/IP level, a finer-grained check for proper synchronisation can | |
1105 | be done. All bytes must have been ACK'd if the client has received the previous | |
1106 | response before sending the next command. See also 293. | |
1107 | ------------------------------------------------------------------------------ | |
1108 | ||
1109 | (157) 07-May-03 M Newline as a list item separator | |
1110 | ||
1111 | This will make life easier for lists obtained form databases where the | |
1112 | separator is naturally a newline. | |
1113 | ------------------------------------------------------------------------------ | |
1114 | ||
1115 | (158) 13-May-03 M Ability to add to OK message for SMTP commands | |
1116 | ||
1117 | For sending reasons for slow response, etc. | |
1118 | ------------------------------------------------------------------------------ | |
1119 | ||
1120 | (160) 19-May-03 M Remove headers using wild cards | |
4990831e PH |
1121 | |
1122 | See also 333. | |
e05f33e0 PH |
1123 | ------------------------------------------------------------------------------ |
1124 | ||
1125 | (162) 28-May-03 M/L Use of real numbers in filters, expansions, and options | |
1126 | ||
1127 | The motivation for this is for handling spam scores that are real numbers. The | |
1128 | questions are (a) how widely should it spread and (b) whether floating point or | |
1129 | fixed point representations should be used. And what about the eval operator? | |
1130 | ------------------------------------------------------------------------------ | |
1131 | ||
1132 | (164) 02-Jun-03 S Set variables for interface and port in smtp transport | |
1133 | ||
1134 | These could be useful for varying HELO data etc. See also several other | |
1135 | items about interfaces above. | |
1136 | ------------------------------------------------------------------------------ | |
1137 | ||
1138 | (166) 18-Jun-03 S CN verification in client TLS code | |
1139 | ||
1140 | A tls_verify_cn option is suggested by Sven Geggus. | |
1141 | ------------------------------------------------------------------------------ | |
1142 | ||
1143 | (168) 19-Jun-03 S Ability to add a header recording envelope rewrites | |
1144 | ||
1145 | Current code adds a deleted header with only some information. Maybe what is | |
1146 | needed is a flag for a rewrite rule. | |
1147 | ------------------------------------------------------------------------------ | |
1148 | ||
1149 | (169) 19-Jun-03 M A way of detecting timeouts in callout returns | |
1150 | ||
1151 | ------------------------------------------------------------------------------ | |
1152 | ||
1153 | (170) 23-Jun-03 S Option to accept rather than defer after local scan timeout | |
1154 | ||
1155 | Suggested patch supplied. | |
1156 | ------------------------------------------------------------------------------ | |
1157 | ||
e05f33e0 PH |
1158 | (172) 23-Jun-03 M Option to make SQL query to specific server |
1159 | ||
1160 | ------------------------------------------------------------------------------ | |
1161 | ||
1162 | (175) 04-Jul-03 S show_all_ancestors_in_errmsg for the redirect router | |
1163 | ||
1164 | This is the opposite of hide_child_in_errmsg in effect. | |
1165 | ------------------------------------------------------------------------------ | |
1166 | ||
1167 | (180) 14-Jul-03 M Extend never_users to be more flexible | |
1168 | ||
1169 | e.g. never_users = ! mailnull : ! cyrus : !mailman : 0-100 | |
1170 | ------------------------------------------------------------------------------ | |
1171 | ||
1172 | (183) 16-Jul-03 S freeze_tell_text to add custom text to the message | |
1173 | ||
1174 | ------------------------------------------------------------------------------ | |
1175 | ||
1176 | (185) 24-Jul-03 S An expansion operator that decodes RFC 2047 strings | |
1177 | ||
1178 | ------------------------------------------------------------------------------ | |
1179 | ||
1180 | (188) 13-Aug-03 T batch_max=0 to mean unlimited | |
1181 | ||
1182 | ------------------------------------------------------------------------------ | |
1183 | ||
1184 | (189) 22-Aug-03 S Allow filter "logwrite" to write to syslog | |
1185 | ||
1186 | I feel this is a dangerous facility, and also of very minority interest, at | |
1187 | least for user's filters. Allowing a system filter to write to mainlog or | |
1188 | syslog may be different. However, writing the main log would only be possible | |
1189 | if the filter runs as root or exim. | |
1190 | ------------------------------------------------------------------------------ | |
1191 | ||
1192 | (190) 22-Aug-03 S A way of testing "forced delivery" in filter and routers | |
1193 | ------------------------------------------------------------------------------ | |
1194 | ||
1195 | (191) 26-Aug-03 M Preserve $address_data for a verified recipient | |
1196 | ||
1197 | The idea is to preserve it in the recipients data structure so that local_scan | |
1198 | can have access to it. The value could also be used as the initial value of | |
1199 | $address_data while routing. | |
1200 | ------------------------------------------------------------------------------ | |
1201 | ||
1202 | (192) 05-Sep-03 M Better handling of TXT records for dnslists | |
1203 | ||
1204 | When multiple lists are accessible via a merged lookup, handling TXT records | |
1205 | is difficult. An option for doing the TXT lookup in a sub-list has been | |
1206 | suggested, with syntax such as | |
1207 | ||
1208 | dnslists = list.example.org=127.0.0.2%dialups \ | |
1209 | ,127.0.0.3%relays \ | |
1210 | ,127.0.0.5%spews | |
1211 | ------------------------------------------------------------------------------ | |
1212 | ||
1213 | (194) 10-Sep-03 M $addresslist_data to be like $host_data/$domain_data | |
1214 | ||
1215 | ------------------------------------------------------------------------------ | |
1216 | ||
1217 | (195) 29-Sep-03 M A variable containing the error for verify = header_syntax | |
1218 | ||
1219 | Maybe there should always be a variable with the error message for all the | |
1220 | different kinds of verify failure. | |
1221 | ------------------------------------------------------------------------------ | |
1222 | ||
1223 | (196) 30-Sep-03 S A way of detecting whether it was HELO or EHLO in the ACL | |
1224 | ||
1225 | $received_protocol isn't reset until after the command is accepted (which | |
1226 | seems right), and $smtp_data shows only the arguments. Maybe $smtp_command? | |
1227 | ------------------------------------------------------------------------------ | |
1228 | ||
1229 | (197) 30-Sep-03 S MACROS_DROP_PRIVS and ALT_CONFIG_DROP_PRIVS | |
1230 | ||
1231 | Now that alternative configurations can be restricted to certain directories, | |
1232 | some more flexibility can be allowed. Not by default, though. | |
1233 | ------------------------------------------------------------------------------ | |
1234 | ||
1235 | (198) 01-Oct-03 M Accept mail after local_scan() crash instead of defer | |
1236 | ||
1237 | This may not be as easy to implement as it sounds; one is never sure of the | |
1238 | environment after a crash. Is is actually a good idea? The crashing local_scan | |
1239 | may have wrecked the memory in arbitrary ways; for example, screwing up the | |
1240 | recipients list... | |
1241 | ------------------------------------------------------------------------------ | |
1242 | ||
1243 | (199) 01-Oct-03 M ${pipe which will pipe the message to a script ... | |
1244 | ||
1245 | ... and otherwise behave as ${run. Probably needs to have locking out features | |
1246 | so that it can be turned off for users .forwards if the sysadmin so desires. | |
1247 | ------------------------------------------------------------------------------ | |
1248 | ||
1249 | (200) 07-Oct-03 L Alternative ways of storing hints | |
1250 | ||
1251 | People want to store hints in databases. Some assert that SQL databases can | |
1252 | be made to perform satisfactorily. If a general interface could be worked on, | |
1253 | people could at least try different strategies. See also 66 above, which is | |
1254 | specifically concerned with Berkeley DB. Another possible option is a switch to | |
1255 | disable smtp-wait hints - to avoid contention problems. | |
1256 | ------------------------------------------------------------------------------ | |
1257 | ||
1258 | (201) 07-Oct-03 M A "soft bounce" feature | |
1259 | ||
1260 | This is an option that turns all hard bounces into soft bounces. The idea is | |
1261 | that it can be used as a safety-net while testing configurations. Instead of a | |
1262 | local bounce, the message stays on the queue; instead of 5xx SMTP responses, | |
1263 | 4xx ones are given. | |
1264 | ||
1265 | The ability to do the opposite - turn 4xx into 5xx under certain circumstances | |
1266 | might also be useful (e.g. after a certain time). This might best be done by | |
1267 | extending the retry logic to recognize 4xx as a special error. (This is now | |
1268 | done.) | |
1269 | ------------------------------------------------------------------------------ | |
1270 | ||
1271 | (202) 10-Oct-03 S -bvsomething to do a callout after the verify | |
fb636a0f PH |
1272 | |
1273 | For example: -bvc and -bvsc. The problem now (Nov 04) is that there are quite a | |
1274 | few possible callout options that can be specified in an ACL, and they would | |
1275 | have to be replicated here. | |
e05f33e0 PH |
1276 | ------------------------------------------------------------------------------ |
1277 | ||
1278 | (203) 14-Oct-03 S verify=something to easily check for header presence | |
1279 | ||
1280 | This is purely cosmetic; "condition" can already be used. | |
1281 | ------------------------------------------------------------------------------ | |
1282 | ||
1283 | (204) 27-Oct-03 S an inverted queue_only_file | |
1284 | ||
1285 | That is, queue if a file does NOT exist. | |
1286 | ------------------------------------------------------------------------------ | |
1287 | ||
1288 | (205) 27-Oct-03 S expand smtp_accept_queue_per_connection | |
1289 | ||
1290 | ------------------------------------------------------------------------------ | |
1291 | ||
1292 | (206) 27-Oct-03 S appendfile: a variable containing the maildir base name | |
1293 | ||
1294 | ------------------------------------------------------------------------------ | |
1295 | ||
1296 | (207) 29-Oct-03 S ability to keep trusted users in a file - expand it. | |
1297 | ------------------------------------------------------------------------------ | |
1298 | ||
1299 | (208) 31-Oct-03 M cache temporary verification errors and fail after a time | |
1300 | ||
1301 | This request was for a way of turning temporary verification failures into | |
1302 | permanent ones after some fixed time. | |
1303 | ------------------------------------------------------------------------------ | |
1304 | ||
1305 | (209) 31-Oct-03 S a way of making crashes in pipe commands temporary errors | |
1306 | ||
1307 | ------------------------------------------------------------------------------ | |
1308 | ||
1309 | (210) 31-Oct-03 S runtime option to change the daemon name used for tcprwappers | |
1310 | ||
1311 | A patch for compile time was supplied, but this seems better as a runtime | |
1312 | option, for use with multiple Exim daemons. | |
1313 | ------------------------------------------------------------------------------ | |
1314 | ||
1315 | (211) 31-Oct-03 S ability to disable debugging output from -bh & -bhc | |
1316 | ------------------------------------------------------------------------------ | |
1317 | ||
1318 | (212) 31-Oct-03 M specify headers lines in HELO ACL to be added to all msgs | |
4990831e PH |
1319 | |
1320 | See also 333. | |
e05f33e0 PH |
1321 | ------------------------------------------------------------------------------ |
1322 | ||
1323 | (214) 05-Nov-03 S Put the wild part of local part prefix/suffx in variables | |
1324 | ||
1325 | Unfortunately, this isn't quite as trivial as it seems. | |
1326 | ------------------------------------------------------------------------------ | |
1327 | ||
1328 | (215) 14-Nov-03 S A way of turning off message-submission fix-ups | |
1329 | ||
1330 | Globally, and perhaps also via an ACL control so that it can be done on a | |
fb636a0f PH |
1331 | per-message basis. Is this still needed? Since this item was added to this |
1332 | list, default fixups for non-local messages have been removed, and control = | |
1333 | submission has been added. | |
e05f33e0 PH |
1334 | ------------------------------------------------------------------------------ |
1335 | ||
1336 | (215) 26-Nov-03 M/L Conversion of IDNA domain names for logging | |
1337 | ||
1338 | IDNA (RFCs 3490-3492) converts domains names containing non-ASCII characters | |
1339 | into ASCII strings of a special form. Exim will of course handle these. | |
1340 | However, it might be nice to convert them to a local code for logging. This | |
1341 | might be quite a big project: there's also output from -bp and eximon queue | |
1342 | display and no doubt other places as well. (Utilities that process the logs, | |
1343 | e.g. exigrep, eximstats, will be automatically handled if the logs are | |
1344 | changed.) | |
1345 | ------------------------------------------------------------------------------ | |
1346 | ||
1347 | (216) 27-Nov-03 S Option to bounce if required TLS doesn't happen | |
1348 | ||
1349 | This is for the smtp transport with hosts_require_tls set. Currently, it | |
1350 | defers. Possibly the best approach is to make the error one that can be seen by | |
1351 | the retry logic. | |
1352 | ------------------------------------------------------------------------------ | |
1353 | ||
1354 | (217) 27-Nov-03 M A function to pass back variables from Perl | |
1355 | ||
1356 | This is a function that can be called from Perl, to take a name and a value and | |
1357 | put that value into an Exim variable. | |
1358 | ------------------------------------------------------------------------------ | |
1359 | ||
1360 | (218) 01-Dec-03 M A local_scan-like hook at system filter time | |
1361 | ||
1362 | That is, make a C API available for custom filtering at this point. | |
1363 | ------------------------------------------------------------------------------ | |
1364 | ||
1365 | (221) 18-Dec-03 U Merge routers and ACLs - or at least make more similar | |
1366 | ||
1367 | "It will be very useful to be able to use most of the ACL conditions | |
1368 | (authenticated, hosts, senders, sender_domains, ... ) in routers and also the | |
1369 | possibility to have multiple conditions in routers. It will be great to also | |
1370 | be able to set variables in routers like in acl's." This is effectively a | |
1371 | radical suggestion for a complete re-design, and is therefore BIG. | |
1372 | ------------------------------------------------------------------------------ | |
1373 | ||
e05f33e0 | 1374 | (223) 22-Dec-03 S Support SOA lookup in dnsdb lookups |
fb636a0f PH |
1375 | |
1376 | This could be like zns, and climb up the tree till it hits a zone. Would the | |
1377 | name of the zone be required? | |
e05f33e0 PH |
1378 | ------------------------------------------------------------------------------ |
1379 | ||
1380 | (225) 22-Dec-03 M Add acl= to routers | |
1381 | ||
1382 | This would use an ACL to "control access" to a router, opening up a number | |
1383 | of interesting possibilities. Details of possible limitations need to be | |
1384 | investigated. | |
1385 | ------------------------------------------------------------------------------ | |
1386 | ||
1387 | (226) 23-Dec-03 S A way of treating DEFER as fail in dnsdb lookups | |
1388 | ||
1389 | (i.e. the dnsdb lookup failed, so accept the message) | |
1390 | ------------------------------------------------------------------------------ | |
1391 | ||
1392 | (227) 30-Jan-04 M A configuration .if facility | |
1393 | ||
1394 | "Second with the .ifdef and such, it would be nice to have a base .if, | |
1395 | so I could do something like | |
1396 | .if DEFINED_DATA == xyz | |
1397 | configuration here | |
1398 | .elseif DEFINED_DATA == abc | |
1399 | configuration here | |
1400 | .else | |
1401 | configuration here | |
1402 | .endif | |
1403 | also this would be nice at least in my case in the system filters, but | |
1404 | isn't required but you could pass the defined data to the system, in | |
1405 | variables." | |
1406 | ------------------------------------------------------------------------------ | |
1407 | ||
1408 | (229) 30-Jan-04 M New expansion mechanism: {list ...} | |
1409 | ||
1410 | "Proposed syntax: {list {separator}{item}{item}...} | |
1411 | This first expands the contents of {separator} and all of the {item}s, | |
1412 | then constructs a separator-delimited list. The twist is: if an {item} | |
1413 | generates the empty string, no separator will be generated for it. | |
1414 | The entire construct will fail is {separator} fails, or all {item}s | |
1415 | fail. If just some {item}s fail, they will be treated as if they | |
1416 | generated empty strings. | |
1417 | Examples: | |
1418 | {list {,}{aaaaaa}{bbbbbb}{cccccc}} -> aaaaaa,bbbbbb,cccccc | |
1419 | {list {,}{:fail:}{bbbbbb}{cccccc}} -> bbbbbb,cccccc | |
1420 | {list {,}{aaaaaa}{:fail:}{cccccc}} -> aaaaaa,cccccc | |
1421 | {list { }{aaaaaa}{bbbbbb}{}} -> aaaaaa bbbbbb | |
1422 | {list { }{:fail:}{:fail:}{:fail:}} -> :fail: | |
1423 | {list {:fail:}{aaaaa}{bbbb}{cccc}} -> :fail: | |
1424 | See particularly examples 2-4, which handle the case of a missing first | |
1425 | and last item with ease; doing this using {if ...} would be quite difficult!" | |
1426 | ------------------------------------------------------------------------------ | |
1427 | ||
1428 | (230) 30-Jan-04 M Find IP addresses of a domain's nameservers | |
1429 | ||
1430 | This needs some way of processing a list of things in a similar way, which | |
fc9c2317 PH |
1431 | should perhaps be a more general facility. // This can now be done using the |
1432 | list facilities of dnsdb; verbose, but it can be done. // | |
e05f33e0 PH |
1433 | ------------------------------------------------------------------------------ |
1434 | ||
1435 | (231) 30-Jan-04 ? -C has a number of problems when used for real | |
1436 | ||
1437 | -C was intended for testing; people are using it for "alternate" | |
1438 | configurations, and it doesn't work too well. Can a better way of doing this be | |
1439 | invented? | |
1440 | ------------------------------------------------------------------------------ | |
1441 | ||
1442 | (232) 02-Feb-04 ? Make parts of the code loadable | |
1443 | ||
1444 | The idea being that drivers, etc. could be compiled separately. There are, of | |
1445 | course, security issues. This is not something I want to go into at present. | |
1446 | ------------------------------------------------------------------------------ | |
1447 | ||
1448 | (235) 02-Feb-04 T Make smtp_accept_count available as a variable | |
1449 | ||
1450 | This is for use in ACLs. Of course, it is a snapshot of the count at the | |
fc9c2317 PH |
1451 | start of the receiving process. As such, it could be confusing because if a |
1452 | connection lasts a long time, the "true" value could be very different. For | |
1453 | this reason, I don't really like this idea. | |
e05f33e0 PH |
1454 | ------------------------------------------------------------------------------ |
1455 | ||
1456 | (236) 02-Feb-04 S String in local_scan that's added to the binary version string | |
1457 | ------------------------------------------------------------------------------ | |
1458 | ||
1459 | (237) 02-Feb-04 M Add_header in ACLs because "message" is overloaded | |
1460 | ||
4990831e PH |
1461 | This would be useful for verbs where "message" is an error message. See also |
1462 | 333. | |
e05f33e0 PH |
1463 | ------------------------------------------------------------------------------ |
1464 | ||
1465 | (238) 05-Feb-04 S ${address to handle multiple addresses | |
1466 | ||
1467 | At present, ${address expects to see just one address. An extension would let | |
1468 | it handle header lines with multiple addresses, just retaining the actual | |
1469 | addresses. Or perhaps a new operator is needed? | |
1470 | ------------------------------------------------------------------------------ | |
1471 | ||
1472 | (239) 23-Feb-04 ? Expansion items for encryption/decryption | |
1473 | ||
1474 | Perhaps for some kind of cookie handling? This would need an external crypto | |
1475 | library, because there's no crypto code in Exim itself. | |
1476 | ------------------------------------------------------------------------------ | |
1477 | ||
1478 | (240) 23-Feb-04 ? Some way to know if a ip is a mx for a given domain | |
1479 | ||
1480 | Some kind of iterative operation for dnsdb might be a general way of providing | |
fc9c2317 PH |
1481 | this. // This can now be done using the list facilities of dnsdb; verbose, but |
1482 | it can be done. // | |
e05f33e0 PH |
1483 | ------------------------------------------------------------------------------ |
1484 | ||
1485 | (242) 01-Mar-04 ? Run a filter from an expansion condition | |
1486 | ||
1487 | This would add a lot of power to ACLs, but its implementation might be tricky | |
1488 | because of the possibility of recursion. | |
1489 | ------------------------------------------------------------------------------ | |
1490 | ||
1491 | (243) 01-Mar-04 ? Run an ACL from an expansion condition | |
1492 | ||
1493 | The problem here is knowing what data is available at an arbitrary time. | |
1494 | ------------------------------------------------------------------------------ | |
1495 | ||
1496 | (244) 01-Mar-04 ? Add an on-success event to transports | |
1497 | ||
1498 | This could just be an expansion string, whose value is either ignored or | |
1499 | logged, but it could be used to run SQL updates or run programs etc. | |
1500 | However, what is "success" when a transport has multiple recipients? | |
1501 | ------------------------------------------------------------------------------ | |
1502 | ||
1503 | (245) 01-Mar-04 M Add all the string expansion conditions to filters | |
1504 | ||
1505 | Some thought would be needed on how to design the syntax for this. | |
1506 | ------------------------------------------------------------------------------ | |
1507 | ||
1508 | (247) 09-Mar-04 S IP addresses that are never looked up | |
1509 | ||
1510 | It would be nice if we could prevent this for certain IP addresses for | |
1511 | which we _know_ we'll never get a valid PTR record, like 2002::/16. | |
1512 | So a new option might reasonably default to: | |
1513 | ||
1514 | hosts_never_lookup = <; 2002::/16 | |
1515 | ------------------------------------------------------------------------------ | |
1516 | ||
1517 | (253) 05-Apr-04 M Use ESMTP and TLS for recipient callout verification | |
1518 | ||
1519 | The best way to do this would involve quite a bit of refactoring so as to | |
1520 | abstract some of the code from the smtp transport into subroutines that could | |
1521 | also be used from the callout code. The tls parameters should probably be | |
1522 | taken from the transport. That might also require some substantial code | |
1523 | refactoring. See also 294. | |
1524 | ------------------------------------------------------------------------------ | |
1525 | ||
1526 | (260) 30-Apr-04 S Respect +tls_cipher +tls_peerdn in rejectlog entries | |
1527 | ||
1528 | ------------------------------------------------------------------------------ | |
1529 | ||
1530 | (261) 05-May-04 S Add a "required_version" option | |
1531 | ||
1532 | So that configurations can insist on a specific Exim version. | |
1533 | ------------------------------------------------------------------------------ | |
1534 | ||
1535 | (262) 10-May-04 S Add "scratch" ACL variables | |
1536 | ||
1537 | The idea is for variables that are flushed at the start of each ACL. I'm not | |
1538 | really convinced that these are worth implementing. | |
1539 | ------------------------------------------------------------------------------ | |
1540 | ||
1541 | (263) 10-May-04 S Add variable $router_name $transport_name | |
1542 | ||
1543 | These could be used in debug_print settings, which are output during -bt, and | |
1544 | thus don't need the privilege to run with -d. | |
1545 | ------------------------------------------------------------------------------ | |
1546 | ||
1547 | (265) 25-May-04 M An init.d script for exim is needed | |
1548 | ||
1549 | The old sendmail script used to "just work" because it just did -bd -q 20m or | |
1550 | whatever. Newer versions start more than one sendmail daemon, so do not work. | |
1551 | ------------------------------------------------------------------------------ | |
1552 | ||
1553 | (267) 25-May-04 S tarpitting delay option | |
1554 | ||
1555 | A modifier that sets a delay between lines for multiline responses. | |
1556 | ------------------------------------------------------------------------------ | |
1557 | ||
1558 | (268) 25-May-04 S? Add a PID to every log line | |
1559 | ||
1560 | Given that pids are reused non-cyclically these days, is this actually useful? | |
1561 | ------------------------------------------------------------------------------ | |
1562 | ||
e05f33e0 PH |
1563 | (270) 01-Jun-04 M Add headers at top and middle |
1564 | ||
1565 | Various initiatives like SPF and DomainKeys require header lines to be added | |
1566 | above or in the middle of existing headers. Exim always adds at the bottom. | |
1567 | When these requirements are more standard and clearer, some way of controlling | |
1568 | where header lines are added will probably become necessary. Some new syntax | |
1569 | will be required. | |
1570 | ||
1571 | This can now be done fairly generally from local_scan(), and at the start and | |
4990831e | 1572 | after the Received: block from an ACL. Is anything more needed? See also 333. |
e05f33e0 PH |
1573 | ------------------------------------------------------------------------------ |
1574 | ||
1575 | (271) 02-Jun-04 L Callouts at routing time | |
1576 | ||
1577 | From a user's message: | |
1578 | ||
1579 | > I would like to be able to: | |
1580 | >[...] | |
1581 | > 2) Forcing callouts as address verification at router level | |
1582 | > [ check_callout just like check_local_user ] | |
1583 | > | |
1584 | > I would like to redirect messages in some domain to "domain with callout | |
1585 | > verification" and to "domain without callout verification" | |
1586 | > | |
1587 | > e.g. | |
1588 | > userA@domain.in -> userX@doamin.out-verify (use callout to verify) | |
1589 | > userB@domain.in -> userY@doamin.out-noverify (do not use callout verify) | |
1590 | > | |
1591 | > [both out-* domains delivered via "callout ready" transports] | |
1592 | ||
1593 | Other versions of the wish: | |
1594 | * limiting callouts in acls to specific transport | |
1595 | verify = recipient/callout=5s,transport:intranet_smtp | |
1596 | * adding "select transport" to ACL conditions | |
1597 | accept domains = +local_domains | |
1598 | transport = cyrus_ltcp | |
1599 | verify = recipient/callout=5s | |
1600 | ------------------------------------------------------------------------------ | |
1601 | ||
1602 | (272) 07-Jun-04 S Expand hosts_randomize | |
1603 | ||
1604 | It occurs in manualroute and in smtp. | |
1605 | ------------------------------------------------------------------------------ | |
1606 | ||
1607 | (278) 21-Jun-04 M quota_warn_message_file option | |
1608 | ||
1609 | Similar to the bounce and delivery warn message files. | |
1610 | ------------------------------------------------------------------------------ | |
1611 | ||
1612 | (280) 23-Jun-04 M A way of adding a header line after callout defer_ok | |
1613 | ||
1614 | This would record that, e.g., a sender domain verified, but the callout | |
fb636a0f PH |
1615 | could not be done. There are ways of fudging this, using ACL variables and |
1616 | "warn" statements. | |
e05f33e0 PH |
1617 | ------------------------------------------------------------------------------ |
1618 | ||
1619 | (285) 16-Jul-04 M Separate and independent log_selector for rejectlog | |
1620 | ||
1621 | For example: mainlog_selector and rejectlog_selector, with log_selector setting | |
1622 | both of them. | |
1623 | ------------------------------------------------------------------------------ | |
1624 | ||
1625 | (286) 21-Jul-04 M Distinguishing a larger number of errors | |
1626 | ||
1627 | For instance, detecting "connection reset by peer" (ENETRESET or ECONNRESET) | |
1628 | might be useful. | |
1629 | ------------------------------------------------------------------------------ | |
1630 | ||
1631 | (288) 10-Aug-04 M Option for verify to require MX | |
1632 | ||
1633 | e.g. verify=sender/require_mx | |
1634 | I'm not too keen because this is rather special purpose, and of course could | |
1635 | only apply if the verification happened to hit a dnslookup router. | |
1636 | ------------------------------------------------------------------------------ | |
1637 | ||
1638 | (289) 10-Aug-04 L Option to treat defers in database lookups as "not found" | |
1639 | ||
1640 | This is so that alternatives can be coded for when databases are down. A | |
1641 | suggested patch has been sent, but it just catches all instances of "defer" | |
1642 | from a lookup in an expansion string. These can occur for a number of different | |
1643 | reasons, not just connection failures. I think that we need a specific | |
1644 | "connection failed" indicator. Also, what about lookups in lists? | |
1645 | ------------------------------------------------------------------------------ | |
1646 | ||
1647 | (291) 13-Aug-04 M An ACL or "local_scan()" to be run on size excession | |
1648 | ||
1649 | The idea is to give something a chance to look at the data so far received when | |
1650 | more than message_size_limit (or some other limit) has arrived. I am not sure | |
1651 | how useful this would actually be in practice. | |
1652 | ------------------------------------------------------------------------------ | |
1653 | ||
1654 | (292) 13-Aug-04 M Overall timeout for message reception | |
1655 | ||
1656 | A client could in priciple keep an SMTP connection open for a very long time by | |
1657 | trickling in data very slowly. Also, after message_size_limit is exceeded, Exim | |
1658 | continues to swallow the data (though it does not write it to disk) until the | |
1659 | end is reached. Again, the connection could be held open for a very long time. | |
1660 | Some kind of overall time limit for an SMTP connection, possibly reset at the | |
1661 | start of each message, might be helpful in these situations. | |
1662 | ------------------------------------------------------------------------------ | |
1663 | ||
1664 | (294) 23-Aug-04 L Callouts and AUTH and LMTP | |
1665 | ||
1666 | People want to do callouts using LMTP as well as SMTP, and that would also | |
1667 | include sockets as well as TCP/IP connections. Also, people want to make use of | |
1668 | AUTH during the callout checking, on all types of connection. I suppose that | |
1669 | means making TLS available as well. This probably means a rewrite of the code | |
1670 | that actually does the callout. Should we use the relevant transport in a new | |
fdfdba09 | 1671 | "callout" mode instead of keeping things separate? See also 253 and 323. |
461f4862 PH |
1672 | |
1673 | And here's another submitted idea: "My actual suggestion is that if this model | |
1674 | is followed, the parent process doesn't have to stop the callout process if it | |
1675 | is taking too long to respond: it can return 450 to the incoming connection | |
1676 | within the 5 minute SMTP command timeout and leave the callout process to | |
1677 | continue, in the hope that it will eventually get a result and store it in the | |
1678 | callout cache in time for the sender's next attempt." | |
e05f33e0 PH |
1679 | ------------------------------------------------------------------------------ |
1680 | ||
1681 | (296) 09-Sep-04 S Make deliver_time work for == lines as well as => | |
1682 | ||
1683 | What about ** lines? | |
1684 | ------------------------------------------------------------------------------ | |
35f53bf6 | 1685 | |
35f53bf6 PH |
1686 | (299) 25-Oct-04 S Options to make Sieve "keep" pass to next router |
1687 | ||
1688 | Currently, "keep" saves in the mailbox. Probably need two options, for implicit | |
1689 | and explicit keep commands. | |
1690 | ------------------------------------------------------------------------------ | |
1691 | ||
0cf417c5 PH |
1692 | (301) 27-Oct-04 M Use an "ACL" to filter logging |
1693 | ||
1694 | This idea was for ACL syntax to be able to "accept" or "deny" individual log | |
1695 | lines. This would make it possible to have, for example, per-host logging for | |
1696 | certain things. See also 15 above. | |
1697 | ------------------------------------------------------------------------------ | |
32aaebb6 PH |
1698 | |
1699 | (302) 28-Oct-04 M Expand pass_router and redirect_router | |
1700 | ||
1701 | Doing this would mean postponing the validity checks till the router was | |
1702 | actually used instead of doing them at start up. It does not seem to be a | |
1703 | facility that will be widely used. | |
1704 | ------------------------------------------------------------------------------ | |
1705 | ||
1706 | (303) 28-Oct-04 M Support SQL relay | |
1707 | ||
1708 | This would make it easier for packagers to support "generic SQL" without having | |
1709 | to choose which one. It can be slotted in using a MySQL interface without | |
1710 | modifying Exim, but native support would be nice. | |
1711 | ------------------------------------------------------------------------------ | |
1712 | ||
1713 | (304) 02-Nov-04 M A way of seeing the whole message in Perl or ${run | |
1714 | ||
1715 | At present, the headers are available in $message_headers, but only part of | |
1716 | the body is visible. The only way to pass the whole body would be as a file | |
1717 | descriptor because it can be very large. See also (42). | |
1718 | ------------------------------------------------------------------------------ | |
1719 | ||
1720 | (305) 02-Nov-04 M A Perl transport | |
1721 | ||
1722 | The suggestion here is that an embedded Perl function takes responsibility for | |
1723 | doing the delivery. I am not at all keen on this. One way of doing it would be | |
1724 | to implement (244), which provides an "on success" string expansion. Then | |
1725 | anyone who wants this could run that on a transport that does nothing. | |
1726 | ------------------------------------------------------------------------------ | |
b5c45968 PH |
1727 | |
1728 | (306) 09-Nov-04 M Make the search type partial-lsearch*@ be useful | |
1729 | ||
1730 | At present, it treats the whole key as a domain for the partial search, then | |
1731 | does the *@ thing. A more sensible plan would be something like: | |
1732 | ||
1733 | user@company.com | |
1734 | *@company.com | |
1735 | user@*.company.com | |
1736 | *@*.company.com | |
1737 | * | |
1738 | ||
1739 | That is, try the local part and * at each of the partial domain values. | |
1740 | ------------------------------------------------------------------------------ | |
5b1fde4d PH |
1741 | |
1742 | (307) 24-Nov-04 S Check the syntax of Message-ID: header lines | |
1743 | ||
1744 | This could be added to "verify=header_syntax" or, if the incompatibility is | |
1745 | felt to be too great, an additional condition, or a sub-option, could be added. | |
1746 | ------------------------------------------------------------------------------ | |
908acc4e PH |
1747 | |
1748 | (308) 24-Nov-04 S Add $body_longlinecount and $header_longlinecount | |
1749 | ||
1750 | These variables would hold the number of physical lines in the body and header | |
1751 | that were longer than 998 bytes. This would be fiddly to implement because of | |
1752 | the way Exim currently reads the input. It isn't just a trivial patch. | |
1753 | ------------------------------------------------------------------------------ | |
a78fb8ef PH |
1754 | |
1755 | (309) 01-Dec-04 S/M Queue runners should get locks before forking | |
1756 | ||
1757 | If a queue-runner opened the -D file and took out the lock before forking, it | |
1758 | would waste fewer resources if the message was already being delivered. But how | |
1759 | often would this actually matter in practice? | |
1760 | ------------------------------------------------------------------------------ | |
fbbf1e99 PH |
1761 | |
1762 | (310) 06-Dec-04 S After "personal" save what matched | |
1763 | ||
1764 | The idea is to save the email address that actually was found in the message | |
1765 | in a variable so it can be used (e.g. as the From: address in an autoreply). | |
1766 | ------------------------------------------------------------------------------ | |
59e88703 PH |
1767 | |
1768 | (311) 07-Dec-04 ? More flexible SMTP response codes | |
1769 | ||
1770 | The requestor wanted to be able to specify, for example, 551 in an ACL deny | |
1771 | instead of 550, and also vary the defer code. The first digit, however, should | |
1772 | remain fixed. In addition to main codes, enhanced status codes (RFC 2034) were | |
1773 | requested. (As far as I can tell, they have never been highly popular.) | |
1774 | ------------------------------------------------------------------------------ | |
f7b63901 PH |
1775 | |
1776 | (312) 10-Dec-04 ? Shadow remote transports | |
1777 | ||
1778 | Unless a lot of work is done, this would be restricted to another remote | |
1779 | transport. A similar effect could therefore be achieved with "shadow_hosts" | |
1780 | which are like fallback_hosts but which operate on success. | |
1781 | ------------------------------------------------------------------------------ | |
23fd96b1 PH |
1782 | |
1783 | (313) 21-Jan-05 ? Multiple queues | |
1784 | ||
1785 | Exim runs poorly if its queue gets too big. Various ways round this are all | |
1786 | to some extent kludges. There has been a suggestion of using multiple | |
1787 | directories instead of just "input". (Originally it was for a whole set of | |
1788 | spool directories, but that introduces complications with the hint files.) | |
1789 | On message arrival, somehow a selection of "input" must be made. Then queue | |
1790 | runners must be startable for the different "queues". Don't forget that the | |
1791 | "msglog" directory is also involved. Perhaps add a new level of indirection: | |
1792 | /var/spool/exim/queue1/{input,msglog}, /var/spool/exim/queue2/.... | |
1793 | ------------------------------------------------------------------------------ | |
7163d8cf PH |
1794 | |
1795 | (314) 15-Feb-05 M Multiple headers_{add,remove} for routers | |
1796 | ||
1797 | If headers_{add,remove} could be specified multiple times, it would be easier | |
4990831e PH |
1798 | for those people that construct configs using .ifdef or .include, etc. See also |
1799 | 333. | |
7163d8cf | 1800 | ------------------------------------------------------------------------------ |
54a4fbd5 PH |
1801 | |
1802 | (315) 15-Feb-05 M String variables for use in filters. | |
1803 | ||
1804 | Currently, only numerical variables are supported. | |
1805 | ------------------------------------------------------------------------------ | |
46c23dba PH |
1806 | |
1807 | (316) 21-Feb-05 M Put callout response into a variable | |
1808 | ||
1809 | When a callout fails, put the entire SMTP response into a variable. This is not | |
1810 | trivial because we probably should retain it in the cache as well. | |
1811 | ------------------------------------------------------------------------------ | |
a6c11ddf PH |
1812 | |
1813 | (317) 25-Feb-05 S Delete the pid file when the daemon exits | |
1814 | ||
1815 | At least try to catch some of the exit routes from the daemon and either delete | |
1816 | or empty the pid file. | |
1817 | ------------------------------------------------------------------------------ | |
09a23feb | 1818 | |
6758c780 | 1819 | (318) 02-Mar-05 S Add current connection count to daemon's exiwhat output |
09a23feb | 1820 | ------------------------------------------------------------------------------ |
6758c780 PH |
1821 | |
1822 | (319) 03-Mar-05 ? Allow file rather than directory for scanning call | |
1823 | ||
1824 | "I can call arbitrary scanning software by specifying the full path. I can pass | |
1825 | a directory to be scanned in the arguments. I'd like to be able to pass a | |
1826 | specific file name instead of a directory. I think this would allow me to call | |
1827 | Bogofilter at smtp time. Bogofilter requires a filename, not a directory. The | |
1828 | file would contain the complete email. I suppose there may be other scanning | |
1829 | solutions with a similar requirement." | |
1830 | ------------------------------------------------------------------------------ | |
1831 | ||
45b1794b PH |
1832 | (321) 07-Mar-05 S Run an ACL on a sync error |
1833 | ||
1834 | ... and possibly "accept" or "deny" it. | |
1835 | ------------------------------------------------------------------------------ | |
596875b3 PH |
1836 | |
1837 | (322) 15-Mar-05 M Add a /defer_ok option to verify=reverse_host_lookup | |
1838 | ------------------------------------------------------------------------------ | |
fdfdba09 PH |
1839 | |
1840 | (323) 15-Mar-05 M Make callouts use smtp_data from the smtp transport | |
1841 | ||
1842 | This is yet another problem caused by duplicating the SMTP code between the | |
1843 | transport and the callout verification. See item 294 above. Merging the | |
1844 | transport and the callout code could prevent this kind of thing from happening. | |
1845 | ------------------------------------------------------------------------------ | |
fb6f3d5c PH |
1846 | |
1847 | (324) 04-Apr-05 ? Make -bP show ACLs | |
1848 | ||
1849 | This is in the Bugzilla as #10. | |
1850 | ------------------------------------------------------------------------------ | |
4e714aed | 1851 | |
f331f3b6 PH |
1852 | (326) 03-May-05 ? Queue-only on memory shortage |
1853 | ||
1854 | This is bugzilla #17. The idea is to have something like queue_only_load that | |
1855 | triggers on a shortage of main memory. | |
1856 | ------------------------------------------------------------------------------ | |
f0884f39 PH |
1857 | |
1858 | (327) 06-May-05 ? Break delay if connection drops | |
1859 | ||
1860 | Currently, "delay=5m" (e.g.) waits for 5 minutes. If we can detect that the | |
1861 | connection has died in the meantime, it would make sense to break the delay. | |
ec798043 PH |
1862 | However, it doesn't seem possible to detect a dropped connection without trying |
1863 | to read from it. | |
f0884f39 | 1864 | ------------------------------------------------------------------------------ |
22907b39 | 1865 | |
c9f149f5 | 1866 | (328) 10-May-05 S After "unseen" routing, pass on header additions/deletions |
22907b39 PH |
1867 | |
1868 | Currently, when an "unseen" router accepts an address, header additions and | |
1869 | deletions stick with that address, and the "clone" address that continues to be | |
1870 | routed starts off without any additions or removals. This request is for an | |
1871 | option to select other actions: retain header actions with the clone only, or | |
4990831e | 1872 | pass them on to both addresses. See also 333. |
22907b39 | 1873 | ------------------------------------------------------------------------------ |
c9f149f5 PH |
1874 | |
1875 | (329) 12-May-05 S Create message ID at MAIL FROM time | |
1876 | ||
1877 | Currently, the ID is created only when Exim is about to create the data (-D) | |
1878 | file for an incoming message. In other words, after it knows it really is going | |
1879 | to accept the message. Creating the ID earlier would mean that rejection | |
1880 | messages in the log would be tagged with an ID, and this is seen as desirable | |
1881 | by some people. | |
1882 | ------------------------------------------------------------------------------ | |
ec798043 PH |
1883 | |
1884 | (330) 31-May-05 ? Default interface for -bh and default port for -oMi | |
1885 | ||
1886 | I do not think it worth putting effort in here for these reasons: If a host has | |
1887 | multiple interfaces, there's no easy way to choose one to be the default for | |
1888 | $interface_address when -bh is used. If the host does not have multiple | |
1889 | interfaces, chances are the configuration won't be looking at | |
1890 | $interface_address anyway. If you are setting -oMi, and care about the port, it | |
1891 | isn't much effort to tack on a port number, though in this case, I suppose a | |
1892 | default of 25 is "obvious". | |
1893 | ------------------------------------------------------------------------------ | |
1894 | ||
1895 | (331) 31-May-05 M More than one retry time per host | |
1896 | ||
1897 | Consider this example: an attempt to start a TLS connection to a host gets a | |
1898 | temporary error. This stops *all* connections, both for TLS and otherwise. | |
1899 | Different retry times for different circumstances are needed to get round this. | |
1900 | What are the circumstances? TLS/not-TLS is clearly one, but sometimes you don't | |
1901 | know if you are going to try TLS until you have connected. So this makes sense | |
1902 | only if require_tls is used. Perhaps the multiple retry times should just be | |
1903 | per-transport, to avoid these difficulties. If we made all retry keys depend on | |
1904 | the transport, this would happen automatically. | |
1905 | ------------------------------------------------------------------------------ | |
857c3b3f PH |
1906 | |
1907 | (332) 03-Jun-05 S A "receive time taken" log selector | |
1908 | ||
1909 | This suggestion is to at an RT= item to the <= line, giving the time it | |
1910 | actually took to receive the message. | |
1911 | ------------------------------------------------------------------------------ | |
4990831e PH |
1912 | |
1913 | (333) 06-Jun-05 L Re-think and re-implement header handling | |
1914 | ||
1915 | There are a number of items related to headers above. Better facilities for | |
1916 | handling headers at ACL time are needed. The whole way in which Exim handles | |
1917 | headers should be re-planned and re-implemented in a more consistent manner. | |
1918 | ||
1919 | These are the main previous items: | |
1920 | ||
1921 | Exim 3 Wish List: 41, 85, 149, 187. | |
1922 | Exim 4 Wish List: 55, 62, 63, 160, 212, 237, 270, 314, 328. | |
1923 | ------------------------------------------------------------------------------ | |
2db98699 PH |
1924 | |
1925 | (334) 07-Jun-05 M Support for messages larger than 2G | |
1926 | ||
1927 | This is probably a longish-term thing at the moment. Quotas over 2G are now | |
1928 | supported, but not individual messages; no doubt one day this will be wanted. | |
1929 | ------------------------------------------------------------------------------ | |
8783ca69 PH |
1930 | |
1931 | (335) 14-Jun-05 T Re-arrange default configuration | |
1932 | ||
1933 | A small niggle which might be worth fixing is the ordering of the ACL in the | |
1934 | default configuration file. The relay_from_hosts and authenticated clauses | |
1935 | would be better off before the dnslists examples. However, this should be left | |
1936 | until a x.x0 release, because of the documentation implications. | |
1937 | ------------------------------------------------------------------------------ | |
4aac9b49 PH |
1938 | |
1939 | (336) 16-Jun-05 M Show recipient(s) after header check failure | |
1940 | ||
1941 | The mainlog line for "There is no valid sender in any header line" shows the | |
1942 | sending host and the envelope sender, but does not show any recipients. There | |
1943 | has been a request to show recipients. Presumably this should be on some new | |
1944 | log selector, and it must have a cutoff maximum number of recipients. NOTE: the | |
1945 | data in the reject log does show the envelope recipients as part of its | |
1946 | additional data. | |
1947 | ------------------------------------------------------------------------------ | |
14c6eb72 | 1948 | |
128376c1 | 1949 | (337) 29-Jun-05 S Add "defer" to $recipient_verify_failure |
14c6eb72 PH |
1950 | |
1951 | This is for when defer_ok was set when verifying recipients. Since this isn't | |
1952 | for a failure, we probably also need "ok" for the non-fail case. | |
1953 | ------------------------------------------------------------------------------ | |
128376c1 PH |
1954 | |
1955 | (338) 14-Jul-05 M Change to Bind 9 API | |
1956 | ||
1957 | Exim uses the original API for calling the DNS resolver. There is a newer API | |
1958 | available, and noises are being made in some OS that compatibility with the old | |
1959 | API is going to be dropped. Nevertheless, there are sure to be systems about | |
1960 | for ages that require the use of the old API. Therefore, we will have to | |
1961 | implement not only an interface to the new API, but a backwards compatibility | |
1962 | feature. It would be nice if this was automatic. | |
1963 | ------------------------------------------------------------------------------ | |
b113f04f PH |
1964 | |
1965 | (339) 28-Jul-05 S Log name of maildir file | |
1966 | ||
1967 | This wish is for an option to log the name of the file that is written in | |
1968 | maildir format (e.g. time.pid.host). | |
1969 | ------------------------------------------------------------------------------ | |
aa2b5c79 PH |
1970 | |
1971 | (340) 30-Aug-05 M Match more than one item | |
1972 | ||
1973 | match_address, for instance, matches one address to a list. The wish is to be | |
1974 | able to supply two lists; for each address in the first list, search the | |
1975 | second. Maybe something like ${match_any{...}{...}} is needed. | |
1976 | ------------------------------------------------------------------------------ | |
1977 | --- HWM 340 ------------------------------------------------------------------ | |
e05f33e0 | 1978 | ---------------------------- End of WishList --------------------------------- |