I have a copier (MFU) in a remote office and users have used it to scan and email to themselves.It worked great until the SP2 of Exchange 2007 was installed, but some reason, it doesn't work any more although there hasn't been any change except Exchange 2007 SP2 installation.Does anyone know why it doesn't work with SP2?I tested sending emails from a workstaton in the remote office via Telnet. It went through the commends and I got 250 Mail queued for delivery. Then the connection was lost after a while.Do I have to creat a Receive connector for this? Thanks for any comments in advance.

On Mon, 25-Jan-10 20:44:02 GMT, Kucheong wrote:>>>I have a copier (MFU) in a remote office and users have used it to scan and email to themselves.It worked great until the SP2 of Exchange 2007 was installed, but some reason, it doesn't work any more although there hasn't been any change except Exchange 2007 SP2 installation.Does anyone know why it doesn't work with SP2?I tested sending emails from a workstaton in the remote office via Telnet. It went through the commends and I got 250 Mail queued for delivery. Then the connection was lost after a while.Do I have to creat a Receive connector for this? Thanks for any comments in advance. Start by looking at the SMTP log files. Do you see the MFU connectingand sending the appropriate SMTP commands? Do they all receive a 2xxor 3xx status? If not, which one's fail (those would have a 4xx or 5xxstatus)?---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

The copier is in the internal LAN? If the mails are sending the internal mailboxes, it wouldn’t require an additional receive connector Please enable the protocol logging on the receive connector, and check the log files after reproduced the issue Please also check the message tracking log for the undeliverable messagesJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

If you are using Forefront (or other AV) on your Hub Transport servers it might be a good idea to check the forefront logs to make sure that a new definition update hasn't changed the behaviour. When we updated to SP2 some missing definition updates were also installed at the same time and we noticed after a while that we had some issues sending large zip files due to some rules that had been added. Hope that helps.