Exchange 2003: Collab/Notification email relay issues

We use Exchange 2003 SMTP email server which is open internally and has relaying disabled.
The portal is installed on internal servers yet is having a problem sending notifications to external email addresses.
In the notification config file there are settings for email servers that have relaying disabled however this functionality doesn't work and the bug ticket for it has been opened for 4 years I'm told.
I'm wondering how smaller companies (<2000 employees) handle this issue.
Do you:
*enable relaying on your main email servers?
*setup a notification specific SMTP server?
*use a 3rd party email company?
What steps are there to reduce the threat of spammers and blacklists while still allowing email to be relayed?
I'm trying to work through this with our IT department but the idea of enabling relaying is a very touchy subject here as we have been burned by being blacklisted a few times in the past.
Thanks for any help!
Geoff

After going back and forth with Plumtree support for about 3 weeks we have solved the problem.
The problem came from a misunderstanding on what needed to be relayed. It turns out that external relaying is not needed, but internal relaying is.
Explicitly granting trust to the notification server allowed emails to begin flowing.
Geoff

Similar Messages

Exchange 2003 push notifications not working on iPhone4 running iOS 5

My Exchange 2003 push notifications are not working on my iPhone4 (iOS5). For this account I need to fetch. I know that at one point I was receiving push notifications from the Exchange 2003 account prior to upgrading to iOS 5 but unfortunately I did not actively monitor push notifications for this accout prior to upgrading to iOS 5. Push notifications work fine for other email accounts on this phone including an Exchange 2007 account. Are there any issues specific to iOS 5 and Exchange 2003 with regard to push notifications?

This is an issue that a lot of people are having... it's all on this thread.
https://discussions.apple.com/thread/4345374?start=0&tstart=0
The 'fix' that is decribed in the first post does not work. The only workaround is if you are on Wi-Fi, turn off Cellular Data and then reset the push service by turning on Airplane mode for a few seconds and then turn it back off. Seems to be an issue with the iOS talking to the new LTE CDMA chip on Verizon and Sprint iPhone 5s.

Exchange 2003 to 2010 migration mailflow issue

Hello,
I have a server 2003 w/ exchange 2003 that we are upgrading to 2010 to support Outlook 2013.
So we installed a windows 2008 server and exchange 2010. We followed a guide to help with the different steps and didn't have problem or error until now.
So what we have right now, is exchange 2003 with still ALL mailboxes.
Replications of folders is done.
Policies are updated.
The firewall is forwarding port 25 to the new exchange 2010 server:
Emails are coming in fine.
Internal emails are also perfectly fine (from internal user to internal users).
the only thing that is giving us trouble is the emails coming out. None of them are going out and they are getting "stuck" in the "routing group connector" on the 2003 machine.
The 2010 exchange has a simple send connector set SMTP/* with this server as source. The 2003 exchange only had the exch2003-exch2010 connector.
Because emails were kind of accumulating (80+) I decided to take the send connector on the 2010 exchange out. and added back a send connector on the 2003 exchange. This kind of "fixed" it as now all emails are going just fine. It also fixed
the queue as part of it got liberated when I added the 2003 send connector.
I still have 25 emails stuck in this "routing group connector" that I'd like to take care of.
We are obviously not done with the migration and this coexistence phase as actual mailboxes still need to be moved.
So I'd like to take care of this queue in the routing group connector as well as continue the process of being able to receive and send from the 2010 machine only. then I would continue the migration process.
FYI, the 2003-2010 connector was created using power shell on the 2010 machine. I am not using any smarthost.
and the error message (in the queue) I get is: "unable to bind to the destination server in DNS"
FYI, my 2003 server is called "SERVER1" and the 2010 server is "SERVER2", they're on the same local domain company.local.
FYI (not sure if that's relevant), the server1 exchange has a different certificate (different domain name) than the new server (server2) as our web host finally allowed us to use subdomains. not trying to confuse anyone but I am really stuck there and maybe
this is related: certificate for the exchange 2003 machine: www.company-mail.com (only 1) and certificates for the exchange 2010 are: mail.company.com / autodiscover.company.com (and a legacy.company.com we may not need since the actual coexistence phase will/should
be short).
any idea what's wrong here?

I added back the send connector on the 2010 exchange. everything still works fine since I still have the send connector on the 2003. However...
I connected through telnet to server2 (the exchange 2010) and was able to mail internally. however I couldn't send mail externally, it gives me a "cannot relay" error when I enter my rcpt to:... command.
I am guessing that this may be the reason why the queue is not emptying itself through that send connector.
Anything else I could try to test my "send connector" on the 2010 exchange?

Ipad and exchange 2003 downloads all email every time and is very slow. We get "no sender" dated 1/1/70 during process.

Ipad has become very slow to sync with exchange 2003. suspect IOS releases have IPad beyond older exchange software but need to understand why sync email is so slow and seems to re-download entire mailbox every time sync runs. Android phones do not have the issue, only ipad. ipad are up do date, mix of 1,2 and new

i have two iPads running different mail, one is my work gmail, one my personal mail. Upgraded my personal mini iPad to iOS 7.1.2 and started getting emails dated 1/1/1970, no sender no content coming I daily, the disappear after a few seconds.
on my other work iPad I haven't upgraded yet am still on iOS 7 but it stopped syncing my email on Friday. I generated a new google password and entered it and when my mail came in there were many emails dated 1/1/1970 with no sender or content, again they disappeared a few seconds later.
What's going on with the mail?

Exchange 2003/2010 Coexistance - User login Issue

Hello
We have deployed Exchange 2010 SP3 in coexistance with 2003 and created connectors.
2003/2010 both Users are not able to login on 2010 OWA and error showing that username/PW is wrong although they are working on OWA 2003 perfectly.
When i add the same user to the local admin group on the Ex2010 server, it works fine with email send/receive. i am confused please suggest what i am missing....Regards
Waseem

Hello
This is the error that occured during that time.
SACL Watcher servicelet encountered an error while monitoring SACL change.
Got error 1722 opening group policy on system SERVER.DOMAIN in domain MYDOMAIN.
Event ID 6003
Source : MSExchange SACL Watcher
i am not sure if its related to this problem.
Secondly i have also tested to run the "Microsoft Exchange Active Directory Topology Service" with a new user having all the rights of exchange & AD groups but its showing giving the error that it cant run the dependency
services. currently this service is running with the local account rights.
I just add the test users (moved from 2003 and new user created in 2010) to the local admin group and it works fine, please give any idea what may be the problem in rights or something else ??
Regards
Waseem

Having problems connecting iPhone 5 with our company's Exchange 2003. Is this a known issue and is there a fix?

I'm not the only one in our company experiencing this, so far i haven't heard of anyone with an iPhone 5 who is able to connect. I'm wondering if people in other companies that have Exchange 2003 also have the same issue or is this isolated to ours.
The errors i get are not being able to verify: "Unable to verify account information." This used to happen before but when i chose to save settings, it would usually work after a while. But this time, with the iPhone 5, i kept getting "Cannot Get Mail" "The connection to the server failed".
I did this with a restore from back up, and a wiped phone, same results. My colleague with a fresh out of the box phone with no previous IOS backups, also has the same errors.
So, anyone else still using Exchange 2003 and experiencing the issues?

Hi Guys,
I got exchange mail working. It seems issue is around "Push". I enabled "push", account verified & all worked well. After that I disabled push (I do not want it & to save mobile data use).
By googling, I found many have got it up & apple may fix it in it next iOS udpate.
Regards,
Mathew

Exchange 2003/2010 Co-Existence - Distribution Group Management

We're running both exchange 2010 and Exchange 2003. I have an issue where some distribution groups were upgraded to Exchange 2010 (v14.0.100) and the manager of those lists who are on Exchange 2003 can no longer modify members, they get the error:
"Changes to the distribution list membership cannot be saved. You do not have sufficient permission to perform this operation on this object".
We've already implemented the myDistributionGroupsManagement role with success to allow Exchange 2010 users to manage their own list without allowing them to create new ones.
http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx
Trying to apply the "Default Role Policy Assignement" to the exchange 2003 users returns an error. Is there any way Exchange 2003 users can manage Exchange 2010 Distribution list they owned without being upgraded to Exchange 2010? If not, is
there any way to downgrade distribution group to Exchange 2003 once they've been upgraded?

Hi,
From my lab, legacy exchange user can manage the distribution group which has been upgrade to Exchange 2010.
Exchange 2010 sp2, Exchange 2003 with sp2.
I can add/remove member for distribution group from address book via outlook.
Xiu Zhang
TechNet Community Support

Exchange 2003 Email Notifications

What's the story with not getting email notifications with the Droid X? Thsi is a very basic function and I see lots of posts regarding this issue but no resolutions.
When will this be fixed? Touchdown or using other third party apps is not the fix I'm looking for

I have read that this is one of the things that might be delaying the deployment of 2.2.: there were some issues with Exchange interfacing generally, especially with Exchange 2003. I believe Motorola (perhaps working with Verizon) is doing extra testing to make sure everything works well before they release 2.2. My point here is that your concern is one of the main things addressed in 2.2, I believe. The latest reports suggest that we should have it by sometime in September if not late August.
In the meantime, enjoy the wonderful other aspect of your phone!

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Forward exchange 2003 Relaying denied

Hi, I've tried to do the following steps
Forward exchange 2003 email to external account such as hotmail, yahoo, gmail
Simple step by step instructions to forward an exchange email to external email:
Step 1. Create new contact with external email address
1. On your exchange server, open active directory users and computers.
2. Right click users OU, point to new and click on contact.
3. Type the fill the user's information (first/last name) and click next.
4. Click modify and choose SMPT address.
4. Type the external email address and click ok and than click finish.
Step 2. Forward the internal email to the external email
Contact you created in step 1 will send the emails to the specify email address. All you need to now is to forward the exchange account emails to the contact. You can forward the emails or forward and leave a copy on the server for the local account.
1. On your exchange server, open active directory users and computers.
2. Select the AD user account, right click and click on properties or double click the account.
3. Click on Exchange General and than click on Delivery options.
4. Check off forward to, and click on Modify.
5. Find and select Contact account created on step 1.
6. Check off "Deliver message to both forwarding address and mailbox".
7. Click OK. Done.
But I've receive this mail while test it
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
Final-Recipient:
Action: failed
Status: 5.5.0
Diagnostic-Code: smtp;550 Recipient address rejected: Relaying denied
X-Display-Name: TecHeader

Hi Aviran,
I have had this problem before and found that the Outlook cache was the issue. might be worth trying this: http://support.microsoft.com/kb/287623
Hope that helps,
Shelly

Exchange 2003 SMTP resolves to incorrect MX record for Outbound emails

Starting October 2007, we have encountered numerous incidents where users complaint that they can not send emails to randomly with Relayed Denied error.
First we thought the problem is with the receipient servers, but after reviewing the SMTP log intensively, I have noticed that the SMTP service on Exchange Server 2003 SP2 tries to send out emails to wrong IP Addresses (instead of sending out to listed IP of MX record, it tries to send to primary domain IP address).
To test further, we have changed the DNS server of the Exchange Server to public DNS service provided by the ISPs and still received same result.
If the user tries to send the email again (from the bounced back message), it some times goes through.
Has anyone know what the problem is?
Have checked the server configuration, DNS configuration, ran all updates, and yet still same result. Is one of the Microsoft Updates causing this issue?

Here is the official explanation i got from MS, sounds like it is doing what they expect it to do.
Problem Description
When Exchange 2003 sends e-mail to the Internet using DNS to resolve external domain names a DNS query is done for the remote domain's MX records. In the event that the initial MX query returns a "server failure", Exchange 2003 will fall back to a DNS A record query. If this query is, in turn, successful and there is an A record for the domain in question that happens to be listening on port 25, Exchange will make a connection to that server. However, if this server does not relay, or accept e-mail for the intended domain a NDR will be generated with a 5.7.1, or
5.5.0 error message.
There are several domains that have A records that point to IP addresses that accept connections on port 25, but do not relay for the same name space:
Eg: Mindspring.com; Earthlink.net
Resolution
Resolve the DNS resolution problems that are causing occasional MX record failures.
Examples:
1. The Exchange server has multiple default gateways set on a multi-homed server.
This is not a recommended configuration and can cause a number of unexpected network problems. If the internal DNS server the internal NIC points to cannot resolve external DNS queries, this problem can occur.
Action: remove the default gateway from one of the NICs.
This doesn’t applies to us, as we don’t use Internal DNS
2. If the Exchange server points to multiple DNS servers on TCP/IP properties, or on the SMTP Virtual Server properties, verify that each of these DNS servers will return MX records properly. If one of the DNS servers does not return DNS records consistently, rectify this problem.
Action: remove this DNS server from the external DNS tab.
Workaround:
Bypass DNS by creating a SMTP connector with address space of <domain.com> and forward to smart host as the IP address the MX/A points to.
Exchange Query Explained
1. If Exchange finds the MX record(s) for a remote domain (through DNS query) it will not fall back to an A record query in the event the MX record (more precisely, the A record the MX record points to) is temporarily not responding on port 25. Instead, Exchange will try another MX record if one exists. If no other MX records exist and none are responding on port 25, the queue will go into a retry state for this remote domain. When that retry state has expired, Exchange will again attempt to resolve MX records for this domain, and so on.
2. Exchange will fall back to an A record query for the remote domain in the event that no MX record can be found. This is not to say that the MX record does not exist - only that when Exchange issued a DNS query for the remote domain the DNS response was "server failure", which basically means no MX was found. So, the MX record may indeed exist, but Exchange simply could not find it through DNS resolution.
3. Exchange then queries the A record and this happens to return a result. If the A record is listening on port 25, but does not accept mail for <domain.com> then we will get the NDR with 550 5.7.1 unable to relay (or some variation of this NDR error code) when Exchange connects and attempts to send the e-mail.
So, the intermittent nature of the problem is caused by a failure to find the MX record and a success in finding A record. This can happen for a variety of reasons, but it boils down to flakey DNS resolution.
For example:
a. A bad DNS server listed as a forwader on the DNS server.
b. A bad DNS server on the TCP/IP properties.
c. A bad DNS server on the SMTP VS (external DNS servers)
d. Multiple default gateways on Exchange (ie. multiple NICs on different networks, each NIC having a default GW)
A netmon on Exchange will show the failed MX lookup and successful A record lookup; however, it may not be conclusive unless the "bad" DNS server is listed in the netmon trace. For example, if Exchange points to internal DNS server(s) for name resolution and these DNS servers service these DNS queries by Exchange, you may need a netmon on the DNS server(s) as well to determine which DNS server/Forwarder/etc is at fault.
Regards,
Shahul Hameed Dasthagir
Support Engineer | Enterprise Communications Support

Exchange 2003 Permissions Error when attempting to forward emails

Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.

Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not.

I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

Office 2011 is not compatbile with Exchange 2003.
I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
http://answers.microsoft.com/en-us/mac

Account Lockout issue between Apple devices and Exchange 2003

I have been having an ongoing issue for a couple of months with a few different users Apple devices locking out their accounts in AD when they try to authenticate to ActiveSync. This doesn't happen every time they authenticate, it seems to be random,
while the rest of the time they have access to their email. It might occasionally happen with an Android, but not on a repetitive basis like this.
Primarily this has been four different iPads, running different versions of iOS, and an iPhone running the latest release of iOS 7. Other iPhones and iPads function without having the problem, including iPhones on iOS 7.
The user accounts in question are set to never have their passwords expire, but again, they aren't the only users that are set like this, and those other users, even with Apple devices are not having the same problem.
I used NetWrix to trace out the source machine, which is my Exchange 2003 server and times, and I've checked the W3SVC1 log file, and come up with the following as an example with identification details masked:
<internal IP>, <Domain\Username>, 4/30/2014, 8:10:04, W3SVC1, <ServerName>, <internal IP>, 15, 329, 3367926, 200, 0, GET, /exchange-oma/<[email protected]>/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplV50462*****/eb53cd5d5b9fcf40****************-20ef44,
As I was typing this, the owner of the iPad from the log file above came by my desk, so I asked a couple more questions. He's never had another iPad, it's a gen 1, and he's never updated the iOS on it. I know one of the other iPads in question
has the most up to date iOS, and the other one is brand new, replacing one that was broken, but the owner of that one had the same issue on a 3 year old iOS.
There is nothing special about the user accounts, no special privileges or restrictions.
Has anyone encountered this before? Exchange 2003, Server 2003 in a 2008 domain. Promotion to the 2008 domain was 2 years ago.

Hi Brian,
I am so sorry for the delay.
Do you have any progress by now?
Since there are lots of devices which use user accounts to log on, failed logon attempts on these devices could be the cause for account lockout.
If this issue persists, I suggest you refer to these troubleshooting articles below:
Troubleshooting account lockout the PSS way
http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
In addition, you can also get efficient support at Active Sync forum below:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy
Best Regards,
Amy

IPhone 4 OS 4.3.3 Exchange 2003 Calendar issue

I have a user that is reporting the calendar entries on her iPhone (iPhone 4 - iOS 4.3.3) randomly disappears and reappears without any changes being made to the device. The email and contact portion of the device seems to be working fine. User took the iPhone to an Apple store and after some troubleshooting, they replaced the phone. This did not resolve the issue. The Apple tech said it was an issue with the Exchange Server. The user’s account was working fine for months. I disabled and re-enabled the user’s Web Services in Active Directory, no luck.
Why would the calendar be the only service being affected and how do I fix this?

No solution but just want to chime in that I'm encountering similar issues. Updated to 4.3.3 and I can no longer sync my work calendar, Exchange 2003. Connecting to the calendar works but only my sub calendars are recognized. My main work calendar isn't displayed. Various attempts to fix this have triggered a message that server identity cannot be verified. MuSt HaVe ExChAnGe SyNc... Please help.
restored, deleted account and reconnected. Apple says it's an Exchange issue. But I seem to be one of the few that are encountering the issue. Co-workers with lower versions do not have a problem syncing with exchange. Awh...progress

Exchange 2003: Collab/Notification email relay issues

Similar Messages

Maybe you are looking for