I am not one to bash Microsoft usually, and I don't intend to here either,
but I have to give some credit to the argument here...

I AM the sysadmin for the system at my office, and I had this same
"non-forwarding" issue for my rules that I have been trying desperately to
troubleshoot for about 6 hours today. I finally found the setting to change
on my Exchange server based on another post in this forum.

I have 2 issues with this...

1) It's not necessarily bad to have the "forwarding" disabled on the server
(relaying can be a major issue), but that fact needs to be disclosed to the
Exchange sysadmin ahead of time, not waiting until he can't get something
done and has to waste an entire day of troubleshooting and web searching to
find the answer.

2) Why on EARTH can't the client receive a message when the rule fails that
says... "Relaying is disabled on the Exchange Server". That alone would have
saved me about 5 hours today. Instead, nothing happens. The rule actually
works, but the server just drops the message and doesn't give any input
whatsoever back to the user to let them know that it failed. That is an
issue with the Exchange server, and Microsoft's lack of user accountability.
--
-jcvader99


"Brian Tillman" wrote:

Conrad Gotzmann wrote:

This is a Microsoft Issue. To make software for people or as
Microsoft claims "poeple ready software" users need to be notified
that the System admin has not enabled what you are trying to do and
suggest a course of action the user should take.

Not at all. That is up to the company to issue policies to the employees
stating what to expect.
--
Brian Tillman