Exchange 2010 mail routing

How did you migrate to Exchange 2010?  Did you not migrate the groups or did you set everything up from scratch?

Hi,
We have a new exchange server installed in our domain and we are moving all our mail transmitted through epicor to this server, and I am experiencing this error
There is problem sending customer order confirmations by email. The
message says the mailbox is unavailable. The server response was 5.7.1. Unable
to relay
Now I know there is nothing wrong within Epicor, What is wrong with the Exchange server? 
Is it something to do with the receive connectors in the HUB transport I have got set up?
All other mail flow is working correctly
Regards,
Ian
This topic first appeared in the Spiceworks Community

Similar Messages

  • My macbook air cannot sync with my office microsoft exchange 2010 mail server

    My macbook air cannot sync with my office microsoft exchange 2010 mail server.
    It used to work perfectly, and then I lost connection and was never able to establish one. I re-istalled my e-mail account several times, no success.

    I am sure all of you got your email issues sorted out by now but i was having trouble settings up exchange email on my Iphone 5S, and the problem i found was to go to settings, icloud, then log into icloud with your apple id first (before setting up the exchange email).  Once i logged into my icloud account on my Phone 5S, the exchange server email starting working and synching right away.
    to confirm this worked, i even deleted my email account and deleted my Icloud accounts both from my iphone was able to simulated the same exact problem (exchange server would not sync with my Iphone 5S) until i logged back into my Icloud account on my 5S.
    Again once i logged into Icloud, the exchange server issues went completely away.
    Just wanted to post this so anyone else having the issue could see.

  • SPAM and Exchange 2010 Mail-enabled Public Folders

    Is there a way to determine if mail sent to our Exchange 2010 mail-enabled Public Folders by our customers is ever rejected because it was tagged as spam? The concern is that we might not be receiving some email. We rely on the mail-enabled PF's
    heavily, but since they aren't a mailbox there is no Junk E-mail folder to check. We do not have the resources to check EOP on a regular basis throughout the day, and the customer would not get an NDR or anything like that.
    HDL

    Hi,
    You can consider to use Message Tracking tool under EMC -> Toolbox to track these messages.
    Understanding Message Tracking
    https://technet.microsoft.com/en-us/library/bb124375%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396
    Search Message Tracking Logs
    https://technet.microsoft.com/en-us/library/bb124926(v=exchg.141).aspx
    Best Regards.
    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]
    Lynn-Li
    TechNet Community Support

  • Exchange Incoming Mail Routing

    Hi,
    I want to test a scenario where currently I have 4 Physical Exchange 2010 servers (3 are in a DAG). They all have their own external IP addresses and can all receive and send mail. I would like to test the scenario where Only 1 of the servers is receiving
    the mail although the "internet" can send to any of the 4, therefore I assume this is a network routing style issue, however is there anything in Exchange where I can send incoming mail to 1 server before it hits one of the other 3? Currently it
    would appear any of the 4 receive mail at any time and it's all a little random.
    I would be happy to keep outgoing as it is for the time being.
    Background Info: I inherited a very patchy/ broken 2007-2010 upgrade 2 years ago and am just starting to sort out the minor irritations e.g. spam, certificate warnings and backups!
    Thank You for any advice you can give.
    regards,
    Jonathan Ward

    You could always try the telnet method. The e-mail doesn't have to come from outside your organization for you to test this, all you need is the ability to establish a SMTP session and complete a single transaction.
    Try something like this:
    ==================
    telnet <ip-address-of-server-1> 25
    helo
    mail from:<[email protected]>
    rcpt to:<[email protected]>
    data
    from: [email protected]
    to: [email protected]
    subject: blah blah blah
    Leave a blank line after the subject
    quit
    =====================
    Or you can just drop a correctly formatted text file (with a ".eml" extension) into the pickup directory on any one of the machines.
    --- Rich Matheisen MCSE&I, Exchange MVP

  • Exchange 2010 mail storing Architecture

    hi I just need to know what is the method that exchange server 2010 use to store the mail,
    if I elaborate more when one user sends a mail to few people in the same organization does that mail copies to every users mail box or exchange just uses the referencing method to one single mail.
    please help one of my clients using DAG in exchange 2010 and their mail box sizes increasing rapidly. I need to provide a solution to them. please let me know if you want more details
    please help me with some links that reveals about these in detail.
    thanks In Advance.

    Every mailbox will get a copy of the message. Single Instance Storage (SIS) is history.
    Dude, Where's My Single Instance?
    http://blogs.technet.com/b/exchange/archive/2010/02/22/3409361.aspx
    Martina Miskovic

  • Exchange 2010 Mail Submission Service Logging

    Hi,
    Is there a way to log all submitted messages from outlook clients (online mode) so I can see what is happening to messages that are getting stuck in the Outbox from the server's perspective?
    Thank you.

    If you look at the logging section in this post
    http://blogs.technet.com/b/rmilne/archive/2013/11/20/exchange-2010-tweaks.aspx
    add key="LoggingTag" value="ConnectDisconnect, Logon, Failures, ApplicationData, Warnings, Throttling" />.
    You can also add ROP logging, which are the individual Outlook commands sent, by adding the tag to the above line.
    This gets *VERY* busy.  *VERY* quickly, so maybe try this out on a test box first to see what that gives you.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 - Mail redirect

    Hello,
    i want to set up my Exchange Server 2010 to pass ALL e-mails he recives on 192.168.137.102:25, to the "Filter" which is listening on IP address 192.168.137.103:25, then after it filters the email (for example delete some vulgarisms) it will
    send them to my Exchange listening on 192.168.137.102:10025 and then the email will be send to users mailbox.
    I've already Set up:
    - send connector: Address space: SMTP *,  Smarthost: filter.<my_domain>, Source server: <my exchange>
    - recive connector: listening All Available IPv4 on 10025, Recive mail from: 192.168.137.103 (my filter IP).
    However it don't work propperly. My Filter don't see any traffic, so no data is passed to it from the Exchange. Could you please tell me what else i should configure to have this thing works as i want it to?
    Thanks,
    Michael

    Here you go:
    http://blogs.technet.com/b/exchange/archive/2013/01/21/how-to-write-an-exchange-2013-transport-agent.aspx
    https://msdn.microsoft.com/en-us/library/office/dd877033%28v=exchg.140%29.aspx
    http://www.c7solutions.com/2012/10/creating-simple-exchange-server-html
    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

  • Exchange 2010 - Mail Database Recovery after Database Portability Applied

    Background:
    We had a city-wide power failure  at Office A and as a result Exchange Server A (ES-A) was taken offline for an extended period of time.  The last good backup of ES-A-DB was from the previous business day.  The DR plan was enacted and the
    ES-A mailbox database (ES-A-DB) was recovered to Exchange Server B (ES-B) as ES-B-DB2.  Keeping in mind that a days worth of emails still reside on ES-A-DB.
    Process:
    I employed the database portability method when restoring the ES-A-DB to ES-B-DB2 at Office B.  I rehomed the exchange users in active directory to now use ES-A-DB2.  Users are working fine, activesync worked without issue.  All is well.
    I now face the situation where power has been restored to Office A and the server is available.  I have NOT turned this server on yet as I am not sure what the net affect will be on ES-A and ES-A-DB.
    The primary goal of the business is to recover the mail items from the missing day that was not backed up and recovered to ES-B-DB2.  What would be the best way to do achieve this objective?  
    This is what I am thinking, though its all theoretical since I've never been in this situation.
    - boot the Exchange Server with the network card disconnected
    - Dismount ES-A-DB from ES-A
    - Remove ES-A-DB from Exchange Org on ES-B
    - Process logs and put the ES-A-DB in a Clean state
    - mount as recovery database
    - copy differential mail items to ES-B-DB2 mailboxes
    Anyone have insight on this?
    Thanks for your help in advance.

    No need to dismount , remove from the org or boot the server w/o a NIC. The association between Exchange and the user is in AD and you already changed that when you set the new database with database portability.
    I would just follow the instructions for restoring back to their current production mailboxes (DB2).
    http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
    Try it with a sample mailbox or two and see how it handles the conflict resolution for duplicates.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2010 Mail Enabled Distribution Group Won't Receive from External Address

    Let me pre-empt the usual first response: yes, I've unchecked "require that all senders are authenticated" on the Message delivery Restrictions properties of Message Delivery Restrictions. I cannot get a message from an external mail server to
    send to an internal mail-enable distribution group. It's working internally. I've checked our ironport and the message is being sent to exchange (at least I think it is).
    How can I troubleshoot this?!
    tfgeorge

    Ironport is definitely sending this email to exchange. Please read:
    06 Jun 2011 08:53:20 (GMT -05:00)
    Protocol SMTP interface Main Interface (IP Gateway IP) on incoming connection (ICID 17720578) from sender IP 65.54.190.154. Reverse DNS host bay0-omc3-s16.bay0.hotmail.com verified yes.
    06 Jun 2011 08:53:20 (GMT -05:00)
    (ICID 17720578) ACCEPT sender group UNKNOWNLIST match sbrs[-1.0:6.0] SBRS 3.0
    06 Jun 2011 08:53:20 (GMT -05:00)
    Start message 2136865 on incoming connection (ICID 17720578).
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 enqueued on incoming connection (ICID 17720578) from
    [email protected].
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 on incoming connection (ICID 17720578) added recipient ([email protected]).
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 contains message ID header '<[email protected]>'.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 original subject on injection: TEST
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 (1471 bytes) from
    [email protected] ready.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 matched per-recipient policy DEFAULT for inbound mail policies.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine: CASE. Interim verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine CASE. Interim verdict: definitely negative.
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Spam engine: CASE. Final verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Virus engine Sophos. Interim verdict: CLEAN
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 scanned by Anti-Virus engine. Final verdict: Negative
    06 Jun 2011 08:53:20 (GMT -05:00)
    Message 2136865 queued for delivery.
    06 Jun 2011 08:53:20 (GMT -05:00)
    SMTP delivery connection (DCID 1658840) opened from IronPort interface 100.100.100.100 to IP address 100.100.100.100 on port 25.
    06 Jun 2011 08:53:20 (GMT -05:00)
    (DCID 1658840) Delivery started for message 2136865 to
    [email protected].
    06 Jun 2011 08:53:21 (GMT -05:00)
    (DCID 1658840) Delivery details: Message 2136865 sent to
    [email protected]
    06 Jun 2011 08:53:21 (GMT -05:00)
    Message 2136865 to
    [email protected] received remote SMTP response '2.6.0 <[email protected]> [InternalId=919833] Queued mail for delivery'.
    tfgeorge

  • Exchange 2010 Mail Security TLS with HSBC

    Dear all,
      I have setup an all-in-one exchange server without edge server role. However, it is needed to have TLS mail communication setup with HSBC. May I know what exactly configuration do I need? Do I need to implement an edge server with public cert?
      Can I enable TLS without edge server and with self-signed cert?
    Thanks a lot
    Best Regards,
    Elroy

    Hi,
    it's not possibile to connect on TLS with HSBC without a public CA certificate. Not selfsigned is permitted.
    No edge server it's mandatory.
    Import certificate on Exchange computer store and set it to use with SMTP service:
    Enable-ExchangeCertificate
    -Thumbprint CERTTHUMBPRINT -Services SMTP
    You need to create a custom send connector, complete domain scope with all HSBC domain and set bridgehead Exchange server. After the send connector creation set the Enforce TLS:
    Set-SendConnector CONNECTORNAME -RequireTLS $true
    Be careful to default internet receive connector that accept TLS connection.
    This is a good site for testing: https://www.checktls.com/
    Bye bye.
    Raffa!

  • Exchange 2010 - Mail contacts - Set as Reply property

    As mail contacts will probably use an external and unknown server to send replies for their mail. I don't understand the purpose of this property for mail contacts ?
    Is it only here because one console developer have missed to gray it out or is there a real utility ?
    Thank you for that clarification !

    Hello,
    Based on your description, I understand that you create mail-contact with two e-mail address:[email protected] and
    [email protected] (set as external address). You want to understand that if the mail-contact reply to these mail from his private mail system, the sender mail will be
    [email protected] and not
    [email protected]
    If so, I consider when the mail-contact reply to these mail from his private mail system, the sender is
    [email protected]
    Based on my experience, you can set any SMTP address as external address, but the address must be resolved.
    If I have any misunderstanding, please free let me know.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Internal Mail Routing Between HUB servers Is Not Working Correctly

    Howdy, Been scratching my head on this one for a while. 
    First off, running Exchange 2010 Sp3 RU5 across the board. 
    I have attached a diagram of our environment for visual aid. Please take a look as it makes more sense. 
    I have drawn the correct mail flow in black and what is happening in red.
    Forest A Site A, has a dedicated edge, dedicated Hub and dedicated CAS 
    Forest A Site A child domain 1, has a multi-roled MBX,HUB,CAS
    Forest A Site B child domain 2, has a multi-roled MBX,HUB,CAS
    Forest B Site C, has a multi-roled MBX,HUB,CAS
    Mail flows TO child domain 2 just fine, but outgoing mail from that same domain keeps routing through HUB in child domain 1 instead of HUB in forest root domain. 
    The send connector for the organization in Forest A is configured to only send through the dedicated HUB server in Forest A. The Receive connector in Forest A's HUB is also configured correctly. But no matter what i do, mail outgoing from child domain
    2 continues to flow to child domain 1 instead of through the dedicated HUB server. 
    Mail needs to flow so for now i added the HUB in child domain 1 as a source server in the organization's send connector and set up the receive connector in child domain 1 to allow a work around for now. 
    I think this is an issue in the routing group connector but its just a guess. Any ideas? 

    Hi,
    Active Directory IP site links costs are based on relative network speed compared to all network connections in the WAN and are designed to produce a reliable and efficient replication topology. Therefore, in most cases, the existing IP site link costs should
    work well for Exchange 2010 message routing. However, if after documenting the existing Active Directory site and IP site link topology, you verify that the Active Directory IP site link costs and traffic flow patterns aren't optimal for Exchange 2010, you
    can make adjustments to the costs evaluated by Exchange.
    You can use the Set-AdSiteLink cmdlet to assign an Exchange-specific cost to an Active Directory IP site link.
    More details refer to the following articles:
    Controlling IP Site Link Costs
    Set-AdSiteLink
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Disater Recovery for exchange 2010 plan.

    Hi All,
    Happy New year 2014 ....
    we have running with exchange 2010 R1 with DAG enabled. we have below mentioned setup in our exchange server.
    Main site.
    Active directory server ( Primary DC, additional DC in our main site)  installed in Hyper V  host. installed exchange 2010 mail box role in another Hyper V host.  installed the CAS& Hub role in another virtual host and installed the Exchange
    edge role in another physical server.
    DR Site
    Active director server( ADC) installed in Hyper V host. installed the Exchange 2010 mailbox,Hub,Cas server role in a physical server. installed the Edge Server in another physical server.
    At present we have enabled the failover DAG  for both our Mail box servers and its working perfectly when the primay mail box server down. we have run some commands to transfer all my exchange 2010  to point through our DR Site. so its take
    some of the minutes of down time happened in our mail flow.  we are planning to avoid that downtime. we  are find for the solutions like  if the primary site down  the DR will need to automatically up. it will be appreciate that any
    one  provide your suggestion to achieve this without affecting the  our current setup.
    Jags

    Hello,
    Kindly find the 3 types of plan for Exchange 2010 DR site. You can check all 3 plans and select as per your requirement.
    1. Rebuild an Entire Database Availability Group plan
    http://technet.microsoft.com/en-us/library/gg513521.aspx
    2. Site Resiliency in Exchange 2010
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html
    3. Exchange 2010 Cross Site DAG Disaster Recovery: Data Center/AD Site failure Part 1
    http://msexchangeguru.com/2012/10/25/exchange-2010-dag-dr/
    Deepak Kotian. MCP, MCTS, MCITP Exchange 2010 Ent. Administrator

  • Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

    Hi
    We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
    The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
    type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
    relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
    2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
    The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
    2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
    We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
    from happening.
    We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
    problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
    existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
    This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
    to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
    Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
    Thanks
    Nauman.

    Hello,
    Why do you want to use the 'internal relay domain' authentication?
    Thanks,
    Simon Wu
    TechNet Community Support

Maybe you are looking for