Looking for advice on implementing an Exch 2007 Standard server for a client who want to use their ISP spam filtering service. I was thinking having the ISP setup a catch-all account and have the Exch server pop the mail. I belive we will need a third party pop3 connector or seyup the ISP as a Smart Host. Any recoomendations appreciated. If the Smart Host is the best solution, can someone provide details on how to configure. Any responce appreciated.

Exchange 2007 canot retreive mail from your ISP with POP3, for that you need extra software. But why dont you let them filter for spam etc, and then deliver mail to you with SMTP. with that you would get a faster mail transportand with any extra software. You need to create a receiveconnector that your ISP can deliver mail to. For outgoing you can just let your sendconnector use a smarthost (that is your ISP mailserver) or deliver yourself (sendconnector uses MX in DNS)

Dear customer: Thanks for Lasse Petterssons reply. He is right. Microsoft doesnt provide POP3 connector software for Exchange 2007 and it is not a supported configuration. For third party POP3 connector information, please refer to the following documents: http://www.christensen-software.com/popcon.htm http://www.exchangepop3.com/ http://www.mapilab.com/exchange/pop3_connector/ However, you can achieve that, let Exchange server send and receive e-mails via ISP smart host. You need to enable anonymous access on receive connector. Create a send connector for Internal usage, If you select the Internal usage type for the Send connector, you must specify a smart host. When you route mail through a smart host, the smart host handles delivery to the next hop in the delivery destination. You can use an IP address or the fully qualified domain name (FQDN) of the smart host to specify the smart host identity. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart host server. For more information about send connector, please refer to the following documents: Send Connectors http://technet.microsoft.com/en-us/library/aa998662(EXCHG.80).aspx For more information about receive connector, please refer to the following documents: Receive Connectors http://technet.microsoft.com/en-us/library/aa996395(EXCHG.80).aspx Hope it helps. If anything is unclear, please feel free to let me know. Rock Wang - MSFT

Sorry for getting back so late and thanks for your imput. At this stage I have implemented a third party pop3 connector. Intenal mail work fine and receiving of external mail works as well. The sending of email is my problem. Rock, i did go through your check list and want to confirm whether I understand correctly. In regards to the recieve connector, Exchange creates the Client and Default connectors automatically and both have Anonymous checked inPermissions tab. I have not created an additional recieve connector. I have a send connector created, but uncertain on what I should enter for a smart host. My smarthost should be my ISP... correct? FQDN - should this be my external smtp server? Address Space Type set to SMTP and address is "*" Route Mail through the following smarthost - woudl this be the IP address of my ISP or local server? Note: My ISP uses Basic Authenitication and SMTP port 587. Source server is my Exchange server. Hope this helps

Dear customer: If you select the Internal usage type for the Send connector, you must specify a smart host. When you route mail through a smart host, the smart host handles delivery to the next hop in the delivery destination. You can use an IP address or the fully qualified domain name (FQDN) of the smart host to specify the smart host identity. The smart host identity can be the FQDN of a smart host server, a mail exchange (MX) record, or an address (A) record. If you configure an FQDN as the smart host identity, the source server for the Send connector must be able to use DNS name resolution to locate the smart host server. You must select at least one source server for a Send connector. The source server is the transport server to which messages are routed for delivery through the selected Send connector. You can set more than one source server on a Send connector that is configured for the Exchange organization. When you specify more than one source server, you provide load balancing and redundancy if a server fails. The source servers associated with Send connectors that are configured for the Exchange organization can be Hub Transport servers or subscribed Edge Transport servers. The General tab of the Send connector properties in the Exchange Management Console includes an option to Specify the FQDN this connector will provide in response to HELO or EHLO. In the Exchange Management Shell, this property is set by using the Fqdn parameter with the Set-SendConnector cmdlet. After an SMTP session is established, an SMTP protocol conversation starts between a sending e-mail server and a receiving e-mail server. The sending e-mail server or client sends the EHLO or HELO SMTP command and its fully qualified domain name (FQDN) to the receiving server. In response, the receiving server sends a success code and provides its own FQDN. In Exchange 2007, you can customize the FQDN that is provided by the sending server if you configure this property on a Send connector. For more information about Send connector, please refer to the following article: Send Connectors http://technet.microsoft.com/en-us/library/aa998662(EXCHG.80).aspx Rock Wang - MSFT