Internal NAV2013 to relay email externaly through our internal exchange server 2013

ello,
We are using NAV 2013 to externally relay email outside and inside through our in house Exchange server 2013.
I created a new Frontend connected with "TYPE" Custom and selected specific ip to configure relay through exchange server.
Once created the Receive connectors I want only Anonymous permission to be set under permission group and not exchange users as this is allowing external 3rd party exchange server to relay emails through our exchange server.
When i edit the properties of the exchange server to uncheck Exchange Server it gives me an error
"You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative."
My motive is that I want to allow only the NAV2013 to relay emails through our exchange and no other exchange server or any other application for security reasons.
Once i created a Receive Connectors bydefault TLS is selected and then i put a tick mark on Anonymous but as soon as i save i get error "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter
to a value of ExternalAuthoritative." and it doesn't let me save unless i select Exchange Server
I have followed the same link that you provided me.
There is another problem as well, I have restricted a distribution group from receiving email from external to the organisation but as soon as i created this relay connectors this group starts receiving email external to the organisation which is very strange.
I tested by disabling the relay connector and then sending email from gmail and then i get a bounce in gmail and the DG doesn't receive email but as soon as I enable relay connector the distribution group starts receiving email.
I have also recreated the connector as well but still the same issue.
Please help

Hi,
Please double check whether the "You must set the value for the PermissionGroups parameter to ExchangeServers when you set the AuthMechanism parameter to a value of ExternalAuthoritative" is an error, we can safely ignore it if it
is only a warning message. 
I found a related KB for your reference even if the Exchange server version is mismatched.
Exchange 2010: Get-ReceiveConnector warns that an Exchange 2007 connector is corrupted and in an inconsistent state
http://support.microsoft.com/kb/2291884
Please double confirm the following setting:
Authentication tab: Checked TLS and Externally Secured.
Permission Groups: Anonymous users, Exchange Servers
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • Blocking Spam Emails by subject name in Exchange Server 2013

    Hello Guys,
    I need to know how to block spams by subject from Exchange Server 2013's Anti-spam/message filter.
    In general, I'm using Exchange's anti-spam agents and configured spam blocking by domain name.. but I need to filter unnecessary emails by subject name also.
    So, if you know how to resolve this issue, please post here the real solution..
    Thanks a lot,

    Hi GMG,
    Thank you for your question.
    We could install Exchange 2013 edge server, then we could create item which block spam base on subject name in “Protection”, we could refer to the following link:
    https://technet.microsoft.com/en-us/library/bb124701%28v=exchg.150%29.aspx
    There is a another method, we could use transport rule to filter spam by subject name by the following link:
    https://technet.microsoft.com/en-us/library/dd351127(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Copy emails (entire mailbox) to another exchange server 2013

    Hi,
    We are a hosted Exchange server 2013 solution provider, and we want to migrate customer mailboxes (from exchange 2007, 2010) to Exchange 2013 using some API, as we have a web portal for other admin tasks too. Someone told us that we can use EWS Managed API
    for this purpose.
    Is there any article  in this regard, which can help us?
    Or, is there any other API which we can use?
    Thanks in anticipation.
    Regards, David Johnson

    Hi,
    Glen thanks a lot for your reply. You are always a great help.
    We are currently exporting\importing using powershell manually, but there are some difficulties in automating it using a web based app, as we don't want our customers to do any manual changes, while also, from our server, we cannot execute powershell commands
    on remote Exchange 2007 servers.
    Automating Cross forest migration is also very diificult, as you know that it has many steps, which are hard to automate, and also there is no api for MRS, as we know.
    We have seen some migration utilities doing migration using EWS API, like CodeTwo, and also Transend
    Migrator. Can you please tell, if you know, how they are doing it.
    Thanks.
    Regards, David Johnson

  • Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

    Exchange server 2013 in Windows server 2012 VM
    It was working fine then start the issue.
    Firewall is managed externally and the last report said:
    "I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
    Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
    Can you verify that the mail server is set up so as to allow port 25? "
    Today I was able to telnet the server from home: successfully 
    220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
    250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
    Also the receive - send connectors seems ok
    Mx record point to Microsoft protection:
    dualtemp-com.mail.protection.outlook.com.
    Again, OWA is able to access and send/receive emails internal but never external even no bounceback  just it never arrive.
    Help me please. This is my first admin chaos...

    Hi,
    Is there any update with your issue?
    If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
    For more information about Exchange 2013 mail flow, here is a blog for your reference.
    Exchange 2013 Mail Flow Demystified…Hopefully
    http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • Exchange Server 2013 SP1 - Internal Email Flow slowness

    Hi Fellows,
    I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
    I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
    When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
    Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
    Header analysis shows the message exchange between mailbox servers is taking time. any clue?
    Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
    Network communication, Storage performance, Server performance are all as good as we love to.
    Thanks.
    J.A

    Hello,
    When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
    Cara Chen
    TechNet Community Support

  • Exchange Server 2013 - 550 5.7.1 Unable to Relay

    Hi Guys,
    I have recently setup Exchange 2013, I have been having an issue were the Emails that we are attempting to send are getting stuck in the 'Drafts' box. I decided to use Telnet to see if I could send emails that way but much to my disappoint I was unable to
    send emails to external contacts using Telnet getting the following error '550 5.7.1 Unable to relay'.
    For my external server lookup I have my internal DNS Server for the DNS and my internal DNS Servers forward DNS Requests to Google's Public DNS Servers (8.8.8.8 and 8.8.4.4). I have tried removing Google's DNS Settings and just using my internal servers
    and using Google's DNS Server and not our internal DNS Settings.
    Does anyone have any suggestion on what might be causing this issue. I have been working through the solution in other posts on other web sites but so fare not much luck.
    Kind Regards
    Thomas Park
    Network Engineer   
    TPark IT Technician

    Hi,
    Please check whether the Windows services that Exchange requires on a server have started via Test-Servicehealth. Especially Exchange Transport service and Mailbox transport service.
    Please add the IP address of our DNS server for testing.
    Please also re-configure our Relay Connector, found a useful article for your reference:
    How to Configure a Relay Connector in Exchange Server 2013
    http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
    If still not working unfortunately, please trace these messages via Message Tracking to check whether there is any error. If has, please post the details for the further troubleshooting.
    Disclaimer:
    Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
    that you completely understand the risk before retrieving any suggestions from the above link.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Help with Moving Emails from Exchange Server 2013

    Hi Team,
    Help, I need a solution on how to copy incoming and outgoing emails together with their attachments and was hoping someone could help with a solution I need to find for this problem.
    1) I have a need to copy all incoming and outgoing emails & attachments from Exchange Server 2013 mailboxes on a daily basis, so they can be archived into an external 3rd party database overnight.
    I believe that the first step is that I can set up another Exchange mailbox, through Journaling to receive these emails. 
    Is there any way that these emails can then be moved direct from the Journaling mailbox that I have created, to a shared folder on the network? If so what format would they be sent out as e.g. .msg, .ems and what is the process?
    Failing that, could they be sent to an Outlook client (not another Exchange mailbox) on the network and stored in a .pst file? (I have a program that will export them from .pst)
    I would really appreciate any assistance that you can provide in this matter.
    Regards, Greg.

    Hi,
    You can set auto-forward on journaling mailbox and auto-forward emails to another mailbox. Why don’t directly archive the emails from the journaling mailbox “an external
    3rd party database”.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Http 500 internal server error exchange server 2013

    Hello Everyone
    Here is my little scenario.
    i have a domain named contoso.com
    i then installed exchange server 2013 in my environment.  cas and mailbox server are on seperate box.
    switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
    i now have 2 cas server and 2 mailbox server
    problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
    although with exchange management shell i can connect to all the servers

    -->switched of my exchange servers for a week, during that period i changed the netbios name of my
    domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain. 
    Renaming of domain is not supported in Exchange2007/2010/2013.  (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
    Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)? 
    Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
    that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
    server.
    Please get back with the result.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

    HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012.  I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role,  first i installed the MBX and after the CAS role, i passed
    prerequisite check without any issue.  However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
    I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and
    I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.
    I appreciate your help, on my case.

    Hi,
    The link that Jatin points to should be this.
    https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
    Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
    If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
    Thanks.

  • Best way for Email Notifications in EWS Managed API 2.0 [ Exchange Server 2013]

    Hi ,
    I want to know best way for Email Notifications in Exchange server. My
    organisation has 
    10 users, i want to get notification if any user mailbox got any new mail.
    i need to create API,
    that was consumed by another Team in their Application.
    I am using Exchange server 2013.
    Please share Your Ideas.
    Thank you

    Take a look at EWS Notifications
    http://msdn.microsoft.com/en-us/library/office/dn458791(v=exchg.150).aspx .
    Cheers
    Glen

  • Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

    Hi people,
    What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
    Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
    Thanks

    Hey AlbertWT,
    Can you clarify exactly what you mean when you say "server patching?"  Do you mean patching at the ESXi host level or something within the guest?
    As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer.  Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role.  NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
    If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
    Matt
    http://www.thelowercasew.com

  • Exchange Server 2013 internal and external DNS records

    I recently installed Exchange Server 2013 and I've register a pubic ip too for exchange server. How can I create internal DNS as well MX record for my Exchange server to send and receive internet mails. It's my first time configuring exchange for a organization.
    registered domain name=====np.bbcmediaaction.org
    public ip=====202.166.212.221

    Hi,
    For external mail flow, we need the following DNS records: MX records for the domain part of the external recipient, A records for the destination messaging servers. For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/bb676467(v=exchg.150).aspx
    Additionally, to ensure external mail flow works well, we also need to configure send connector.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx   
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Configuring Multiple domain Email addresses in Exchange server 2013 for Send/Receive

    I've setup an exchange server 2013 , I have an requirement to setup email addresses for multiple domain account.
    For example - My primary email addresses - [email protected] however i need to setup multiple domain email account for single AD user.
    Example
    [email protected]
    [email protected]
    [email protected]
    I was able to setup account to receive email from different users to single mailbox users however how can i send mails from other domains email address apart from primary domain email 
    Thank you
    Benhur

    Hello,
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.
    Cara Chen
    TechNet Community Support

Maybe you are looking for