 |
| |
|
Making messages urgent
An urgent message appears in bold. Where applicable, it also invokes special gateway handling.
To make a message urgent, choose Message > Priority > Priority Urgent with the message open.
Making messages low priority
Some gateways have special handling for low (bulk) priority mail. Check with your administrator to see if making messages low priority is useful to you.
To make a message low priority, choose Message > Priority > Priority Bulk with the message open.
Requesting notification of message receipt
When you send someone a private message, you can make FirstClass send notifications of the message status to your Mailbox. The message is marked as Registered.
To be notified when the recipient reads your message, choose Message > Receipt > Receipt on Read with the message open.
To be notified when your message is delivered to the recipient's Mailbox, choose Message > Receipt > Receipt on Delivery with the message open. This option is useful when the recipient is using FirstClass on another server; it will not work on most other mail systems.
To be notified each time your message is delivered to another server on its route, choose Message > Receipt > Receipt on Route with the message open. This option is useful for detecting problems in multiserver FirstClass mail systems; it will not work on most other mail systems.
Preventing generation of nondelivery notices
By default, FirstClass sends a nondelivery notice (NDN) to your Mailbox when your message cannot be delivered.
If you do not want to receive an NDN for a particular message, choose Message > Receipt > Suppress NDN with the message open.
Setting message sensitivity
Currently, message sensitivity has no effect on how FirstClass handles messages. It is provided as information for the recipient, and could be used by third-party gateways.
By default, messages are assigned normal sensitivity. To change sensitivity, choose Message > Sensitivity, then one of the following:
• Sensitivity Personal
• Sensitivity Private
• Sensitivity Company.
Sending messages
To send your message but leave it open, choose Message > Send.
To send your message and close it, choose Message > Send and Close.
After you send a message, FirstClass adds a postmark icon to the message envelope.
Sending messages later
To close a message and leave it unsent, just close the message window. The message stays in your Mailbox with an unsent flag beside it.
You can open the message later to update and then send it, or simply select and send it.
Unsending messages
In certain circumstances, you can unsend a message. This makes the message disappear from the Mailbox or conference to which you sent it.
Note
Be aware that the message may have already been read.
You cannot unsend a message that was:
• sent through the Internet or a gateway
• moved into a folder or deleted by the recipient
• sent to a user who does not allow you to unsend from her Mailbox.
To unsend a selected or open message, choose Message > Unsend. An unsent flag is displayed beside the message in your Mailbox.
Checking whether messages have been read
FirstClass tracks the history of each message. This history includes when it was created, who has read it and when, and whether it was worked with in any other way (for example, forwarded or copied).
To see the history of a message, select or open the message, then choose Message > History.
In the history window, you can double-click a user's name to see the résumé for that user. If you double-click a gateway (a "Routed to" entry), you will see information about that gateway.
Note
The names of Bcc recipients do not appear in the history, except to themselves and to the message sender.
Mailing files using a MAPI-enabled application
If you have set FirstClass as your default mail client in your general preferences, you can create files in a MAPI-enabled application such as Microsoft® Word, then mail them using FirstClass.
To mail a file from a MAPI-enabled application, choose the application's Send command (often under the File menu) with the file open. FirstClass creates an unsent message with the file attached. If you are not currently connected to a FirstClass server, you will be prompted to log in before you see this message.
|