Page 1 of 1

GoAnywhere Command and lists or email bcc

Posted: Wed Feb 05, 2014 9:24 am
by bothunbr
Hello,

I want to send out email to several recipients using director send email and ghttps package from a single gacmd. Here is an example:


Email addresses:
[email protected]
[email protected]
[email protected]
[email protected]

I don't want each of the recipients to see each other on the message. My desired outcome would be to replicate having the above list into a bcc field. GA doesn't seem to have a bcc field. I think I can accomplish this with a loop but I can't seem to figure out how to send a list with the gacommand.


gacmd -server http://gadirector.tastercentral.com:8000/goanywhere -user xxxxx -password xxxxx -command runProject -project /Production/Illume/IllumeNotifications -mode batch -variables ENrecipient [email protected] ENsubject "Ready to Export" ENmessage "your file was completed in blah seconds"

Re: GoAnywhere Command and lists or email bcc

Posted: Fri Feb 07, 2014 8:30 am
by Support_Rick
In this scenario, you shouldn't have to go through the GHTTPS to send these emails. You could just do a SendEmail Task directly from within the GADirector Project and by clicking on the "Next" button, selecting BCC (See screenshot).
Send BCC Email.JPG
Send BCC Email.JPG (39.3 KiB) Viewed 6790 times
Unless you are attaching documents to the email that need to be sent to the recipients as Secured, you shouldn't need to use the GHTTPS to access the Secure Mail module.

Re: GoAnywhere Command and lists or email bcc

Posted: Fri Feb 07, 2014 2:36 pm
by bothunbr
Rick,

I am sending out a package via ghttps. The user gets the securemail with a password protected link. It would be nice if the ghttps task had the same options as email.

--Brad

Re: GoAnywhere Command and lists or email bcc

Posted: Fri Feb 07, 2014 5:29 pm
by Support_Rick
Brad,

Try sending the Secure Mail to all 4 recipients (separated by commas). The Secure Mail that each receives should be individual, not grouped. So, 1 should not see the other 3.

Please test to verify. This should take care of your issue.