This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 5%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
I would not think this would be too unique of a situation, but we have an internal distribution group that we want internal users to be able to send to. We also have an external service that sends reports and we would like that to be able to send to the group as well... but we don't want to open the group up to the whole awful that is the Internet.
Under Delivery Management on the distribution group I see where I can add an account or contact, but this then blocks everyone on the inside (as the description says it will). Also in my testing, adding a contact with an external email address does not work either. If I open it up to internal and external with no limits it works as expected, just trying to not do that if at all possible.
Also, any "Best Practices" to follow on this?
Thanks!
Use transport rule instead:
Set the group to allow external senders, then create a rule that drops anything from Outside except from that sender sent to the Email Address of that DL:
It would look like this:
That looks like it will work perfectly. I was hoping to have the controls on the account itself, but that makes enough sense to me.
Thank you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 48%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
I get an error message stating the sendto rule can not be applied to a distribution list.... so close yet no dice...
In fact the only way I seem to be able to do this is to have a shared mailbox with the same rule as above applied to the shared MB. The MB it set to forward to the DL and not keep the original email, just to keep it cleaner.
`
Hi Tony,
Correct, you cannot add a DL to the recipient field. To bypass this and achieve the same result, please change "The recipient" to "The message" and then select "To or Cc box contains this person" and then you can select the DL email address.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 2%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
This is only part of the solution. It won't work if somebody uses the BCC field. How do you block this? I tried to include my list email under: "Any recipient..." -> "address includes any of these words". But it seems that the BCC field isn't stored under the message headers, so it won't work.
For me it would be easier if Microsoft just includes the option to whitelist the domains when creating the distribution list. For me, this looks like a workaround that works under certain conditions
Hi Josef,
That is incorrect. We tested the solution using the BCC field and the email was delivered without fail.
Hi Dale
Sorry for my late reply. I didn't elaborate here much. I meant, everybody using the BCC will able to send to that distribution list, so, a spammer can take advantage of this because he will be only blocked if he uses the TO and CC, but not BCC.
Unfortunately there isn't any apparent solution of filtering the BCC too. It seems, as I said, that the BCC is not accessible at the mail server.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 40%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
I have this same situation. Previously, a few short months ago, I could do this with a transport rule or by using a 3rd party email filtering tool such as App River. However, Microsoft has hosed us yet again on this. If you have an answer that works, please reply.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 26%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
use the Message property with the "To or Cc Contains this Person" and put your DL email.
BCC will bypass this as explained above in the comment section.