1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
|
$Cambridge: exim/doc/doc-txt/NewStuff,v 1.33 2005/04/05 13:58:34 ph10 Exp $
New Features in Exim
--------------------
This file contains descriptions of new features that have been added to Exim,
but have not yet made it into the main manual (which is most conveniently
updated when there is a relatively large batch of changes). The doc/ChangeLog
file contains a listing of all changes, including bug fixes.
Version 4.51
------------
PH/01 The format in which GnuTLS parameters are written to the gnutls-param
file in the spool directory has been changed. This change has been made
to alleviate problems that some people had with the generation of the
parameters by Exim when /dev/random was exhausted. In this situation,
Exim would hang until /dev/random acquired some more entropy.
The new code exports and imports the DH and RSA parameters in PEM
format. This means that the parameters can be generated externally using
the certtool command that is part of GnuTLS.
To replace the parameters with new ones, instead of deleting the file
and letting Exim re-create it, you can generate new parameters using
certtool and, when this has been done, replace Exim's cache file by
renaming. The relevant commands are something like this:
# rm -f new.params
# touch new.params
# chown exim:exim new.params
# chmod 0400 new.params
# certtool --generate-privkey --bits 512 >new.params
# echo "" >>new.params
# certtool --generate-dh-params --bits 1024 >> new.params
# mv new.params params
If Exim never has to generate the parameters itself, the possibility of
stalling is removed.
PH/02 A new expansion item for dynamically loading and calling a locally-
written C function is now provided, if Exim is compiled with
EXPAND_DLFUNC=yes
set in Local/Makefile. The facility is not included by default (a
suitable error is given if you try to use it when it is not there.)
If you enable EXPAND_DLFUNC, you should also be aware of the new redirect
router option forbid_filter_dlfunc. If you have unprivileged users on
your system who are permitted to create filter files, you might want to
set forbid_filter_dlfunc=true in the appropriate router, to stop them
using ${dlfunc to run code within Exim.
You load and call an external function like this:
${dlfunc{/some/file}{function}{arg1}{arg2}...}
Once loaded, Exim remembers the dynamically loaded object so that it
doesn't reload the same object file in the same Exim process (but of
course Exim does start new processes frequently).
There may be from zero to eight arguments to the function. When compiling
a local function that is to be called in this way, local_scan.h should be
included. The Exim variables and functions that are defined by that API
are also available for dynamically loaded functions. The function itself
must have the following type:
int dlfunction(uschar **yield, int argc, uschar *argv[])
Where "uschar" is a typedef for "unsigned char" in local_scan.h. The
function should return one of the following values:
OK Success. The string that is placed in "yield" is put into
the expanded string that is being built.
FAIL A non-forced expansion failure occurs, with the error
message taken from "yield", if it is set.
FAIL_FORCED A forced expansion failure occurs, with the error message
taken from "yield" if it is set.
ERROR Same as FAIL, except that a panic log entry is written.
When compiling a function that is to be used in this way with gcc,
you need to add -shared to the gcc command. Also, in the Exim build-time
configuration, you must add -export-dynamic to EXTRALIBS.
TF/01 $received_time is a new expansion variable containing the time and date
as a number of seconds since the start of the Unix epoch when the
current message was received.
PH/03 There is a new value for RADIUS_LIB_TYPE that can be set in
Local/Makefile. It is RADIUSCLIENTNEW, and it requests that the new API,
in use from radiusclient 0.4.0 onwards, be used. It does not appear to be
possible to detect the different versions automatically.
PH/04 There is a new option called acl_not_smtp_mime that allows you to scan
MIME parts in non-SMTP messages. It operates in exactly the same way as
acl_smtp_mime
PH/05 It is now possible to redefine a macro within the configuration file.
The macro must have been previously defined within the configuration (or
an included file). A definition on the command line using the -D option
causes all definitions and redefinitions within the file to be ignored.
In other words, -D overrides any values that are set in the file.
Redefinition is specified by using '==' instead of '='. For example:
MAC1 = initial value
...
MAC1 == updated value
Redefinition does not alter the order in which the macros are applied to
the subsequent lines of the configuration file. It is still the same
order in which the macros were originally defined. All that changes is
the macro's value. Redefinition makes it possible to accumulate values.
For example:
MAC1 = initial value
...
MAC1 == MAC1 and something added
This can be helpful in situations where the configuration file is built
from a number of other files.
PH/06 Macros may now be defined or redefined between router, transport,
authenticator, or ACL definitions, as well as in the main part of the
configuration. They may not, however, be changed within an individual
driver or ACL, or in the local_scan, retry, or rewrite sections of the
configuration.
Version 4.50
------------
The documentation is up-to-date for the 4.50 release.
****
|
