If you run across a bug in MailBounce, please submit a report to Smart Mail Solutions, Inc., so that we may fix it in the next release. When reporting a bug to us, please provide the following information:

Your site number (if you are a registered user),
Your machine type and operating system (PowerMacintosh G4 with Mac OS X 10.2.2, UltraSPARC 1 with Solaris 8, etc.),
The version of MailBounce you are running (displayed in your diagnostics file),
A detailed description of the problem encountered.

Ideally, you should always send your diagnostics file, which will aid us in identifying the bug. We might also ask for your bounces file (and/or other relevant files) if we cannot reproduce the bug here. If your bounces file is large, we'll set up an FTP account and drop box on our server for you.

It would also be best if you included your Preferences (.ini) file with all bug reports, so that we can see your configuration settings; if you send your Preferences file, however, BE SURE TO REMOVE YOUR LIST PASSWORD FIRST! There will never be a case where we will need an actual list password, so there is no need to include it; for security's sake, it really should be removed prior to sending the file.

Please send all files as attachments! This helps preserve proper formatting within the files.

Note that unrecognized bounces are NOT considered bugs! Please refer to the New_Bounce form for information on submitting new bounce formats to us. However, improperly classified bounces are considered bugs -- that is, if you notice that a truly "SOFT" bounce is classified as "HARD," please report it as a bug. Also, if a clearly hard bounce is classified as soft, please file a report for that, as well -- but note that there are many arguably hard bounces that are classified soft just to be conservative; if the bounce is not clearly hard, then it is probably classified as soft intentionally.

But when in doubt, inform us of the problem!

[home]

[ReadMe]