Hi All, I'm trying to setup an auto-reply rule on a mail-enabled Public Folder and all is working well with internal email addresses (eg. when a user within the organisation emails the public folder they get an auto-reply) but for users outside the organisation no auto-reply is received. I've gone over various Google results and they all say the same thing - ensure 'Allow Automatic Replies' and 'Allow Automatic Forwarding' under Organisation Configuration > Hub Transport > Remote Domains is enabled. All this is setup correctly (as far as I can tell). Any ideas what other things I should check for this to work? On a side note, I've noticed something in EMC that doesn't look right on the configuration of the Remote Domain, see below: Compare the one on the left (from our Exchange environment) to the one on the right (from the following MS article: http://technet.microsoft.com/en-us/library/aa996309(EXCHG.80).aspx) - the title of the second tab is different (and doesn't make sense to me) and the 'Display senders name on messages' option has a corrupt character. Has something become corrupt in Exchange or is this correct? Thanks for any help, Matt

Matt, Did you track auto reply message for external sender, Did you track in message tracking. I have seen some organization use spam engine and for outbound mail and disable OOF/autoreply for external sender. Can you check this kind of setting in your side.Anil

I've just tried this and it seems they do appear in the tracking logs - but I don't really understand the report and I can't see a way of copying it so you can have a look. Any ideas? Thanks, Matt

I've manually put the tracking log info for one of the messages in a spreadsheet: http://www.omgpm.com/temp/noreply-log.xls Would you mind looking at it and letting me know if there's anything wrong? Thanks, Matt

No one? Any help would be appreciated! Thanks, Matt

I've got the same issue, setup the same as you. If you ever worked this out please let me know. Thanks

Figured it out so I will supply my answer: Did all the above but needed to reboot the server for it to take effect. I read tht all I need to do was restart the Transport service but this hit a snag and then no local clients could send, so I did a reboot and it all came up good. Hope this helps others with the same issue

That message tracking doesnt tell much, all it shows is it was received and submitted to the store but doesnt show it was sent to that domain. When you message track and you see that part you have to highlight it in message tracking click next then click next again. You want to see the eventID transfer and send which will show if it attempted to send to the external domain. Also that screenshot of the remote domain is a mislabeling in 2007.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com