MAIL

Limitations and known problems
SwiftFile creates a separate preferences profile for each replica of a user's mail database. The separate preference profiles allow the user to set his or her SwiftFile preferences on a replica-by-replica basis. However, this may cause confusion when using clustered servers. When a mail database first fails over to a second mail server, the SwiftFile buttons will disappear because SwiftFile has not been explicitly enabled for this second server. The SwiftFile buttons can be brought back by enabling SwiftFile in the SwiftFile tab of the mail preferences dialog (Actions -> More -> Preferences -> SwiftFile.

SwiftFile cannot read desktop private folders. If there are desktop private folders in a mail database, SwiftFile will not suggest filing messages into these folders even if the choice of folder appears obvious. Private folders that are not stored on the desktop work as expected.

The SwiftFile buttons are part of the mail header that is displayed with each mail message. If the sender of a message requests that the mail headers be hidden, then the SwiftFile buttons will also not be visible.

SwiftFile is continuously building a model of how the user files e-mail. In rare instances, this model may become out-of-sync with the user's recent mail-filing habits. The "Rebuild Index" button on the SwiftFile preferences dialog requests SwiftFile to rebuild its user model from scratch and therefore can be used to resync SwiftFile's user model with recent user activity. The Rebuild Index button can also be used to repair SwiftFile's data files in the unlikely event that they are corrupted.