HP3000-L Archives

July 1999, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Denys Beauchemin <[log in to unmask]>
Reply To:
Date:
Fri, 9 Jul 1999 13:39:47 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
X-no-Archive:yes
Contrary to some of the other opinions on this list, I think Exchange is a very
good system.  I speak from experience as I have used it for several years.  It
has a lot of flexibility and is very stable, especially in the 5.5 version.

What you need to look at at this time, is MAPI.  You will need to write a small
MAPI aware application on NT to which you will forward the message to be sent
and the address(es) to which to send said message.

I have a couple of names of people to whom you might want to talk about this
subject (I am not one of them).   Let me know.

Kind regards,

Denys. . .

Denys Beauchemin
HICOMP
(800) 323-8863  (281) 288-7438         Fax: (281) 355-6879
denys at hicomp.com                             www.hicomp.com


-----Original Message-----
From:   Steve Miller [SMTP:[log in to unmask]]
Sent:   Friday, 09 July, 1999 12:17 PM
To:     [log in to unmask]
Subject:        Automatic E-Mail from HP to Exchange

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)

ATOM RSS1 RSS2