When someone sends a meeting request from Outlook/Exchange it works fine for some of my users and others get the request as an email - not as a meeting invite and do not get the accept option - what setting needs to be changed?
Subject: Re: Outlook Meeting Invite
Yeah, me too.
I have a PMR opened on this (and have for a long…time). Any ideas?
It appears to happen to us on a reschedule…and the thing comes in as a TNEF attachment that LOOKS like an invitation–but is really just a plain email to Notes.
So far, IBM is claiming that MS is sending the invitation out improperly.
Subject: I would agree IF
it happened to all of my users - it works for some but not others - strange
Subject: Re2; Outlook Meeting Invite (
Same here…one manager gets it fine, another gets it messed up (side question: why do these problems always seem to happen to managers??). It’s extra hard to deal with since the Outlook/Exchange users are at another site and it’s tough getting support moving on that end.
Subject: have you ever figured this out?
Subject: I have exactly the same problem! No ideas??
Subject: Has anyone found the cause of this?
I have the same thing happening, several of the people here receive it fine, but one receives it as an email, no accept/decline. Even the word “Invitation” and the date/time are removed from the subject on this persons message.
I have not been able to find anythng different about his Person document or mail file. If there is something I should check, or something the sender should check in their personal address book. Or any other items to check, please let us know.
Thank you
Subject: Outlook Meeting invites - Any ideas on the cause of this?
Does anyone have any ideas of what causes this?
It is still occurring, but very sporadic and no clear idea of the cause.
Thank you,
Matt
Subject: text/calendar MIME part removed during routing
I have looked at data for this issue previously. What I found was then when the invite first arrives at the Domino server that it does not have a MIME part containing text/calendar data, so Domino is correct in not treating this as a meeting invite.
I do not think that this is a necessarily a problem with the way that Oultook/Exchange SEND the invite. In fact, I had seen it even from a Notes chair. However, someone mucks with the message during routing.
The only case that I know of which does this is when you route through an Exchange 2003 server that does not have Security Update for Exchange Server 2003 Service Pack 2 (KB959897)’ .
I imagine that there are other third party tools (virus scan, archive tools, etc) which try to view the message and may for some reason reassemble it without the correct MIME parts.
Nate
Subject: Thank you, but the issue with the Microsoft Calendar invitations appears more systemic.
Thank you for the information Nate.
It seems odd that this would only effect one or two users consistently, while others consistently get the meeting invite correctly.
Currently, it appears that two of our people will always get it as a message, not invite, while others will always get it correctly.
Thanks again for the suggestion Nate, but I think there is something more systemic occurring.
If anyone has any thoughts on what to look at, it would be greatly appreciated.
Matt
Subject: Re: Outlook Meeting Invite
Hmmm…
It seems like there are some things in Outlook/Exchange that may impact this. I’m not familier with Exchange or with these details in Outlook either–so I may be wrong!
However, I get the idea that Outlook and/or Exchange may have something internally that makes them think they are talking to another Outlook/Exchange user–and, in that case, they do the typical MS thing & send stuff in a proprietary format. Maybe, make sure the users receiving the improperly formatted invitations are not improperly created in the sending person’s contacts (or in the sending domain’s address book).
Subject: SOLVED: The outlook contact seems to be the issue.
The sender removed our employee from her contacts and re-added him, which corrected the issue.
It appears there was something in the contact that was sending it incorrectly. We did not go through every setting, so I am not sure which one created this issue. However, recreating the contact resolved the issue for us.
Thanks to all who posted.
Matt