Joe,
Simple answer :) Integration not directly but I think it acheives what your after.
I have done something similar I suppose but maybe it involves a couple of more steps than you would like, also it may
not be as secure as you would like as it involves forwarding mail as input into some perl scripting. There are
many options available but this approach although long-winded best suited at the time.
In essence how I set it up, was:
For each mailbox on the exchange server that I needed to get mails into remedy, I added a forwarding rule to the
mailbox which forwarded the mail to a Unix mailbox residing on the remedy server [sendmail running/configured].
Once it arrived in this unix mailbox I would forward it, this time the forward would pump the contents of the mail into a perl script which in-turn would
forward the re-formatted mail onto the remedy mailbox which armaild was listening on. The perl script would get the free format mail message
and cut the various key bits of information such as subject, to, from , body, source and put them into the appropriate location in a mail template which the
script built up [One would export the mail template from Remedy Administrator and use it's output in the script creation] and then forwarded the mail to the remedy mailbox which armaild was listing on. armaild would then submit the template into remedy.
For a maintenance point of view, from an email your normally only interested in about 4 or 5 items from it, e.g To, Cc:, From:, Subject, Body the other
headers are generally of less value. You would build a temp form which would contain fields for these key fields, and build some workflow which would push
the value's on to the main form, e.g helpdesk. As part of the push you can figure out from the email address the rest of the contact details and provide default
values for fields etc.... In certain situations I also built workflow that if a mail was replied too, and had a request id in the subject line I would update the helpdesk ticket, the engine behind this was remedy workflow, the purpose of the interface was to allow users to write free format messages and the job of the perl script was to get it into the format that remedy liked.
There are a number of ways to reduce the steps involved but this way suited at the time.
Hope this gives you some ideas.
Regards,
Kevin
-----Original Message-----
From: Joe DeSouza [mailto:joe.cybermak@MAKHARAFI.NET]
Sent: 14 July 2002 13:21
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: ARS 4.x on Solaris and Exchange Server....
Simple question...
Has anyone integrated the ARS version 4.x residing on Solaris to integrate into MS Exchange server to receive notifications without using any third party tools you have to pay for? I know the guys at (UWIP) Rem-Mail may be eagerly wanting to tap my back, but I think cost of achieving this integration here is a consideration unless you guys can make us an offer we can't refuse (I just watched Godfather part I again last week).
So I'd be willing to look at even a free unsupported product that may give me a little bit of hell every now and then.
Oh did I say that out too loud on a Sabbath day!!
I know the above is achievable in version 5.1 which will be released soon, but that is not an option I have right now.
Any thoughts would be appreciated.
Joe DeSouza,
CyberMAK Information Systems
Kuwait.
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
Previous Topic
Index