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