I have read a few prior issues, but wasn't sure what I might be up against. I have created a repetitive e-mail action using the file contents iterator. It s definitely working thru the iterations, however it is only delivering to addresses in my Microsoft Exchange domain. Any addresses that exist outside do not receive my e-mails. Is there a setting on my: firewall(port 25), exchange, or in outlook that I can do to correct this issue?
Thanks for posting the log output. It looks like this could be an Automise issue after all. Do you receive the error on all non-Outlook domain addresses that are specified? Is the succeeding address the first address in the list?
Also, if you change the Send Email action to use the “load recipients from file” option, instead of a File Contents Iterator, does this make any difference to the behaviour?
The first name in the list is an e-mail address IN my exchange domain, so the unsuccessful one you see iss the list of OUT of domain names. How do I go about trying the "Load recipients from file" option.
To load the list of recipients from a file, go to the Recipients property page in the action, select the “Load from File” radio button, and then select a file to load the list of addresses from.
The file can be either a list of addresses (with each address on a new line) or a list in the format “Address, Name”. As well as (hopefully) working around the Send Email issue, this approach should be much faster than using a separate action for each recipient.
I just noticed that this feature is currently not documented in the help file, I’ll address this ASAP.
I got it to work with the new beta version, but I think the problem was more of the setup of the smtp. I used port 25 instead of 15 and the Logon & password needed to be filled in with the current user that is logged on to the network using Automise. I just sent it to one outside e-mail & it worked!
thanks again for your help,
John
p.s. Incidentally, I see now how both scenarios work(i.e. Using the Iterator and loading from a file) - your tech support is great!
Thanks Angus - it actually did default to 25, I must have changed it during the course of trying to fix this. I think I had used port 25 prior, but never with the proper logon & password used in conjunction with it. I was using the administrator logon & password until I discovered that I needed to use MY Logon & password.