Hints & Tips

Hints & Tips

Mail settings

1. Only use Simple MAPI for Outlook Express and other applications that can set themselves as the default mail client without having to specify a profile to login as. Even though Outlook can open with a given profile that profile must be specified in the options. For providers such as this use the Extended MAPI functionality.

2. If using Outlook Express make sure it is specified as the default e-mail program (and with Outlook Express 4.0) make sure it is also registered as the default Simple MAPI client. Be careful though, when Outlook Express registers itself as the default Simple MAPI client it replaces the MAPI32.dll with it's own. This will prevent other messaging applications, such as Outlook, from working.

3. Netscape Communicator (or any others derived from the Mozilla code base) cannot be used for reading RemoteCommand emails because its implementation of the Simple MAPI interface does not support the reading of attachments. Netscape Communicator can be used for sending emails (although this is not recommended) but it can corrupt attachments during the attachment encoding phase. Netscape Communicator 4.5 and above allows the user to specify that attachments should always be encoded using Base64 binary encoding, instead of Quoted-Printable. To make the change:
- Shut down Netscape Communicator
- Add the following line to "prefs.js" file.

user_pref("mail.file_attach_binary", true);

Detailed instructions can be found at: http://help.netscape.com/kb/consumer/19990419-6.html

4. If possible create a separate email address specifically for RemoteCommand emails. This avoids accidently deleting or modifying RemoteCommand emails before the Listener has had time to process the email.

5. Although RemoteCommand will handle emails up to around 2GB in size many email providers limit a single email to 5MB. Therefore try and reduce the number of commands sent in a single command email.

6. If it appears that RemoteCommand is 'choking' on a particular email, e.g. an initialization request email from a computer that is not valid, the email may be deleted manually. Two menu options on the File menu, 'Incoming Mail Store...' and 'Outgoing Mail Store...', show the contents of RemoteCommand's local inbox and outbox. Any problem emails may be deleted.

7. If a RemoteCommand email is inadvertantly delivered to a location that RemoteCommand is unable to check, e.g. a non-Inbox folder in Outlook Express, then the email can be processed manually by saving the attachment and using the 'Process File...' menu option on the File menu.

8. Some versions of Outlook Internet Mail Only (IMO) edition do not permit the automated 'flushing' of inbound/outbound email, e.g. Outlook 2000 IMO. In such situations leave the Outlook application open and set it to regularly check for email itself instead of relying on RemoteCommand to perform the email flushing.