2 exchange servers, 1 outlook profile?

We have a situation where we have some partners that would like to
access their @mydomain.com while utilizing their own profile to access
their @theirdomain.com. The exchange servers are not connected in any
way. I know that you can only add 1 exchange profile to outlook at a
time (thanks Microsoft for allowing this in Entourage but not in
Outlook!!!), but I know that you can do it if the secondary account is
set up using IMAP. However, our admins do not allow IMAP access. Can
we do this using Outlook over HTTP for the secondary profile? Just
to confuse everyone a little bit more, to summarize: the partner
would be using Outlook, connecting to their own Exchange server
@theirdomain.com, and would add an extra account for @mydomain.com.
We are trying to avoid the need for them to use Outlook for their
@theirdomain.com mail while then using either a separate Outlook
profile for @mydomain.com or using OWA to access their @mydomain.com
mail. The people are using a mixture of Outlook 2003 and 2007. Not
sure what version the servers are, but I would assume that they are
Exchange 2003.

Thanks!!

Mark
Tue Jul 22 15:55:30 CDT 2008

On Tue, 22 Jul 2008 13:37:14 -0700 (PDT), tbrodie@gmail.com wrote:

>We have a situation where we have some partners that would like to
>access their @mydomain.com while utilizing their own profile to access
>their @theirdomain.com. The exchange servers are not connected in any
>way. I know that you can only add 1 exchange profile to outlook at a
>time (thanks Microsoft for allowing this in Entourage but not in
>Outlook!!!), but I know that you can do it if the secondary account is
>set up using IMAP. However, our admins do not allow IMAP access. Can
>we do this using Outlook over HTTP for the secondary profile? Just
>to confuse everyone a little bit more, to summarize: the partner
>would be using Outlook, connecting to their own Exchange server
>@theirdomain.com, and would add an extra account for @mydomain.com.
>We are trying to avoid the need for them to use Outlook for their
>@theirdomain.com mail while then using either a separate Outlook
>profile for @mydomain.com or using OWA to access their @mydomain.com
>mail. The people are using a mixture of Outlook 2003 and 2007. Not
>sure what version the servers are, but I would assume that they are
>Exchange 2003.
>
>Thanks!!

RPC over HTTPS still "counts" as a MAPI profile and as you know you
only have one per profile.
That's it really, not much more to say. You know what you're doing and
are thwarted by muppet policies. IMAP is the way people go any clowns
who don't allow a damn protocol like that OUT and can't even bring
themselves to restrict it (not that you need to) to a given host (i.e.
the actual destination host name) really don't deserve to have jobs,
they piss me off.

Brian
Tue Jul 22 16:02:49 CDT 2008




On 7/22/08 1:37 PM, in article
f58ed8b8-ccbd-4aa2-b304-7312c2956677@56g2000hsm.googlegroups.com,
"tbrodie@gmail.com" <tbrodie@gmail.com> wrote:

> We have a situation where we have some partners that would like to
> access their @mydomain.com while utilizing their own profile to access
> their @theirdomain.com. The exchange servers are not connected in any
> way. I know that you can only add 1 exchange profile to outlook at a
> time (thanks Microsoft for allowing this in Entourage but not in
> Outlook!!!), but I know that you can do it if the secondary account is
> set up using IMAP. However, our admins do not allow IMAP access. Can
> we do this using Outlook over HTTP for the secondary profile? Just
> to confuse everyone a little bit more, to summarize: the partner
> would be using Outlook, connecting to their own Exchange server
> @theirdomain.com, and would add an extra account for @mydomain.com.
> We are trying to avoid the need for them to use Outlook for their
> @theirdomain.com mail while then using either a separate Outlook
> profile for @mydomain.com or using OWA to access their @mydomain.com
> mail. The people are using a mixture of Outlook 2003 and 2007. Not
> sure what version the servers are, but I would assume that they are
> Exchange 2003.
>
> Thanks!!


Of course I manage all the mail servers I talk about, but the easiest way to
do this is to have Outlook open on one Exchange server and then use POP3 to
pull the mail from the other Exchange server and set the destination to be
the Exchange mailbox in Outlook. The downside is that now you're
co-mingling mail though.

/b/b

Mark
Tue Jul 22 16:05:14 CDT 2008


>
>
>Of course I manage all the mail servers I talk about, but the easiest way to
>do this is to have Outlook open on one Exchange server and then use POP3 to
>pull the mail from the other Exchange server and set the destination to be
>the Exchange mailbox in Outlook. The downside is that now you're
>co-mingling mail though.
>
>/b/b

Muppets that don't understand simple directions and don't allow IMAP
outbound are even less likely to be allowing POP3 out.

Michael
Tue Jul 22 16:04:29 CDT 2008

I remember reading a few months ago about someone who wrote a utility that
allowed two copies of Outlook to be opened simultaneously. You could then
have two separate profile, one in each copy of Outlook. I haven't used this
utility and in fact don't even recall the name, but I suppose you could
search for it.

Really though, as Mark said allowing IMAP out to that host would really be
the easiest route to take here.

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:e5ic84llqo25nvgj2acc7a3e92ap7m86kk@4ax.com...
> On Tue, 22 Jul 2008 13:37:14 -0700 (PDT), tbrodie@gmail.com wrote:
>
>>We have a situation where we have some partners that would like to
>>access their @mydomain.com while utilizing their own profile to access
>>their @theirdomain.com. The exchange servers are not connected in any
>>way. I know that you can only add 1 exchange profile to outlook at a
>>time (thanks Microsoft for allowing this in Entourage but not in
>>Outlook!!!), but I know that you can do it if the secondary account is
>>set up using IMAP. However, our admins do not allow IMAP access. Can
>>we do this using Outlook over HTTP for the secondary profile? Just
>>to confuse everyone a little bit more, to summarize: the partner
>>would be using Outlook, connecting to their own Exchange server
>>@theirdomain.com, and would add an extra account for @mydomain.com.
>>We are trying to avoid the need for them to use Outlook for their
>>@theirdomain.com mail while then using either a separate Outlook
>>profile for @mydomain.com or using OWA to access their @mydomain.com
>>mail. The people are using a mixture of Outlook 2003 and 2007. Not
>>sure what version the servers are, but I would assume that they are
>>Exchange 2003.
>>
>>Thanks!!
>
> RPC over HTTPS still "counts" as a MAPI profile and as you know you
> only have one per profile.
> That's it really, not much more to say. You know what you're doing and
> are thwarted by muppet policies. IMAP is the way people go any clowns
> who don't allow a damn protocol like that OUT and can't even bring
> themselves to restrict it (not that you need to) to a given host (i.e.
> the actual destination host name) really don't deserve to have jobs,
> they piss me off.

Michael
Tue Jul 22 23:18:59 CDT 2008

You never know; these muppets might think that POP is way more secure than
IMAP and allow it out. ;)

"Mark Arnold [MVP]" <mark@mvps.org> wrote in message
news:3ric84tq0inv8tonnqbs2827rlkiad47on@4ax.com...
>
>>
>>
>>Of course I manage all the mail servers I talk about, but the easiest way
>>to
>>do this is to have Outlook open on one Exchange server and then use POP3
>>to
>>pull the mail from the other Exchange server and set the destination to be
>>the Exchange mailbox in Outlook. The downside is that now you're
>>co-mingling mail though.
>>
>>/b/b
>
> Muppets that don't understand simple directions and don't allow IMAP
> outbound are even less likely to be allowing POP3 out.

Mark
Wed Jul 23 07:25:23 CDT 2008

Indeed. Stranger things have happened.

toddb
Wed Jul 23 08:10:45 CDT 2008

Thanks for the thoughts. Unfortunately IMAP will not be allowed --
the powers-that-be have declared it off-limits for whatever reason. I
unfortunately know very little about the Exchange side, so my argument
of "it would really help!" doesn't quite work.

I guess the partners will be stuck using OWA for the @mydomain.com
messages, unless I can test alternate email clients (thunderbird
maybe...).

Anyway - thanks for the posts!!