-
Notifications
You must be signed in to change notification settings - Fork 4
/
RELEASE.NOTES
197 lines (156 loc) · 8.43 KB
/
RELEASE.NOTES
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
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
Please see UPGRADING and CHANGELOG for a detailed
explanation of the differences from previous versions.
Summary Changes from 3.10.1 to 3.10.2
=====================================
DSPAM 3.10.2 is a bugfix release that resolves some issues that existed in earlier releases.
- Support for Postgresql 8.1 (EOL) was dropped
- Support for Postgresql 9.1 was added
- Bug in RSET handling during LHLO phase fixed
- Introduced 'TxtDirectory' directive in dspam.conf (defaults to previously hardcoded location)
- Introduced 'GroupConfig' directive in dspam.conf (defaults to previously hardcoded location)
- Various updates to the webui
- Some (potential) memory leaks were fixed
Summary Changes from 3.10.0 to 3.10.1
=====================================
DSPAM 3.10.1 is a bugfix release that resolves an issue with the MySQL driver
introduced in DSPAM 3.10.0.
Summary Changes from 3.9.0 to 3.10.0
===================================
Changing DSPAM license to AGPL v3
Remove support for MySQL < 5.0.0 (EOL)
Add support for MySQL >=5.5.x
Future removal of SQLite2 driver noted
Add dot de-stuffing when receiving message in daemon mode (aka: DLMTP/LMTP) or over socket
and speedup up dot stuffing when sending to LMTP/SMTP delivery
Extensive work on MySQL, PostgreSQL and Hash driver
Remove unused direct dependencies on most of the executables and libraries
Extending delimiters for advanced tokenizers (aka: SBPH and OSB) that profit from more tokens per message
Adding more debug output
Adding HE translation (web-ui)
## Upgrading from 3.9.0 / 3.9.1RC1
- We expect no changes are required to upgrade to 3.10.0
## upgrading from 3.8.0
- Read the release notes from 3.9.0 (see end of this file)
- Read UPGRADING
## upgrading from 3.6.8 or older
- Read all the documentation
- Read the release notes from 3.9.0 (see end of this file)
- Read UPGRADING
What happened to 3.9.1RC1 ?
===========================
3.9.1RC1 was packaged in July 2010. It is now one year later and
a lot of work has been added since the RC1 package.
The DSPAM team feel its more accurate to release our current
status as 3.10.0
Please see CHANGELOG for a detailed explanation of the differences
from previous versions
##################################################################
# Release notes from previous release, here for your convenience #
##################################################################
RELEASE 3.9.0
Why should you upgrade to DSPAM 3.9.0?
======================================
The question of whatever to upgrade and when are always hard ones. You've had
your DSPAM up and running for ages and it's doing a fine job. Now there is this
brand new DSPAM, 3.9.0, and you don't know if you should upgrade, when or why?
We as the DSPAM community can not make that decision for you. You should
carefully read the README and UPGRADING documents and see if an upgrade is
something for you or not. Please allow us to assist you in making that decision
by pointing out some benefits of DSPAM 3.9.0 as compared to older releases of
DSPAM.
Enhanced stability
------------------
We took the time to hunt down and fix most cases of stability issues found in
the older releases of DSPAM. The new DSPAM 3.9.0 has more robust
- character decoding
- HTML mail processing
- memory handling
- storage engines
- SBPH/OSB tokenizing
- and much, much more
Memory handling
---------------
We reduced the memory footprint on many parts in DSPAM. No more restarting of
DSPAM after days of running because of memory leaks. We fixed most of them.
Allocated memory is freed after it is no longer needed. But that's not all. If
you for example use MySQL and you have set 'max_allowed_packet' to a low value,
then DSPAM will honor your decision and use no more then you have told it to
use. Not only MySQL storage driver will honor your database settings but the
other SQL-based storage engines in DSPAM will do the same.
HTML mail handling
------------------
We enhanced the way DSPAM processes your HTML mail. The older HTML processing
engine in DSPAM was replaced with a much better and under certain conditions
faster processing engine. If you receive a lot of mails in HTML then DSPAM 3.9.0
is the best DSPAM you can get today for correctly processing your HTML mail. If
most of your mails are non English then you will love DSPAM 3.9.0. We now
correctly convert most of the special encoded characters found in typical non-
English HTML mails to their proper decoded characters. As a side effect you will
get higher accuracy from DSPAM 3.9.0 as compared to older releases.
Character decoding
------------------
Not only have we enhanced the character decoding in DSPAM 3.9.0, but we've also
took the decoding engine to the next level and improved processing speed
significantly.
Storage engines
---------------
Ever executed something like 'dspam_admin change preference myuser
"trainingMode" "toe"' while using the PostgreSQL driver and then realized that
DSPAM wrote a bunch of non-readable characters in your preference table if the
user "myuser" did not exist before in that table? Done the same with the MySQL
storage driver and realized that there it worked? Well... we fixed those
problems. MySQL? PostgreSQL? SQLite? It's not important which one you use. We
adjusted the SQL-based storage driver to be equal in their cores.
Scalability
-----------
You always wanted to handle more users on your DSPAM installation but you were
limited by the amount of user ID's DSPAM could handle? Not any more! DSPAM 3.9.0
can now handle up to 2,147,483,647 users before it reaches a technical limit on
certain storage engines. But not only has the number of possible users
increased, but also the statistical counters where changed to allow you to store
not less then the double amount compared to older DSPAM releases.
Speed improvement
-----------------
You have read all the above points and are still not convinced that you should
upgrade? Okay. How about the vast speed improvement we have introduced in DSPAM
3.9.0? That should convince you. We speeded up DSPAM everywhere we could without
scarifying stability. We have speeded up character decoding, HTML mail
processing, storage engines, SBPH/OSB tokenizing, buffer management, SQL
queries, the purging scripts and much much more.
Documentation
-------------
We have been listening carefully to the needs of our user base and have updated
the documentation to have more examples and to be more accurate then ever. And
we have documented even more options available in DSPAM which where never
published before.
Additional/enhanced functionality
---------------------------------
Wait! That's not all! We even added new functionality to DSPAM. A brand new
module is introduced in DSPAM 3.9.0 to help you do more versatile and flexible
lookups against LDAP and/or use external programs to do lookups. Have we
mentioned the enhancements and new functions in the training script? Yes! We
have finally added MBOX training. Let's not forget RBLLookups! We enhanced that
as well. And we enhanced SBPH/OSB tokenizing. And we pushed more configuration
options into the preference extension. And we enhanced the output of statistical
data. And, and, and... still not convinced?
Final notes
-----------
Should you upgrade? Why not? DSPAM is free software and there is no price
attached to a new release. You can upgrade to new releases whenever you are
ready to do so. We have taken extra care not to change DSPAM 3.9.0 to render
your old trained data and tokens to be useless. So you can upgrade without
losing your old data (please read the UPGRADING document found in the root
directory of the DSPAM source). We (the core team behind DSPAM) and the DSPAM
community will off course be there to help and assist you in your upgrade to
3.9.0. BUT should you decide to stay on a older version, then this is fine with
us. It's your decision. For us it does not change anything. You can still ask
your questions on the DSPAM user list [1] and/or report your problems in our
issue tracking system [2]. No matter what release of DSPAM you use.
As a matter of course we think that DSPAM 3.9.0 is worth installing. It's the
best DSPAM you can get today. We are very proud of what we as a community have
reached so far in the short time since we took over DSPAM. And we want to share
that positive experience with you. Go and grab yourself a copy of the source or
binary and give DSPAM 3.9.0 a try. You will not be disappointed.
External links:
[2] https://sourceforge.net/tracker/?atid=1126467&group_id=250683&func=browse