Link to home
Start Free TrialLog in
Avatar of cawasaki
cawasaki

asked on

Exchange 2013: my Default Frontend receive connector autorize internal anonymous user

hello,

i have 6 exchange 2013 server multi role.

i have test this morning and i can send from user computer email without any authentification and i can chooseany sender like toto@xxx.com or president@domain.com.... and send to all exchnage user.

from smtp log i see that the Default Frontend receive connector accept this email.

this receive connector is a default one and i think i have not modified this one, i can see that anonymous user is checked.

with this command i can see this:

Get-ReceiveConnector "servername\Default Frontend servername" |get-adpermission -User "NT AUTHORITY\ANONYMOUS
 LOGON" |select AccessRights,ExtendedRights

AccessRights                                                ExtendedRights
------------                                                --------------
{ExtendedRight}                                             {ms-Exch-SMTP-Accept-Authoritative-Domain-Sender}
{ExtendedRight}                                             {ms-Exch-SMTP-Accept-Any-Sender}
{ExtendedRight}                                             {ms-Exch-SMTP-Submit}
{ExtendedRight}                                             {ms-Exch-Accept-Headers-Routing}
{ExtendedRight}                                             {ms-Exch-Store-Create-Named-Properties}
{ExtendedRight}                                             {ms-Exch-Create-Public-Folder}

any help plz?
Avatar of Bembi
Bembi
Flag of Germany image

If anonymous user is checked, you can indeed send mails to the server without any authentication. But as I remember it is not enabled by default.
A connector which accepts anonymous users is mostly needed, if any service, server or device should send mails to the exchange, i.e. status or monitoring mails. Not all service allow authentication or it is just made to keep it easy.

As long as the connector can not touched by the external world (usually a firewall is in front of it), it would not be the biggest issue.
A better solution would be to use 2 connectors...
One for the exchange from known clients (i.e. the firewall or front appliance or whatever is in front of exchange, and a second one for any server, which should be able to send monitoring mails. The second connector your can limit to your know servers, and the first one to your firewall.
AS anonymous access to the server is usually not used by clients (they use a authenticated connection), you can reduce an impact of an some smtp related virus outbreaks if only allowed services can sent anonymous messages.
This is the default behaviour.
It is not a Open relay so it do not trigger a security risk.

my bigger concern is ms-Exch-SMTP-Accept-Authoritative-Domain-Sender but thats a seperate topic.
Avatar of cawasaki
cawasaki

ASKER

its a default, but i am sure i can modify one of this config to correct the problem:

AccessRights                                                ExtendedRights
------------                                                --------------
{ExtendedRight}                                             {ms-Exch-SMTP-Accept-Authoritative-Domain-Sender}
{ExtendedRight}                                             {ms-Exch-SMTP-Accept-Any-Sender}
{ExtendedRight}                                             {ms-Exch-SMTP-Submit}
{ExtendedRight}                                             {ms-Exch-Accept-Headers-Routing}
{ExtendedRight}                                             {ms-Exch-Store-Create-Named-Properties}
{ExtendedRight}                                             {ms-Exch-Create-Public-Folder}
sure

technically, you can do this by  ** DISCLAIMER , PLEASE READ BEFORE you DO ANYTHING) **

Get-ReceiveConnector <the one you want to change> | remove-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Sender"
Get-ReceiveConnector <the one you want to change> | remove-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Authoritative-Domain-Sender"


So, what will it potentially break?

1. Internet in-bound email
2. application bound email like printers and etc
3. notification emails that any application have configured
4. etc that i haven't anticipated.


Usually set a very low threshold so no one can send more than 10 emails per minutes (default is unlimited) using these receive connectors.

Again, the choice is yours :)

good luck!
Or let me formulate it in a different way.

You can uncheck the anonymous access in the connector properties if... (all of them)
a.) you can make sure, that any service, server or device, which is sending mails can be configured for authenticated SMTP.
b.) you have configured all these servers, services, devices to use it
c.) you have a smtp gateway in front of exchange, which connects to exchange with authentication.

If your exchange is directly connected to the internet and mails are directly delivered via SMTP to you server, you need a connector which allows anonymous access as otherwise you would not get any email anymore. Nobody outside your organization has credential to logon.
hello,

i have 2 smtp gateway delever email to my exchange server, this gateway not used this smtp connector, it user other connector and i have authorize IP adress of gateway to relay email without authentification.
ASKER CERTIFIED SOLUTION
Avatar of Bembi
Bembi
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial