Re: incoming mail not working properly

2010-04-14 Thread Nair, Rajesh IN BOM SISL
Hi After lot of modification system atlast started except the mails. But now i am getting this error in the log Apr 14, 2010 5:01:10 PM com.remedy.arsys.emaildaemon.LoggingModule doWork SEVERE: You must have a Help Desk Fixed License to modify case information. Apr 14, 2010 5:07:15 PM

Re: incoming mail not working properly-update

2010-04-14 Thread Nair, Rajesh IN BOM SISL
Hi After lot of modification system atlast started except the mails. But now i am getting this error in the log Apr 14, 2010 5:01:10 PM com.remedy.arsys.emaildaemon.LoggingModule doWork SEVERE: You must have a Help Desk Fixed License to modify case information. Apr 14, 2010 5:07:15 PM

incoming mail not working properly

2010-04-13 Thread Nair, Rajesh IN BOM SISL
Dear List I am facing an issue while sending a mail to remedy email engine I am getting an error which i can see in the log .. mentioned in the trail mail I am using the database name within !! quote say !Submitter! : XYZ I have mentioned all the required fields in the mail which i send it to

Re: incoming mail not working properly

2010-04-13 Thread Konrad Banasiak
Of Nair, Rajesh IN BOM SISL Sent: Tuesday, April 13, 2010 3:04 PM To: arslist@ARSLIST.ORG Subject: incoming mail not working properly ** Dear List I am facing an issue while sending a mail to remedy email engine I am getting an error which i can see in the log .. mentioned in the trail

Re: incoming mail not working properly

2010-04-13 Thread Brittain, Mark
if I can find the cause. Mark From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Nair, Rajesh IN BOM SISL Sent: Tuesday, April 13, 2010 9:04 AM To: arslist@ARSLIST.ORG Subject: incoming mail not working properly Dear

Re: incoming mail not working properly

2010-04-13 Thread Nair, Rajesh IN BOM SISL
] On Behalf Of Brittain, Mark Sent: Tuesday, April 13, 2010 8:10 PM To: arslist@ARSLIST.ORG Subject: Re: incoming mail not working properly ** Hi Rajesh, It looks like there is a problem with the email template that you are using. I found that if you remover the server name from the template, it works