Exchange Server 2013 Timestamp on Email

We have just had to resync all our physical servers and VMs because the domain controller was issuing the wrong time and date. All VMs and physical servers and DCs now have the correct time and date. Now when I send an email from Outlook the sent date and
time is still a day ahead. The Exchange server is a VM and the system time and date is correct.
This also happens if I send myself an email through OWA.

Hi,
You need to restart the AD Topologic service to re-detect the new DC.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

  • 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 not receiving emails

    I have a new Exchange 2013 mail server installation (no migration - completely new domain and everything).  For some reason the server is not accepting mail from the Internet.  My router is indicating it is forwarding SMTP packets to the Exchange
    server's IP address, but nothing shows up in the message queues or users mailboxes.  The event viewer is giving me no clues.  No errors.  This is a simple installation - one Server 2012 DC and the Exchange server.  One Exchange server in
    a domain environment.  The receive connector looks correct.  It is using port 25 and I indicated to use the IP address of the Exchange server network card.  Any ideas as to how to configure the receive connector?  Thanks!

    Greylisted  is an anti spam check done on exchange. However to me this would meanone of two things.
    1: The inbound email domain is listed not your exchange server. Your Exchange server seems to be set up to only allow inbound mail from specific domains perhaps instead of * (All).
    2: More likely i think is that your domain is not set up in Exchange.
    In order to test the product you probably want to create your own domain, and that is easily done in the Exchange Admin Center by clicking the Mail Flow item
    and then Accepted Domains in the tab area and finally the Add… icon, <o:p></o:p>
    Type in the information and click Save,
    the new domain will show up on the List View.<o:p></o:p>
    For reference you can check if your domain is blacklisted here: http://mxtoolbox.com/blacklists.aspx but i am sure this is not your issue.
    Martin

  • Deploying Windows Server 2012 and Exchange Server 2013

    Hi All,
    Our Clinet is planning to implement Exchange Server 2013 as an email solution. There is no Active Directory Domain exists in the environment. So, we have planned to configure a Windows Server 2012 R2 Standard as a Domain Controller and Exchange
    Server 2013 Standard would be installed on another Windows Server 2012 R2 Standard.
    The setup would be for 250 users. Please guide me about the Cost of OS + Exchnage and CAL for 250 Users.
    Warm Regards,
    Prosenjit Sen
    Thanks & Regards, Prosenjit Sen.

    Another option would be to consider signing up for Office 365 instead of setting up the hardware and software for such a small number of users.  It will take a long time for the cost of the hardware, maintenance, and support to be less costly than Office
    365, if it would ever be less expensive.  There is a lot of maintenance required for Exchange, so unless your client already has someone experienced in configuring and maintaining Exchange, there is a lot of expense in bringing someone up to speed to
    perform those functions capably.
    Just a suggestion.  I do not work for Microsoft and I have no financial incentive to propose an Office 365 environment.  I just know that if I were running my own business, I would have to be convinced that my business required its own internal
    mail system when there are so many fully functional and capable mail systems available via subscription.
    . : | : . : | : . tim

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • 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: incoming messages are not delivered into user mailboxes occasionally

    Exchange Server 2013 CU1, two mailbox servers (DAG, only one mail database), two CAS servers (NLB cluster). Two Sendmail/CentOS-based SMTP relays route mail between Exchange servers and Internet (incoming mail is routed to NLB cluster name).
    Usually mail flow is OK: messages are sent and received normally. However, I've got several complains from different users. They state that occasionally they don't receive messages that were sent to them from outside. Tomorrow morning I've decided to
    investigate the issue.
    So, we have a message sent from Gmail account that was not delivered in user mailbox. It was received and routed to Exchange by Sendmail host:
    Jun 27 22:06:37 MX01 sendmail[12169]: r5RG6HC8012166: to=<USER_ADDRESS>, delay=00:00:19, xdelay=00:00:19, mailer=smtp, pri=124702, relay=NLB-FQDN [NLB-IP], dsn=2.0.0, stat=Sent (<CAHgK_sjEkj41htuVsutMP3XhgR5RRDs8-EgSC-UfHoaiHWFj=A@mail.gmail.com>
    [InternalId=13069585481819] Queued mail for delivery) 
    Running Get-MessageTrackingLog applet on the mailbox servers displayed the followed log entries for the message:
    DB Server #1:
        22:11:18 HAREDIRECT
        22:11:18 RECEIVE
        22:11:18 AGENTINFO
    DB Server #2:
        22:11:18 HARECEIVE
        22:12:44 HADISCARD
    So, we can see that the message was placed into shadow queues, but was NOT delivered into mailbox (no DELIVER status entries). Also pay attention to the timing. Time on all the servers is in sync, but Sendmail timestamp is 22:06, and Exchange timestamps
    are 5 minutes behind it.
    Today a message sent to the same address from the same Google mailbox was received by Exchange and placed into user mailbox with no glitches.
    We use Exchange antispam system activated on Exchange mailbox servers. Spam is never dropped silently. It is either returned to sender (SCL 9) or placed into quarantine mailbox (SCL 6 and above). I'm pretty sure that the lost message was not in the quarantine
    mailbox this morning, and the sender didn't receive any NDRs.
    Any ideas what to investigate next?

    Hi,
    Do you mean the emails are placed in the Shadow Redundancy queue?
    Shadow Redundancy
    http://technet.microsoft.com/en-us/library/dd351027(v=exchg.150).aspx
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 failing Readiness Checks

    Here are the list of errors it reports
    Error:
    Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
    My user is in the Enterprise Admins group.    
    Error:
    The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx
    My user is in the Enterprise Admins group and it is also in the Organization Management Role
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    I am
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    I am
    Error:
    Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have been created but have not yet replicated to the local domain.  Wait for replication to complete and then run setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    While this is showing up, I do have the Exchange objects availabe on all of my DCs in all of the sites.
    Error:
    The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
    Its currently at 2008 Which is the highest I can make it in my organization at this time.
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    I'm able to communicate with all the DCs from the machine I'm attempting to install exchange on.
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Has anyone encounterd this?  
    I've run Setup /PrepareSchema and Setup /PrepareAD on the DC in the site Exchange specified.
    I have installed all of the Prereqs
    Here's an example of my set up
    One Forest
    AwesomeCompany.net -
    There's Two sites
    Atlanta-HeadQuarters
    Atlanta-DataCenter
    and Two Sub Domains
    HeadQuarters
    DataCenter
    Exchange Machine is in Atlanta-DataCenter Site and attached to DataCenter domain.
    Exchange requested the /PrepareAD and /PrepareSchema be run on a Domain Controller in the root domain that is in site Atlanta-HeadQuarters.
    Any guidance would be appreciated.

    Hello,
    Just for double confirm, please run “WhoAmI” in CMDlet and see if you are using a local admin account.
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

Maybe you are looking for