Re: Email engine (6.03, Solaris8, Oracle9)

2008-01-30 Thread Michiel Beijen
e > From: "Sanford, Claire" <[EMAIL PROTECTED]> > To: arslist@ARSLIST.ORG > Sent: Wednesday, January 30, 2008 6:42:03 AM > Subject: Re: Email engine (6.03, Solaris8, Oracle9) > > In case I am missing something... Don't you need the field ID numbers > alon

Re: Email engine (6.03, Solaris8, Oracle9)

2008-01-30 Thread Ray Gellenbeck
in production ;) Ray Gellenbeck around since 3.x - Original Message From: "Sanford, Claire" <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Wednesday, January 30, 2008 6:42:03 AM Subject: Re: Email engine (6.03, Solaris8, Oracle9) In case I am missing something... Don&

Re: Email engine (6.03, Solaris8, Oracle9)

2008-01-30 Thread Sanford, Claire
evelID!: Basic > > !AssetID!: > > !ForeignNational!: No -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Michiel Beijen Sent: Wednesday, January 30, 2008 5:17 AM To: arslist@ARSLIST.ORG Subject: Re: Email engine (6.03,

Re: Email engine (6.03, Solaris8, Oracle9)

2008-01-30 Thread Michiel Beijen
Hi Ray, In order for Remedy to parse the incoming messages you need to set the "Email Action" field on the AR System Email Mailbox Configuration form record for the Incoming mailbox to "Parse". Also, you would need to restart the email engine to read any configuration changes you made to the Mail

Email engine (6.03, Solaris8, Oracle9)

2008-01-29 Thread Ray Gellenbeck
We've not had to use email for incoming requests in the past, so bear with a faily new (and hopefully simple) question. We are now using the email output from a different system and trying to automate the ticket-creation process behind the scenes by parsing this email into a ticket. We had the

Email engine (6.03, Solaris8, Oracle9)

2008-01-29 Thread Ray Gellenbeck
We've not had to use email for incoming requests in the past, so bear with a faily new (and hopefully simple) question. We are now using the email output from a different system and trying to automate the ticket-creation process behind the scenes by parsing this email into a ticket. We had the