I had a similar issue. We send an email to a lot of devices via JAMF. If one email or more is no longer valid, or accurate, or maybe the employee left, it bounces the entire "Action" command. In our environment, I worked with the network/email folks to uncover these invalid email accounts.
Once you discover this account, you can either update the Jamf inventory record or just exclude that specific account in your criteria before sending the "Action" command.
I worked with Jamf on this as well. The best they could do was view the Jamf log and point this to the SMTP error (or something like that). Ultimately, it was one or more bad email accounts that causes this error.
I had a similar issue. We send an email to a lot of devices via JAMF. If one email or more is no longer valid, or accurate, or maybe the employee left, it bounces the entire "Action" command. In our environment, I worked with the network/email folks to uncover these invalid email accounts.
Once you discover this account, you can either update the Jamf inventory record or just exclude that specific account in your criteria before sending the "Action" command.
I worked with Jamf on this as well. The best they could do was view the Jamf log and point this to the SMTP error (or something like that). Ultimately, it was one or more bad email accounts that causes this error.
Ok, thanks for your suggestions. I spent some time going through the list (fortunately less than 100 users) just checking to make sure the email addresses were correct in the field, but I had a feeling it could have something to do with whether or not one or more of the email addresses were no longer active, which is most likely the case.
Thanks again!
Keith
If I were you I would probably have sent it to 50/80 users of the 100 and see if it fails, then 30/40 and see if it fails, that will help you narrow down who/where the problem arises.