Forum Discussion
How to set an organization wide setting to automatically download pictures from a trusted sender.
Good afternoon. I am reaching out to this community to get suggestions on how to automatically download pictures/images from one specific and trusted external sender/domain. I suspect this will likely be through powershell. If it is, I would like to know the cmdlet name and syntax.
Configuring a GPO policy on all Outlook clients in one option but will take at least one week for internal review, approval, testing and another three weeks (minimum) for full deployment.
I am already receiving push-back from the business users after suggesting the following two options:
- Manually add the %external% email address into their SafeSender list in Outlook.
- Manually uncheck the "Do Not" setting in the Automatic Download option if they want to download pictures as standard HTML.
Any guidance would be appreciated.
Thank you!
There's no organisational setting or policy as such, but you can set it for all existing mailboxes in your org with the following powershell:
$mailboxes = Get-Mailbox -ResultSize Unlimited foreach ($mailbox in $mailboxes) { $mailboxIdentity = [string]$mailbox.UserPrincipalName Set-MailboxJunkEmailConfiguration -Identity $mailboxIdentity -TrustedSendersAndDomains @{Add="<SenderEmailOrDomain>"} }You'll then just need to make sure you add them to all new mailboxes going forward, so there is some admin overhead at account creation.
- I first tried to run the command on a single mailbox like this: When using a command such as this: set-MailboxJunkEmailConfiguration -Identity "xxxx@domain" -TrustedSendersAndDomains @{Add="yyyy@domain"}
I consistently get this error: Set-MailboxJunkEmailConfiguration: ||Property validation failed: TrustedSendersAndDomainsDoes the email address you're trying to add exist within your org? I think this error occurs if the address is in your directory.
I've had success with @mycompany.com addresses using the above (which is fine as they're sent from a marketing platform with a noreply address), but if there's a recipient in exchange with that address assigned I get the above error.
I've had a dig and Microsoft seem to claim this is expected behaviour, although I don't know why it doesn't return an appropriate error message.
