Forward email rule not working.

[Guest]

I am trying to forward all inbound email as a server based rule.
I am using rules and alerts from outlook 2003.
I apply the rule to all inbound email by not selecting any conditions.
I have tried using the redirect rule or forward rule. I then select the
email address which is a external internet email address.
I make sure the rule is enabled.
I then send a email to the person and nothing happens except the email is
delievered to the inbox.
How can I trace what is happening. ?

 

[Hal Hostetler [MVP-P/I]]

In this context, In guessing an Exchange Server. If so, this is a server
setting that needs adjusting:

http://support.microsoft.com/kb/266166/en-us
Automatic replies and automatic forwards to Internet recipients are disabled
in Exchange 2000 Server and in Exchange Server 2003

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP- Print /Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

 

[Guest]

It would be nice when I created the rule using an internet address I would
have been notified as to this restriction. I guess thats not Microsofts
thinking.

But that this worked.

 

[Brian Tillman]

It would be nice when I created the rule using an internet address I
would have been notified as to this restriction. I guess thats not
Microsofts thinking.

The default that automatic replies (like the OOA) and forwards to outside
addresses do not work is documented, but it is totally up to the Exchange
admins whether this default is enabled or not, so it has nothing to do with
"Microsoft's" thinking, and everything to do with the thinking of the
Exchange admins.

 

[Guest]

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. Instead Microsoft keeps missing the point that people need to
use software and continue to keep users in the dark unless they keep up with
tech notes etc. Business people need to do there jobs not figure out how to
make software work, and system admins need to provide solutions for business
needs not patching and fixing software problems. Thanks for your input.

 

[Brian Tillman]

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.

 

[Guest]

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.