Is there any way to send Outlook meeting requests from a non-default calendar?


First of all, note that while you cannot have a "full" MAPI connection to more than one Exchange mailbox via a single Outlook profile, you can get awfully close by making one mailbox a delegate. Many users find this works better than what you're currently doing. Instructions on how to do this are located here.

Once you have this setup, when the user wishes to send a message (email, meeting invitation, etc) from the secondary mailbox, she must fill in that user in the From field in Outlook which is also explained in the link above. Note that if follow this technique when she sends as the other account those messages will say "From Userabc on behalf of userxyz". If you wish to change that so they just say "From userxyz", you'll need to give userabc Send As permission on the userxyz mailbox. Instructions for doing this are here.

Richard Beier
Author by

Richard Beier

Updated on September 17, 2022


  • Richard Beier
    Richard Beier about 1 year

    We have a user with two Outlook accounts. [email protected] is of type Exchange; [email protected] is of type IMAP/SMTP. Both are actually on our Exchange server; but since an Outlook profile can only have one Exchange account, the second one is set up as IMAP.

    The user would like to send a meeting request from her account, so the "from" address appears as [email protected]. Unfortunately that doesn't work. If she creates the meeting in her calendar, the meeting request still goes out through her Exchange account, [email protected]. The meeting request "compose message" window has an Account dropdown below the Send button, but this has no effect.

    Before she sends the invitation, a warning appears:

    "Responses to this meeting request will not be tallied because this meeting is not in your main Calendar folder. Is this OK?"

    Is there any workaround for this? We're using Outlook 2007 and Exchange 2003 SP2.


  • Richard Beier
    Richard Beier over 13 years
    Thanks! I'll definitely try this out. We'd need full "send as" permissions, since the recipient shouldn't see at all - but it sounds like this will do what we want.