1
* libESMTP 0.8.10 development release. 2002-01-29
3
- Usual autoconf stuff, see ChangeLog for details.
5
Added an NTLM authentication module. Currently this requires OpenSSL to
6
build. This has not seen much in the way of testing as I don't have
7
regular access to a server which requires NTLM authentication for SMTP.
8
However it does generate the correct responses for the test cases I have
9
tried. Feedback on the success or otherwise of this module is solicited.
11
Compilation with --enable-more-warnings=picky seems to be clean again.
13
* libESMTP 0.8.9 development release. 2002-01-02
15
- See ChangeLog for details.
18
The use of libltdl is now deprecated in favour of dlopen(). libltdl
19
is no longer distributed with libESMTP reducing tarball size. This
20
change simplifies installation for the majority of users, however
21
users with platforms which do not supply dlopen or libltdl must now
22
obtain and install libltdl seperately.
25
Building with --enable-more-warnings=yes/picky might prove akward.
26
Recent glibc versions seem to have changed their mind about the
27
status of strcasecmp and friends to being GNU extensions.
28
Naturally, autoconf 2.13 detects the functions in the library but
29
not that their declarations are unavailable. For this reason,
30
_GNU_SOURCE is defined on gnu type platforms but this might cause
31
inconsistent pointer declarations wrt. signedness, YMMV. If you
32
have problems, try ./configure --disable-more-warnings.
35
Added tentative support/hack for the non-standard AUTH= syntax in
36
EHLO responses. It might work. Don't complain to me if it doesn't.
37
You need to ./configure --enable-nsauth for this support.
38
This syntax was only ever described in internet drafts and never
39
made it into RFC 2554. It should *never* have been deployed on the
40
internet. Internet drafts are deleted after 6 months and after
41
publication of RFCs. So there is *no* documentation for this syntax
42
and I can't even begin to guess what it is supposed to be or what
43
implementation errors there are wrt these unavailable documents.
44
My advice is if this hack doesn't work, complain to your ISP and
45
recommend that they deploy MTAs that are standards compliant.
46
Documentation exists for standards and I am happy to make sure
47
libESMTP complies with documents I can actually obtain.
49
* libESMTP 0.8.8 development release. 2001-11-30
51
- See ChangeLog for details.
53
o Fixes more autoconf issues.
55
o Fixed a type mismatch that prevents compilation on some systems.
57
* libESMTP 0.8.7 development release. 2001-11-7
59
- See ChangeLog for details.
61
o Fixes minor build issues.
63
o Improved error handling wrt getaddrinfo
65
* libESMTP 0.8.6 development release. 2001-10-17
67
- See ChangeLog for details.
69
o Fixes minor build issues.
71
o SASL CRAM-MD5 builds without OpenSSL
73
* libESMTP 0.8.5 development release. 2001-10-04
75
- See ChangeLog for details.
77
o Header code no longer enforces presence of recipient fields.
79
o Fixed some build issues related to the automake/libtool interaction.
80
Reverted to autoconf 2.13
82
o Removed support for gethostbyname resolver interface. Please
83
refer to the 'Dependencies' section in README.
85
o Enhancements to STARTTLS support.
87
o Calculation of current timezone's offset from GMT (UTC) is now
88
portable and thread safe.
90
* libESMTP 0.8.4 development release. 2001-08-13
92
- See ChangeLog for details.
94
* libESMTP 0.8.3 development release. 2001-07-06
96
- See ChangeLog for details.
98
o Support for sendmail's XUSR extension.
100
o Fixed a bad bug which caused connections to the server to be dropped
101
depending on the amount of buffering provided by the server.
103
* libESMTP 0.8.2 development release. 2001-06-26
105
- See ChangeLog for details.
107
o Added lots of assertions in the code.
109
o Fixed a bad dangling pointer bug that could strike when sending
110
messages with lines > 510 characters.
112
o Fixed a polling bug that could cause deadlock.
114
o Resolver interface now uses Posix standard getaddrinfo.
115
Use of gethostbyname is deprecated.
117
Please note that the current RFC 2822 header API is adequate but
118
incomplete; for example, interactions between certain headers are not
119
implemented. This will not change for a while. The current priority is
120
to make the protocol engine robust.
122
* libESMTP 0.8.1 development release. 2001-06-15
124
- See ChangeLog for details.
126
Fixed two uninitialised variable bugs that might cause the protocol
127
to quit without sending anything to the server.
129
Enabled many more compiler warnings when compiling with gcc. Compiles
130
should now be much cleaner.
132
* libESMTP 0.8.0 development release. 2001-06-12
134
- See ChangeLog for details.
136
The libESMTP feature set and API for version 1.0 is more or less complete.
137
There have been minor changes to the arguments or semantics of some of
138
the API functions, particularly wrt. the callback functions. Applications
139
using previous libESMTP versions will need to be recompiled or relinked.
141
From this point on no new features will be added and, as far as possible,
142
API changes will be resisted. Having said that, the range of error codes
143
will likely be expanded. Effort will now be directed at bug fixes and
144
improving the documentation and web site, though this is likely to be a
147
Many of the supported SMTP extensions have had only superficial testing
148
mainly due to lack of access to servers supporting them. Developers using
149
libESMTP are encouraged to test extensions against servers to which they
150
have access and to submit bug reports to <brian@stafford.uklinux.net>.
152
The libESMTP web site will be updated in the near future to set up
153
(finally!) mailing lists and bug tracking. In addition the web site will
154
link to projects using libESMTP. If you would like a mention for your
155
project, drop a line to <brian@stafford.uklinux.net> with the details.
added
removed
NEWS
