I just ran across that myself. The policy from a trusted domain was pushed
down to our domain. It's a total cluster...... Our local domain is in a
trust with Corp, totally different forest, etc. All the WS are in the corp.
domain but access all the local servers in our local domain..... Don't even
ask. I had to go in and uncheck automatically update email addresses and
whack all the entries and manually create them. Not fun!
M
----- Original Message -----
From: "Michael B. Smith" <[EMAIL PROTECTED]>
To: "MS-Exchange Admin Issues" <exchangelist@lyris.sunbelt-software.com>
Sent: Friday, May 23, 2008 8:26 AM
Subject: RE: Exchange 2003 Recipient Policy Issue
I would be most interested to know how that happened. You can't do that
using the GUI.
Regards,
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
-----Original Message-----
From: JB [mailto:[EMAIL PROTECTED]
Sent: Friday, May 23, 2008 11:12 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 Recipient Policy Issue
All-
We have a customer that is using E2K3 and I'm looking through their
recipient policies and I noticed that in most of their policies that they
have two primary smtp addresses and it's causing conflicts with other
applications from what I'm told.
Is there a way to demote an email address to become the secondary smtp
address?
Thank you,
_____________
John Bowles
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~ http://www.sunbeltsoftware.com/Ninja ~
