 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Home > Products > Windows > BounceStudio Enterprise > Upgrade Notes
|
|
| |
BounceStudio™ Enterprise - Upgrade Notes
If you’re upgrading from a previous version of BounceStudio Enterprise, then
please read these upgrade notes first.
NOTE: BounceStudio 3.x (pre 3.5) users can skip to Item 8 below.
BounceStudio 3.5+ users (including 4.x users) can skip reading this document.
- BounceStudio 2.x Users – BounceStudio Enterprise 3.5 can not run side-by-side on the same machine with BounceStudio Enterprise 2.0. Do not install BounceStudio Enterprise 3.5 onto your "live" system unless you're ready to upgrade right away.
- BounceStudio 2.x Users – BounceStudio Enterprise 3.5 requires a new unlock code if you’re currently running BounceStudio Enterprise 2.x. An unlock code can be purchased from our website at http://www.boogietools.com/sales/.
- BounceStudio 2.x Users – When upgrading, we recommend installing into the same folder that your current version of BounceStudio Enterprise exists in.
- BounceStudio 2.x Users – When upgrading, make sure your current BounceStudio Enterprise Bounce "Service" is stopped.
- BounceStudio 2.x Users – If you were using the MessageArchiveOff feature then you will need to reset this because this INI setting has changed to another name. You can set this from the BounceStudio Admin - Global Settings - Advanced Settings screen. If you're not sure what this setting is, then you're probably not using it.
- BounceStudio 2.x Users – If you were using the #RETURNEDTO# BounceStudio Variable then you will need to update their SQL statements with the new replacement variable #TO#. If you're not sure what this setting is, then you're probably not using it.
- BounceStudio 2.x Users – If you were using the #RETURNEDTO# BounceStudio variable then you will need to re-enable this functionality after installing. The "ReturnedTo" INI setting is no longer used. To re-enable check the appropriate check box on the Global Settings - Advanced Settings screen. If you're not sure what this setting is, then you're probably not using it.
- BounceStudio 3.x (pre 3.5) Users - When upgrading, we recommend installing into the same folder that your current version of BounceStudio Enterprise exists in.
- BounceStudio 3.x (pre 3.5) Users - When upgrading, make sure your current BounceStudio Enterprise Bounce "Service" is stopped.
- BounceStudio 3.x (pre 3.5) Users – BounceStudio Enterprise 3.5+ includes several new bounce type return codes (see below). Make sure you are handling them in your SQL code, or backend processing code that you may have written.
Type – "Bounce Description"
----------------------------------------
SBDF – "Soft Bounce - Dns Failure"
SBMF – "Soft Bounce - Mailbox Full"
SBMS – "Soft Bounce - Message Size To Large"
MBKS – "Mail Block - Known Spammer"
MBSD – "Mail Block - Spam Detected"
MBAD - "Mail Block - Attachment Detected"
MBRD – "Mail Block - Relay Denied"
CR – "Challenge-Response"
- BounceStudio 3.x (pre 3.5) Users – See the BounceStudio help file "glossary of terms" for descriptions of the new bounce type return codes.
- BounceStudio 3.x (pre 3.5) Users – If you are storing your bounce data in a database table, then you may want to verify the data type size of the field where you store the Bounce Type value. In the past, our bounce codes were only 2 characters in length. As you can see in item 10 above, we now have bounce codes that are 4 characters in length. If you made your Bounce Type field 2 characters in length in the past, then you’ll definitely want to increase the length of it.
|
|
|
 |
|
|
|
|
|
