Canon 3323B001 Installation Guide - Page 113
eCopy Connector for Fax via Microsoft Exchange, About Exchange Environment connection protocols
UPC - 013803103397
View all Canon 3323B001 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 113 highlights
eCopy ShareScan® Installation and Setup Guide | 105 eCopy Connector for Fax via Microsoft Exchange The eCopy Connector for Fax via Microsoft Exchange enables users to scan and fax documents from an eCopy-enabled device through an e-mail-to-fax gateway on the Microsoft Exchange server. To use this connector, you must have a network fax server and the appropriate Exchange server plug-in. The recipient's fax number is included in the To field (on the ShareScan Client) in the format required by the fax server. The server plug-in recognizes the recipient address as a fax number and hands the request off to the network fax server for delivery as a fax. While ShareScan always uses the ShareScan User account information to log on to the Exchange server and retrieve the Global Address List, it sends scanned documents from this account only if the Send from personal account option is not selected. If the Send from personal account option is selected, the connector prompts the user to log on at the device. The Wizard selects the Send from personal account option automatically. Note: The eCopy Connector for Fax via Microsoft Exchange and the eCopy Connector for Microsoft Exchange have many common functions and settings. Where common information exists, crossreferences in this section are to the relevant section of the eCopy Connector for Microsoft Exchange documentation. About Exchange Environment connection protocols The eCopy Connector for Fax via Microsoft Exchange supports four combinations of connection protocols that can be used to connect to your Exchange server, depending on your environment. The Wizard automatically selects the protocol based on the Exchange environment information that you supply. for more information about the available combinations of protocols and the environments in which they can be used, see Table 22.