Actually we want to avoid creating one email entry per email address inside remedy, because it is just slow and it is not designed for bulk email blast. We want to hand over that task to email servers that are built for doing that. Our each outgoing email usually contains 500 or more email addresses in CC list. And our SLA is usually with in a few minutes once an incident happens to send a notification to impacted customer. I agree it does not matter if it failed at remedy level or at smtp server level, the end result is email failed reaching end users. It seems like the our smtp server vendor has promised that it can properly handle these kind of email address errors. And single error in an email address is causing the whole email to fail. So we want to validate if it is the smtp server issue so that they can provide a fix. We wrote workflow to validate or handle these at remedy level but seems like users did not like that when they are handling hundreds of email addresses and getting popup errors from remedy when they copy paste from their spread sheets.
On Thursday, September 27, 2012 1:14:48 AM UTC-7, Misi Mladoniczky wrote: > > Hi, > > If addresses are incorrect, it does not really matter if the email engine > or your mail server is the complaining party. The messages are not sent. > > So why do you have characters that are not OK? > > One way to fix this is to send individual emails to each person instead of > one email with "," between addresses. > > Just separate the addresses with "return" instead of "," in the > Notification-action, and each user will get an individual email. > > Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) > > Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10/11): > * RRR|License - Not enough Remedy licenses? Save money by optimizing. > * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. > Find these products, and many free tools and utilities, at http://rrr.se. > > > There is an ar system email error logs form that records errors. Do you > > know the exact error text? If not check this form. > > On Sep 27, 2012 12:47 PM, "patchsk" <[email protected] <javascript:>> > wrote: > > > >> ** > >> Is there a way to know if an error in the remedy email error logs is > >> from remedy email engine or from an external email server that remedy > >> connects to like exchange server without turning on debug logs in > remedy > >> email engine. > >> We are seeing remedy outgoing emails failed due to an illegal character > >> in > >> the To or CC or BCC field. > >> An illegal character could be a new line or space or a multibyte > >> character etc.. > >> The problem here is the entire email is failing and no one in the To OR > >> CC > >> or BCC list is receiving the email just because one of the several > >> emails > >> has a syntax error. > >> If there are 10 people in the email address list, no one is receiving > >> just > >> because one email address has issues. > >> So we want to know if this is limitation on remedy email engine side or > >> external email server. > >> I know may be I need to turn on the email engine debug logs to verify > >> it. > >> Just want to check with the group before going through the approval > >> process to get logs turned on in our production server. > >> We do not have a dev env with an exchange server connected. > >> This is ARServer 7.1. > >> > >> > >> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ > > > > > _______________________________________________________________________________ > > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > > > > _______________________________________________________________________________ > > > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
