Unable to send mail using notification activity -job aborted

maypandh · Post by **maypandh** » Thu Apr 28, 2016 7:31 am

Hi All,

Scenario ::
I want to collect recipient addresses from a file then for those addresses which are mentioned in MailList file I want to send emails.

So I have created one shell script called through execute command activity which is fetching data from file & echoing output as mail addresses and passes as input to notification activity stage to send mail.

Job Flow ::

Execute Command Activity (For Fetching mails from a file & passing those mails as output) -- > Notification Mail Activity (Mentioned Command output in recipient mail address)

So For a sample file MailList.txt which is holding 2 addresses (Space separated)
abc.123@gmail.com xyz@gmail.com

Output From Command Activity Stage (From Script MailList.sh) is ::
abc.123@gmail.com xyz@gmail.com

Input to Notification Mail Activity ::
Recipients email address : #Execute_Command.$CommandOutput#

But Job is getting aborted stating Parameter 2 ('') does not start with a keyword.

Kindly suggest how to resolve this issue.

chulett · Post by **chulett** » Thu Apr 28, 2016 8:40 am

I believe the email addresses need to be comma separated with no space.

maypandh · Post by **maypandh** » Thu Apr 28, 2016 10:29 am

In Notification Mail Activity stage while sending mails, in recipient addresses can be space separated.

As I have tested with only notification activity stage with space separated between mail ID's.

chulett · Post by **chulett** » Thu Apr 28, 2016 1:34 pm

And yet passing that space separated list as a parameter may be problematic, hence my suggestion. Seems to me it's worth a shot, then you can come back here and tell me I was full of crap if it still doesn't work.

maypandh · Post by **maypandh** » Fri Apr 29, 2016 12:04 am

Hi Craig,

I tried with comma separated but still facing same issue as Parameter 2 ('') does not start with a keyword.

Kindly suggest any alternative way.

chulett · Post by **chulett** » Fri Apr 29, 2016 7:00 am

I have no idea right now what exactly "Parameter 2" might be. Can you copy / paste the complete, unedited error message from the log here? I'd also be curious if your mechanism works at all with a single email address being passed.

JRodriguez · Post by **JRodriguez** » Fri Apr 29, 2016 5:10 pm

Try cleaning up the output from the command in a user variable before passing to the email notification. The parameter2 (") might just be that the command output contain a field marker (@FM)

maypandh · Post by **maypandh** » Fri Apr 29, 2016 9:29 pm

Hi Julio,

I had already tried that option as to capture output from command output to a user variable then bypass that variable as a input to notification mail activity.

But still got same issue.

chulett · Post by **chulett** » Sat Apr 30, 2016 7:23 am

How about a response to my last post?

JRodriguez · Post by **JRodriguez** » Sat Apr 30, 2016 10:28 am

I guess that you also cleaned up the field markers -@FM- values in the user variable activity. Did you?

Convert(@FM,'', commandOutput)

maypandh · Post by **maypandh** » Mon May 02, 2016 12:37 am

Hi Julio,

Thanks a lot !!

Given logic worked fine & able to send mails to different id's.

chulett · Post by **chulett** » Mon May 02, 2016 7:05 am

Ah... should have pushed earlier on the @FM possibility but those usually end up throwing a "code=-4 [ParamValue/Limitvalue is not appropriate]" error message. I also thought when Julio first mentioned them and you said you "already tried that option" that you meant you'd already stripped out the Field Mark(s) that $CommandOutput always adds to the string. For the record, you would have had this problem using this mechanism to pass in any number of values, including a single email address.

Thanks for pushing the proper solution, Julio.