Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 183
  • Last Modified:

Block External Users sending to Internal Distribution List

Hi Experts,

I have set our Exchange 2010 SP3 to prevent external users to send to our internal Distribution List. In fact, the default is to Require that all senders are authenticated under Message Delivery Restrictions. However, this isn't working at the moment. I also have tried to create Transport Rules with the condition for messages outside the organization destined to members of a certain DL forward to a moderator. This works fine if the email is emailed directly to the DL email address itself but if the email is sent directly to the email address of an individual user it will be quarantined for approval which is not really what we want. Any ideas what's causing this?
0
Bogart Bogart
Asked:
Bogart Bogart
  • 11
  • 9
1 Solution
 
AkhaterCommented:
what are you trying to accomplish exactly ? it seems to me that everything is working fine

1) you send from outside to the email address of the DL the email gets rejects (that's what should happen)

2) you created a transport rule to ask for moderation if an email is sent from outside the org to a user in a specific DL and this is what is happening no ?


" Require that all senders are authenticated" means that emails sent TO THE DL will not get accepted and not to its members . if you want no one to send an email to the members change your transport rule to

1) email sender is form outside the organization
2) recipient is member of specific DL
3) Reject the message with the enhanced status code


that should cover you
0
 
Bogart BogartAuthor Commented:
The "Require that all senders are authenticated" isn't working which means external emails are getting through if an external user sends to the DL itself.

Setting up a transport rule it seems that it is working fine like you've oveserved BUT just would like to block the DL@test.com and not on the user level email address i.e. user1@test.com
0
 
AkhaterCommented:
when you say "external emails" you means emails sent from external users like hotmail.com right ?
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
Bogart BogartAuthor Commented:
Hi Akhater, Yes external users such as Hotmail, yahoo etc.

The "Require that all senders......" should just do the job by blocking incoming emails directly destined to the DL email address but still allows emails send individually to internal emails.
0
 
AkhaterCommented:
Can you test with a new dl? Create a brand new dl don't change anything in it's config, add to it a couple of users and email the dl from Hotmail / yahoo
0
 
Bogart BogartAuthor Commented:
Hi Akhater, I have done this already and the same is happening.
0
 
AkhaterCommented:
Oh well then please check your receive connectors is it configured with "externally secured"?
0
 
Bogart BogartAuthor Commented:
I have tried that setting as well to no avail. Weird that it just doesn't want to work!
0
 
AkhaterCommented:
Which setting? No you should NOT have externally secured on your receive connector
0
 
Bogart BogartAuthor Commented:
I don't have it.
0
 
Bogart BogartAuthor Commented:
I should have indicated that on my Default connector I don't have that (Externally Secured) selected as I don't want my server to become a relay.

Looking at the connectors it allows incoming emails alright but the behaviour of not allowing unauthenticated (external) users to send to internal DL isn't working which is really the problem.
0
 
AkhaterCommented:
Can you share the output of

Get-ReceiveConnector | fl name,*authmec*
0
 
Bogart BogartAuthor Commented:
Name          : Default XXXXXXXXXXXXXX
AuthMechanism : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer

Name          : Client XXXXXXXXXXXXXX
AuthMechanism : Tls, Integrated, BasicAuth, BasicAuthRequireTLS

Name          : Application Relay
AuthMechanism : Tls, ExternalAuthoritative
0
 
AkhaterCommented:
OK so we have "Application Relay" that has "ExternalAuthoritative" enabled

how do you receive emails from outside ?
you have an anti-spam / relay that delivers emails to Exchange ?


Get-ReceiveConnector "Application Relay" | fl name,*authmec*,RemoteIPRanges

what is the output of that ?
0
 
Bogart BogartAuthor Commented:
The application relay only allows internal network to relay to our exchange - this is mainly outgoing. So this is not the issue.

We do have Sophos Virtual Email Filter. Spoken to the guys but was advised that it's got nothing to do with the filter.
0
 
AkhaterCommented:
Get-ReceiveConnector "Application Relay" | fl name,*authmec*,RemoteIPRanges
please run this and make sure that the SoPhos ip address is not in the RemoteIPRanges
0
 
Bogart BogartAuthor Commented:
I can confirm that Sophos isn't part of the list.
0
 
AkhaterCommented:
ok can I ask you to create a new Receive connector with just the IP of sophos keep everything default just allow Anonymous on it and test again ?
0
 
Bogart BogartAuthor Commented:
Hi Akhater,

I am tempted to restart the server at this stage before proceeding. I will provide update on any improvements - hopefully.
0
 
Bogart BogartAuthor Commented:
In Exchange 2007 and 2010 having your filter as trusted will bypass authentication.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 11
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now