Outlook rules puzzle for clever people....help please!

I have a puzzle which I would like someone to help solve if at all
possible!

If I may explain.....

I have two business email accounts on two separate networks which cannot
be connected together. On both networks the client software is Outlook
2003.

With Network A, I can only access emails while physically in the office.
With Network B, I can access emails from any physical location via
webmail.

I would rather manage all of my email in one place which is accessible
from anywhere.

It is trivially easy to do this on Hetwork A, by configuring an Outlook
rule on Network B to redirect or forward all messages to Network A.
However I then can't access mail from anywhere other than my physical
Network A office location.

Instead I would like to be able to configure a rule in Outlook on Network
A, to automatically send all emails as and when received to Network B.

I want to set it up so that emails are forwarded (either as an attachment
or inline, it doesn't really matter which) rather than redirect them as I
know from experience that a redirect rule will change the 'To' field in
the message subject header from the original email address the sender
used, to the redirected address. I don't want this to happen, because it
is important that the 'To' field is left intact for valid business
reasons.

So what I want to be able to do is something like reply using a specific
template', but can't do this by setting up a reply template pre-populated
address, because it woud then not include the original message (either as
an attachment or inline).

So instead I want to configure Outlook on Network A to forward messages
to Network B. This would normally be quite simple were it not for the
fact that unfortunately Network A requires us to use a specific release
phrase as the first words in the subject line of all messages sent
externally over the internet. Messages which don't contain this phrase
are not released and bounce back and this can't be turned off.

So I want to be able to set up a template so that I can configure a rule
in Outlook on the client side which the server then uses to forward all
emails received on Network A to my email address on Network B with the
release phrase in the subject header, and which also includes all of the
original message and attachments, either as an attachment itself or
inline.

Unfortunately I can't seem to find an appropriate option in the rules
configuration area of Outlook which would allow me to do what I want
here.

So my question is........Can this be done, and if so, how do I do it?
.

Relevant Pages

  • Re: Outlook rules puzzle for clever people....help please!
    ... With Network A, I can only access emails while physically in the ... Outlook rule on Network B to redirect or forward all messages to ...
    (microsoft.public.outlook)
  • Re: Primary user login problems
    ... I have a user that runs 3 emails off the one machine. ... futzing) what happens is when he reconnects to the network as the ... thought it was outlook asking but I linked it to the synchronization) ... Offline Files in Windows has nothing to do with Offline ...
    (microsoft.public.windows.server.sbs)
  • RE: NEW SBS2003 INSTALLATION ON EXISTING NETWORK
    ... Does this allow users on the LAN to send and receive emails over the Internet ... Probably configuring network shares and transferring across the network. ... but using the SBS wizards makes it easier still. ... >> requires SBS2003 with Windows XP clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Is Exchange server what I need?
    ... MS Outlook from my Computer A through the LAN Network. ... send and receive emails. ... a PST file you can configure Outlook on your PC the same way and then, ...
    (microsoft.public.exchange.setup)
  • Re: Outlook rules puzzle for clever people....help please!
    ... Author - The Lawyer's Guide to Microsoft Outlook 2007: ... With Network B, I can access emails from any physical ... >> redirect them as I know from experience that a redirect rule will ...
    (microsoft.public.outlook)
Loading