dipersp
asked on
NDR when accepting meetings from iPhone in Exchange 2010 on-prem
Server is running Exchange 2010 SP2. iPhone is running 6.1.3.
I have ONE user out of about 50 that is having problems occassionally when accepting (Or denying, etc.) meeting requests from internal users. They get an NDR stating the user who sent the meeting does not exist.
What we're seeing with the NDR is that it's messing up the formating of the original sender's email address. All of our internal users are Last, First in their syntax of display names. The NDR is showing
Last, (First@domain.com)<mailto: first@doma in.com>
What it SHOULD be showing is -
Last, First<first.last@domain.co m>
All email addresses are in the format of first.last@domain.com.
So no idea if it's the iPhone, activesync, what. This isn't happening for anyone else, and the user is fine if they accept meetings from Outlook.
Any ideas?
I have ONE user out of about 50 that is having problems occassionally when accepting (Or denying, etc.) meeting requests from internal users. They get an NDR stating the user who sent the meeting does not exist.
What we're seeing with the NDR is that it's messing up the formating of the original sender's email address. All of our internal users are Last, First in their syntax of display names. The NDR is showing
Last, (First@domain.com)<mailto:
What it SHOULD be showing is -
Last, First<first.last@domain.co
All email addresses are in the format of first.last@domain.com.
So no idea if it's the iPhone, activesync, what. This isn't happening for anyone else, and the user is fine if they accept meetings from Outlook.
Any ideas?
ASKER
Simon -
I don't disagree with you one bit. I've told my clients this for years. The problem is, it's only happening for one user. And he happens to be the boss. If it was happening for everyone, I could get out on that excuse. . .
I don't disagree with you one bit. I've told my clients this for years. The problem is, it's only happening for one user. And he happens to be the boss. If it was happening for everyone, I could get out on that excuse. . .
There isn't much more I can say, because the issue is intermittent. I have seen the issue hit some clients really hard, others didn't see it at all.
What is probably happening is that user is a heavy calendar user and probably has delegates involved. That is the main cause of the problems.
Get the device updated to begin with, see if that helps.
Simon.
What is probably happening is that user is a heavy calendar user and probably has delegates involved. That is the main cause of the problems.
Get the device updated to begin with, see if that helps.
Simon.
ASKER
We're doing more testing this week now that the user is back in the office, but I've come to learn it may not be intermittent. Apparently he rarely uses his iPhone to accept appointments, but it may happen every time he does accept on his phone. You know users, hard to get the facts until we get in there and do it ourselves. . .
First order will be to update device.
First order will be to update device.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Figured out the solution on our own.
6.1.3 is not the latest iOS, so I would update which might improve things. If you are using Activesync you must keep it up to date.
I would also keep this article bookmarked.
http://support.microsoft.com/kb/2563324
Simon.