Hi Michael,
Thanks for the swift and thorough reply.
>What you probably need is a masquerading module (like the ftp module)
that
>makes this protocol work. The unfortunate part is that you will
probably
>have trouble getting the protocol specs out of Microsoft. They tend to
be
>really annoying about giving out protocol info.
I was afraid that this was the situation when I posted (hence the offer
of coding...) I was hoping that some of the clever people on this list
might
have already done this :-)
>Try some or all of the following:
>1) Check microsoft's support on-line web site and try to find any
articles
>dealing with running outlook across a router or over RAS or something
like
>that. You are looking for any information about using outlook in
situations
>there the exchange server is not on the same local net as the client.
There
>might be information there that will give you what you need. It is just
>vaugely feasable that you might be able to do the job with appropriate
port
>forwarding. I doubt it, but who knows?
As you rightly pointed out, getting this kind of information from
Microsoft
seems to be like getting blood from a stone. I have searched all
available
online sources as much as time permitted with no success.
>2) You could try running wingate on the mail client box and using it to
>masquerade the rest of the machines. Not an optimal solution in any
case,
>but it might do the job if all else fails.
Wingate really doesn't suit me in this situation, but good suggestion.
>3) You could try running packet sniffing software on the linux machine
to
>try and reverse engineer the protocol, then write an appropriate
module.
>This would of course, be somewhat labor intensive.
I had thought about this but wanted to make sure first that I was not
re-inventing the wheel. I'm no rocket scientist and reverse-engineering
protocols is certainly not my specialty but this does sound like a fun
project - I guess all we need is to be able to recognize a few key
packets
from the conversation and not the entire protocol.
>4) Is there a way to access your exchange server via POP instead of the
>exchange protocol? I've never managed an exchange server, but mbar you
can
>just use POP or IMAP on the thing and avoid the problem that way.
I just experimented with this and Exchange can be used as a POP server.
My limited testing of this shows it not to be very satisfactory though,
and
a poor substitute for a 'proper' outlook->exchange connection. In a
pinch it
might do, but simple problems that I have encountered include only being
able to get at the mail in my inbox (and not the other folders which I
automatically filter some mail into). Perhaps further investigation will
find
a solution for this without having to change all my filters.
So it seems that the best solution would be an Exchange masquerading
module.
I would be interested in having a go at this but I really don't have a
lot of
time on my hands. I will consider it a long-term project - masq readers:
don't
hold your breath! I will of course post any results to the list. Anybody
who has
any information that would assist in this project please forward it to
me.
>Good luck!
Thanks and cheers,
Morgan
+
Life (definition) : Life is getting complicated
The above posting does not necessarily represent the
views of my employer.
+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
