|
HP3000 E-Mail Configuration: Clients with OpenDesk
If you are using PC or Macintosh or Unix clients with HPOpenDesk as your server there are a few items which might be useful to understand about the configuration. There are notable differences in capability among the various clients. Among other things the HP provided clients (available with HPOpenDesk II - C.02) support more functionality in relation to your HPOpenDesk server; for instance, access to distribution lists and folders. By contrast, the cc:Mail and Microsoft Mail clients are more familiar to users, and since they support much larger installed bases, are more likely to be enhanced at a consistent rate. Another notable difference is that the cc:Mail and MS Mail clients use a different network interface than do the HP provided clients. As such there are sometimes subtle differences in the ability to pass special (binary) file types. An important aspect of the passing of binary files between Desk users and the outside world (when using the DeskLink gateway) is the automated mapping DeskLink does to convert these files for mail transport. DeskLink must map MPE files (or attached PC files) to MIME data types for transport to remote systems. This mapping is accomplished by a mapping table (pcfiles.data.threek) which maps mpe filecodes to PC file types along with corresponding MIME transport types. This file can be customized on site if needed, but already includes all the file types already recognized by OpenDesk's clients. [OpenDesk uses a similar method to map attached pc files to MPE filecodes and back to pc file types when pc clients read and download files attached to messages.] Note; in the current OpenDesk C.02 release there is a bug [SR#5000713222] which causes the OpenDesk clients to lose "foreign" addresses, thus making them inoperative with any FSC gateway product (such as fax, telex, or our SMTP gateway).
|