Archive for November, 2012

Known problems in version 7.1.1 of OrganiZATOR

Wednesday, November 28th, 2012

It has been discovered an error in the process of recording new email in dBase, that under certain circumstances, result in a corruption of the associated indexes, so that even if the email is recorded correctly, is unusable because can not be further accessed. The processes susceptible to such corruption are:

Receiving email from the mail server.

– Storing the local copy of outgoing emails.

Save email as draft or as pending shipment.

The issue can be particularly problematic if, as usual, in the configuration of the email accounts, establish to clear the email in the server after it has been received, since the image is destroyed on the server, while the email received becomes inaccessible.

We recommend not to use this service until the next update of the product, in which the problem has been corrected. Otherwise, keep the emails on the server and delete them only after checking that the local copy has been recorded correctly. For outgoing emails, we advise to include sending Bcc to the own mailbox address, as a fallback if fails the automatic storage of the local copy of the sent email.

As a result of corruption mentioned in the process Util-2 -> Check Integrity, appears missed links and orphans Blob objects (missed emails). If you run this option, the dBase integrity is restored, but the missed email become lost permanently. The update that will be released in the near future, includes a mechanism that allows to record these lost emails as external files; files that can then be further imported back into the application. Consequently, if you has suffered some of these losses, we suggest not using the above utility, and wait for the next update to recover the lost emails.

It has also been observed that in Windows 8, the email stored in Zator’s dBase appear as plain text (the body of the email as-is transmitted by the mailer agent). This anomaly does not mean that Zator is being storing incorrectly the incoming email; it is because in the new system, Microsoft has broken backwards compatibility in one of its controls. This anomaly is now corrected in the update that is prepared.

We regret any inconvenience caused to our users and expect that the correction thereof, and the incorporation of improvements and enhancements that have been included in the next version will allow you to continue to enjoy our product.