Re: Application relaying

Tech-Archive recommends: Fix windows errors by optimizing your registry



That's by design, as far as I can tell. You need to add Anonymous Users as a permission group. For example:

Set-ReceiveConnector –Identity "Server\Default Server" –PermissionGroups AnonymousUsers,ExchangeUsers,ExchangeServers,ExchangeLegacyServers

Do a Get-ReceiveConnector | fl to find out which permission groups are already present and then use the above command to add AmonymousUsers to the list. The above command applies if ExchangeUsers, ExchangeServers and ExchangeLegacyServers were already present.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"akg414s" <akg414s@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:E4FAE314-F339-4D24-BE49-0169073CF34F@xxxxxxxxxxxxxxxx
ED, Thank you for your response.

I have not changed the settings on the default receive connector yet I can't
successfully deliver messages internally from an annonymous submitter (using
the default connector). Annonymous users is not ticked as Permission Group.
I'm sure that would probably fix it, but does this create any security risk?

If I telnet to that IP, I get a "Client was not authenticated" error when I
enter a mail from command.

Thanks

"Ed Crowley [MVP]" wrote:

If they are submitting messages only for internal recipients then they can
use the "Default" receive connector as configured by default. They are not
relaying in the Exchange sense--relay to Exchange means submitting messages
that are destined for outside the Exchange organization. The "Default"
receive connector also does not require authentication.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"akg414s" <akg414s@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B73E2F87-2E97-4814-9301-17B23BD6571C@xxxxxxxxxxxxxxxx
>I have created an additional receive connector on my HUB. I have given
> anonymous access to the conector and restricted connections to it by > IP.
> It
> works fine. My problem is I need to allow a coouple of other app > servers
> to
> connect, but they do not need to relay only deliver to the local > domain.
> How
> can I allow these other app servers to connect to the new receive
> connector
> but not be able to relay to the outside world.
>
>
> Thanks



.


Quantcast