When we switched from NetMail on our HP 3000 to Exchange, we were able
to set up our Exchange server as a "trusted gateway" in the NetMail
configuration. That routes all messages through the Exchange server.
We kept some folks on NetMail and that required setting them up as
"custom recipients" in the Exchange Admin program. I'm not familiar
with PostHaste, but something similar may be possible and would let
you continue using PostHaste for those automatic e-mails.

On Fri, 9 Jul 1999 13:16:54 -0400 , Steve Miller
<[log in to unmask]> wrote:

>This is more of a MS Exchange questions/problem than HP3000, but it starts
>on the 3000 and there's lots of varied expertise out there, so...
>
>We are currently replacing our HP 3000 based e-mail package (PostHaste) with
>MS Exchange and Lookout 2000.  I have some programs on the HP that
>automatically generate E-Mails (i.e. notifying a customer of a backorder).
>This was easy to do with PostHaste - I created a file with the address
>information, a second file with the body text, a third file that named the
>first two, and dropped the name of the third file into a MSG file scanned by
>PH.
>
>I must now accomplish the same end result with Exchange.  Somehow, I must
>get a message created in some way on the HP to our exchange server for
>ultimate routing to either an internal user or an internet address, with no
>human intervention.  Unfortunately, I'm not the network person, so I did not
>receive NT or Exchange training of any kind (I can barely spell NT).  Our
>highly paid NT/Exchange consultant has no idea.  Our internet gateway is
>actually on an exchange server at another subsidiary (connected via frame
>relay) and they have no idea.
>
>I have three weeks, at which time I will be executed (okay, just shunned).
>Any pointers for resources would be greatly appreciated (my contact at our
>other subsidiary would only say 'Good Luck!').
>
>Steve Miller
>Portion Pac, Inc
>[log in to unmask] (Exchange)
>[log in to unmask] (PostHaste)
>