Exchange 2013 not delivering mails to Exchange 2010

I am upgrading exchange 2010 to exchange 2013 and currently in coexistence.  I cutover the mx to deliver mail to 2013 cas VIP last night and no mail was being received by the 2010 mailboxes, it was all being queued on the 2013 mailbox servers (mailbox
and cas servers are separate in this deployment.) There are only a few 2013 mailboxes as I have not yet started migrating them.  These 2013 internal mailboxes can not send to exchange 2010 either, but 2010 can send to 2013. 2013 to 2013 mail works
fine. I have read somewhere about an issue with a receive connector having the same ip range that includes the mailbox servers, but I'm not clear on really which mailbox servers it is alluding to.
All the exchange 2010 servers are all on the 10.1.1.* network.  Exchange 2013 CAS servers are all on the 10.1.1.* network and the 3 exchange mailbox servers are on 10.1.1.*, 10.1.2.* and 10.30.5.*.  Only 1 AD site.  On one of the 2010 receive
connectors there is a scope of 10.1.1.0/24  I'm wondering if this is the culprit and by removing it should fix the problem.  Any other ideas would be appreciated.

Exchange 2013 users are unable to send emails to exchange 2010 users then check your connectors on Exchange 2013 Mailbox server. and yes if you have overlapping of scopes in different connectors then this can happen.
Kindly mark this as answer if found helpful. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Similar Messages

  • Exchange 2013 not delivering all emails

    Hi All,
    I have a fresh install of Exchange 2013 SP1 with CU5 on Windows Server 2012 R2 and I am having a weird mesage delivery issue. 
    Im getting most emails, but some messages I am not getting. They don't show up in my inbox. If i do a Get-MessageTrackingLog, the EventID is listed as FAIL
    [PS] C:\Users\Administrator\AppData\Roaming\ClassicShell\Pinned>Get-MessageTrackingLog -MessageSubject "Balance Snapshot" -Start "7/20/2014" | FL
    RunspaceId              : 06baa1a8-4732-49df-b00c-0a685d5e75fb
    Timestamp               : 7/20/2014 10:43:05 AM
    ClientIp                : xxx.xxx.xxx.xxx
    ClientHostname          : DC1
    ServerIp                : 192.168.0.4
    ServerHostname          :
    SourceContext           : Sender Id Agent
    ConnectorId             : DC1\Default DC1
    Source                  : SMTP
    EventId                 : FAIL
    InternalMessageId       : 1275605286912
    MessageId               : <[email protected]>
    Recipients              : {[email protected]}
    RecipientStatus         : {[{LRT=};{LED=250 2.6.0 <[email protected]>
    Queued mail for delivery};{FQDN=};{IP=}]}
    TotalBytes              : 0
    RecipientCount          : 1
    RelatedRecipientAddress :
    Reference               :
    MessageSubject          : Balance Snapshot: Your Available Balance
    Sender                  : [email protected]
    ReturnPath              : [email protected]america.com
    Directionality          : Incoming
    TenantId                :
    OriginalClientIp        :
    MessageInfo             :
    MessageLatency          :
    MessageLatencyType      : NoneEventData               : {[DeliveryPriority, Normal], 
    I have verbose logging turned on, and its showing the log of the email that is not getting delivered, but no errors. Any ideas?
    Brad Nelson MCSE/DCSE/A+/Network+/WCSP

    Hi,
    From your description, I recommend you disable the Postini anti spam temporarily to determine whether this issue is related to it.
    I look forward to your response.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 cannot deliver mails

    Hello,
    We purchased and installed an Exchange server 2013 and a domain name ''alaa.com''. Just before purchasing the domain name, we installed exchange, we kept almost everything in default setting and we added an MX INTERNAL Send Connector. We were able to send and
    receive internal mails. However, when we purchased the domain name and configured the MX record to point to mail.alaa.com the following happened:
    1/ we can send external mails
    2/ internal mails leave the Drafts folder but never delivered (sent but not received).
    3/ Cannot receive mails sent from the internet. However we receive an email from [email protected] that says this:
    http://txt.do/138s
    and sometimes this:
    http://txt.do/138a
    Please, this is urgent, We would really appreciate your help.

    Hi,
    I cannot see reverse DNS record for "sst.com.tn".
    You must create reverse DNS record for delivery to external mail address.
    Also, I cant open link http://txt.do/138s and http://txt.do/138a

  • Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured

    Exchange 2013 not receiving emails above 10MB even though MessageReceive Size has been configured.
    [PS] C:\Windows\system32>Get-TransportConfig
    AddressBookPolicyRoutingEnabled                             : False
    AnonymousSenderToRecipientRatePerHour                : 1800
    ClearCategories                                            
    : True
    ConvertDisclaimerWrapperToEml                               : False
    DSNConversionMode                                          
    : UseExchangeDSNs
    ExternalDelayDsnEnabled                                     : True
    ExternalDsnDefaultLanguage                                  :
    ExternalDsnLanguageDetectionEnabled                         : True
    ExternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority                               :
    ExternalDsnSendHtml                                        
    : True
    ExternalPostmasterAddress                                   : [email protected]
    GenerateCopyOfDSNFor                                        :
    HygieneSuite                                               
    : Standard
    InternalDelayDsnEnabled                                     : True
    InternalDsnDefaultLanguage                                  :
    InternalDsnLanguageDetectionEnabled                         : True
    InternalDsnMaxMessageAttachSize                             : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority                               :
    InternalDsnSendHtml                                        
    : True
    InternalSMTPServers                                        
    : {127.0.0.1}
    JournalingReportNdrTo                                       : <>
    LegacyJournalingMigrationEnabled                            : False
    LegacyArchiveJournalingEnabled                              : False
    LegacyArchiveLiveJournalingEnabled                          : False
    RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
    RedirectDLMessagesForLegacyArchiveJournaling                : False
    MaxDumpsterSizePerDatabase                                  : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                                            
    : 7.00:00:00
    MaxReceiveSize                                             
    : 50 MB (52,428,800 bytes)
    MaxRecipientEnvelopeLimit                                   : 5000
    MaxRetriesForLocalSiteShadow                                : 2
    MaxRetriesForRemoteSiteShadow                               : 4
    MaxSendSize                                                
    : 20 MB (20,971,520 bytes)
    MigrationEnabled                                           
    : False
    OpenDomainRoutingEnabled                                    : False
    RejectMessageOnShadowFailure                                : False
    Rfc2231EncodingEnabled                                      : False
    SafetyNetHoldTime                                          
    : 2.00:00:00
    ShadowHeartbeatFrequency                                    : 00:02:00
    ShadowMessageAutoDiscardInterval                            : 2.00:00:00
    ShadowMessagePreferenceSetting                              : PreferRemote
    ShadowRedundancyEnabled                                     : True
    ShadowResubmitTimeSpan                                      : 03:00:00
    SupervisionTags                                            
    : {Reject, Allow}
    TLSReceiveDomainSecureList                                  : {}
    TLSSendDomainSecureList                                     : {}
    VerifySecureSubmitEnabled                                   : False
    VoicemailJournalingEnabled                                  : True
    HeaderPromotionModeSetting                                  : NoCreate
    Xexch50Enabled                                             
    : True

    hi stephan... lets put in this way... are you sending attachment ...did you checked the max attachment size as mail send size and attachment size are two different things.. please check this for info on different size creteria
    http://technet.microsoft.com/en-us/library/bb124345%28v=exchg.150%29.aspx
    can you please share the output of below three commands... i doubt your receive connector is not configured properly.
    Get-TransportConfig | Format-List -Property MaxReceiveSize, MaxSendSize
    Get-SendConnector | Format-List -Property Identity, MaxMessageSize
    Get-ReceiveConnector | Format-List -Property Identity, MaxMessageSize
    you can also check this link which gives a perfect info on how exchange works for email size... http://rajisubramanian.wordpress.com/2014/01/26/exchange-server-2013-message-size-configuration-detail/
    Mark as useful or answered if my replies helped you solving your query.
    Thanks, Happiness Always
    Jatin
    Skype: jatider2jatin, Email: [email protected]

  • Is exchange 2013 support thunderbird mail

    Is exchange 2013 support thunderbird mail?
    Akhilraj

    Yes. add imap account for email.
    Add the following addon (or the latest version of the same add-on) for calendar
    http://www.1st-setup.nl/extensions/exchangecalendar-3.2.0-Beta77.xpi

  • Exchange 2013 - The connection to Microsoft Exchange is unavailable

    Hi there,
    i have some problems on my new Exchange 2013 Server: Here is the topology:
    1 serveur 2012 in workgroup with the Hyper-V role
    2 VM: DC2012 is the DC of the domain: intra.mydomain.com, Windows 2012
    The other VM is member of the domaine, Windows 2012, Exchange 2013 SP 1 installed.
    So, i have dc2012.intra.mydomain.com and mail1.intra.mydomain.com (another DC: DC2008, name: dc2008.intra.mydomain.com)
    I have some troubles with the SSL and the connexion of Outlook outside the LAN.
    In the LAN on a client, i launch Outlook 2010 and the autodiscver make the rest. The connexion is ok.
    But i have a client not in the LAN, so i configured a SSL. I made a request. First Question:
    In the ECP, Server, Certificate, i have 3 times "Microsoft Exchange Server Auth Certificate" and 3 times "Microsoft Exchange" with differents dates. Why?
    I installed my PKI on the DC2012, and paste the request and download the certificate. I retuned on the exchange server in ECP, Server, Certificate and treat the pending request. In Services i checked IMAP, POP, IIS, SMTP.
    Then, in Server, Server, Mail1, OutlookAnywhere, in url extternal: mail.mydomain.com and Authentification: NTLM.
    In ECP, Servers, Virtual Directories i wrote the same url external and internal: mail.mydomain.com for ECP, OWA, ActiveSync, OAB.
    In my DNS on the DC, i created a CNAME record for mydomain.com et i created a A record for mail. on a client if i make nslookup then mail.mydomain.com the IP is the LAN IP of my exchange server.
    I modified the MX record of my public domain: mail.mydomain.com to point on my Public IP. That works.
    On the client outside of the LAN, i installed the root certificate and the exchange certificate.
    second question:
    Why my client outside of the LAN can't connext with outlook.
    Thanks a lot for your answers and sorry for the long post.
    Alex

    I resolved my problem!
    here is the solution that solved it:
    actually, i tried to connect Outlook 2010 ti Exchange 2013. I knew that Exchange now connect Outllok via rpc over http(s), BUT, the Autodiscover (in LAN) transform the field server to something like that:
    [email protected] , the xxx correspond to the GUID of the mailbox. So, for my remote user, i launch this command on Exchange 2013:
    Get-Mailbox test | fl name, exchangeguid , it give to me the GUID, then in te field "Server" i fill ([email protected]): [email protected]
    And in advanced parameters, same things i mentioned in previous post. And it works!!!!!
    Thanks to me.

  • Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

    Hello guys,
    I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
    When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
    When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
    We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
    What should I check and configure to make it work?

    Hi,
    I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
    By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
    A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
    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

  • Exchange Server 2013 does not deliver mail as they arive.

    I need Help and guidance on this problem. I have installed Exchange server 2013 with SP1 on Server 2012. Install Went perfect no error. It on a server with 2 TB storage. 16G
    memory. Exchange 2013 is the only application running on the box. DNS service is also running on the box. I can see the mail arrive in the mail Box Queue with the Queue Viewer and they would just sit there and then after a 15 to 30 min delay it release the
    mail to the mail boxes. The only error or warning I am seeing in the logs are the 6002 warning. Any suggestion would be greatly appreciated.

    Please share message header of one of the delayed message. It will help to narrow down the issue.
    Do you see any connection failures in connectivity logs.
    Do you have multiple 2013 servers in your exchange environment ?
    Lets fix it.
    Received: from Xchngsvr.A.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
     (xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32 via Mailbox
     Transport; Fri, 25 Apr 2014 13:31:33 -0400
    Received: from Xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
     (xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 25 Apr
     2014 12:30:44 -0400
    Received: from xchngsvr.a.com (xxx.xxx.xxx.xxx) by Xchngsvr.a.com
     (xxx.xxx.xxx.xxx) with Microsoft SMTP Server id 15.0.847.32 via Frontend
     Transport; Fri, 25 Apr 2014 12:30:37 -0400
    Received: from mia0vm-cass03.colo.sonicwall.com ([208.17.117.5])        
    by
     xchngsvr.a.com (SonicWALL 7.4.5.1391)               
    with ESMTP id 201404251630370000228;
     Fri, 25 Apr 2014 12:30:38 -0400
    Received: from mail1.fieldsolutions.com ([98.129.95.107])           
    by
     mia0vm-cass03.colo.sonicwall.com (SonicWALL 7.4.4.8439)        
    with ESMTP id
     201404251631070343409; Fri, 25 Apr 2014 09:31:07 -0700
    Received: from localhost (localhost [127.0.0.1]) by mail1.fieldsolutions.com
     (Postfix) with ESMTP id F32731031781  
    for <[email protected]>; Fri, 25 Apr 2014
     11:31:06 -0500 (CDT)
    MIME-Version: 1.0
    To: <[email protected]>
    From: Field Solutions <[email protected]>
    Subject: WIN#: 649890 NEW Signage - Reply-To: <[email protected]>
    Content-Type: multipart/alternative;
    boundary="=_747eac72d0ea92652b25d7d469d7165b"
    Message-ID: <[email protected]>
    Date: Fri, 25 Apr 2014 11:31:06 -0500
    X-Mlf-KeyWords: preapproved,dollars$$$,pay,toner,expectations,fl,dollars,guarantee,voltage,confi
    X-Mlf-Language-Detected: NoLanguageFilter_English
    X-Mlf-Connecting-IP: 50.244.134.141
    X-Mlf-Country-Code: US
    X-Mlf-Rules: rn;7.24
    X-Mlf-Rules-Pos-Features: WORD_voltage_2.97;WORD_configuration_2.51;WORD_inputs_2.50;WORD_documentation_2.
    X-Mlf-Rules-Neg-Features: WORD_preapproved_-1.85;SUBJ_dollars$$$_-1.74;SUBJ_pay_-1.56;WORD_toner_-1.53;WOR
    X-Mlf-Sliderbars: N4,B4,S4,L4,Q4,G4,A4,I4
    X-Mlf-Version: 7.4.4.8439
    X-Mlf-Threat-History: nothreat
    X-Mlf-Threat-Detailed-History: nothreat;none;none;none
    X-Mlf-UniqueId-History: i201404251631070343409
    X-Mlf-Connecting-IP: 208.17.117.5
    X-Mlf-Country-Code: --
    X-Mlf-Threat: nothreat
    X-Mlf-Threat-Detailed: nothreat;none;none;cloud-nj
    X-Mlf-UniqueId: i201404251630370000228
    Return-Path: [email protected]
    X-MS-Exchange-Organization-Network-Message-Id: 5ea15b9c-561d-4a2a-d03e-08d12ebad75d
    X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
    X-MS-Exchange-Organization-AuthSource: Xchngsvr.a.com
    X-MS-Exchange-Organization-AuthAs: Anonymous
    There is only one Exchange server in the Organization

  • Exchange 2013 user cannot mail 2010 user

    Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
    Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
    I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
    on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
    - thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
    Cheers, db.

    Hi Dennis,
    if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
    1. run a Powershell or CMD
    2. telnet exchange2013server 25
    Does it connect using the Exchange 2013 CAS / Transport Server Name?
    If no, please check
    1. is there any anti Virus / Firewall Software blocking the Connection?
    2. is there any Firewall on the Network blocking the SMTP Connection?
    3. does your receive connector include the subnet of your Exchange 2013 CAS server?
    If you cannot connect verify please the remote IP range includes your new servers ,  check it running
    Get-ReceiveConnector  | fl name,binding,remoteipranges
    from Powershell. If required, use set-receiveconnector to Change it.
    http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
    Regards,
    Martin

  • Out of office replies in Exchange 2013 not working for external recipients

    Hi,
    Few days ago a couple of company workers went to vacation. They set up OOF automatic replies in OWA 2013. However automatic replies are not working for external recipients (outside of company). Internal users (company users) receive OOF notification.
    I'm using smart host in sender connector configuration (SMTP server of internet provider) to deliver emails. Any clues about this problem ? Please find below part of the transaction log. For testing purposes i set up administrator account
    to be on vacation.
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    DROP     ROUTING 
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    TRANSFER ROUTING  [email protected]           
    {[email protected]}             Automatic reply: vacation test
    FAIL     SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test

    Hi Informus,
    Please check if it is allowed in AllowedOOFType of the Remote Domain *
    In Exchange 2013, the only way to see or change the current configuration for automatic replying and forwarding to the Internet is via the Exchange Management Shell (EMS) with PowerShell commands.
    To get the currently configured Remote Domains, use:
    Get-RemoteDomain
    Name                           DomainName                                  
    AllowedOOFType
    Default                        *                                           
    External
    Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled
    AllowedOOFType     : External
    AutoReplyEnabled   : False
    AutoForwardEnabled : False
    To change the settings, use the Set-RemoteDomain command.
    Enable automatic replies
    Set-RemoteDomain -AutoReplyEnabled $true
    Enable automatic forwards
    Set-RemoteDomain –AutoForwardEnabled $true
    Enable OOF for Outlook 2003 and previous (for Exchange 2007 and 2010 support)
    Set-RemoteDomain –AllowedOOFType $ExternalLegacy
    To change all these properties at once, you can use:
    Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy
    Note:
    Valid settings for the AllowedOOFType property are:
    External
    This is the default and only allows for the new style OOF messages as introduced in Outlook 2007.
    ExternalLegacy
    This settings allows for both the new style and old style OOF messages and needs to be set if you want to enable external OOF support for Outlook 2003 as well.
    None
    This setting doesn’t allow for the use of OOF messages at all (both internal and external).
    InternalLegacy
    This setting only allows for internal OOF messages to be sent for all Outlook versions.
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2013, scan-to-Mail, Attachments broken down to mime tipes

    Good day
    I recently installed Exchange 2013 to our domain. 
    The problem i'm facing is that any scan to email document gets delivered as the following  :
    This is a multi-part message in MIME format.
    --DC_BOUND_PRE_<1361347488.00267327e1cb>
    Content-Type: text/plain; charset=US-ASCII
    Content-Transfer-Encoding: 7bit
    --DC_BOUND_PRE_<1361347488.00267327e1cb>
    Content-Type: application/pdf; name="20130220090448407.pdf"
    Content-Transfer-Encoding: base64
    Content-Dis;
                    filename="20130220090448407.pdf"
    JVBERi0xLjQKJeLjz9MKNCAwIG9iago8PC9UeXBlL1hPYmplY3QKL1N1YnR5cGUvSW1hZ2UK
    L1dpZHRoIDE2NTYKL0hlaWdodCAyMzM5Ci9CaXRzUGVyQ29tcG9uZW50IDEKL0NvbG9yU3Bh
    Y2UvRGV2aWNlR3JheQovRGVjb2RlWzEgMF0KL0xlbmd0aCA0ODQxNzMKPj4Kc3RyZWFtCgAA
    AAAAAAAAAAAAAEAl+3vv///+gAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAF9
    gAAAbgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
    AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFZK26AAAAAAAAAAAAAAA
    And it goes on for this for a couple hundred more lines. 
    I have tested the following
    Scanning to any email address outside my domain, work 100% 
    Any scanner sending mail-to-pdf from outside my organization it get delivered as above
    I have changed smtp servers to our ISP and that also delivered as abve
    I change the sending address of scan-to-mail machine to gmail account, also delivered as above, but to my non domain email address it works perfectly 
    Please help 

    one of our clients had the same problem before, he have Richo printer with scanner witch is scanning to pdf file attached to email , this printer  is working fine by using Exchange 2010 but has that problem after the migration to exchange 2013, this
    problem is totally fixed after installing Exchange SP1 (CU4). I found others say this problem is fixed by just installing CU1.
    for more information about content conversion
    http://technet.microsoft.com/en-us/library/bb232174.aspx#External

  • Exchange 2013 - Cannot sent mail warning to user (Quota)

    Hi all,
    I have an enviroment with Exchange Server 2013 SP 1 (Version 15.0 (Build 847.32)). (DAG)
    My problem is that my users not recieve mail of notification (warning).
    I did a lot search, but i didnt found any solution.
    I already moved a mailbox to another database, but the user received mail once.
    Any idea?
    I see in forum MS that it can be a problem of Exchange.
    Marco

    Hi Marco,
    From your description, I recommend you use the following cmdlets to verify the quota status of mailbox.
    If you want to verify the status of individual mailbox quota, use the following cmdlet:
    Get-MailboxStatistics DisplayName | ft *quota*,*size -AutoSize –Wrap
    If you want to verify the status of the mailbox quota for all the mailboxes that are hosted on a database, use the cmdlet below:
    Get-MailboxStatistics -Database DatabaseName | ft displayname,*quota*,*size -AutoSize –Wrap
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 CAS server connection to Exchange 2010 Mailbox server

    Hi Guys,
    I have a quick question i am planning to upgrade my infra from Exchange 2010 to Exchange 2013 and i have come across a small question, my infra looks likes below
    3 Exchange server (CAS+ HT + MBX roles) Exchange 2010
    1 Exchange server MBX role For journlaing Exchange 2010
    1 CAS for internet owa access Exchange 2010
    Now i will be  installing exchange 2013 CAS on 2 box and MBX on 3 box 
    will decomm the 3 exchange box which has (CAS+ HT + MBX roles) and 1 CAS which we use for owa access.
    will keep the Journaling server as it is will not be decomming it as of now.
    My question is is will i be able to connect to the journaling mailbox's which are hosted on exchange 2010 journaling server without actually having any 2010 cas server, will exchange 2013 cas directly help me to connect to the journal mailbox or would i need
    to add CAS role on Exchange 2010 journaling server and enable outlook anywhere configure the directories with the url's to make it working.
    Please suggest on the same.
    BR/Deepak

    Hi TheLearner,
    Thank you for your question.
    Exchange 2013 didn’t connect to the journal mailbox directly when we access it by outlook/OWA. The journal mailbox will connect the former Exchange 2010 CAS. Or we could migrate Journaling mailbox to Exchange 2013. Because Exchange 2010  could communicate
    with Exchange 2010 by RPC, but Exchange 2013 could communicate with Exchange 2013 by HTTPS.
    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

  • Exchange 2013 not receiving internal and external emails ..

    I have a coexistence of exchange 2007 and exchange 2013 ..2013 mailboxes where able to receive and send mails (internal and external) but suddenly the mail flow has stopped. 
    Mail flow status
    2013 to 2007 = OK
    2013 to internet = OK
    2013 to 2013 = OK
    2007 to 2013 = FAIL
    Internet to 2013 = FAIL 
    incoming internet mails return the NDR below
    Diagnostic information for administrators:
    Generating server: mydomain.com
    [email protected]
    Remote Server returned '< #4.4.7 smtp;400 4.4.7 Message delayed>'
    What could be a possible reason for this? 
    Cheers guys ..
    ..forever is just a minute away*

    Hi Richard,
    Thank you for your question.
    When there is a coexistence of Exchange 2007 and Exchange 2013, external email will be sent and received by Exchange 2013.
    4.4.7 means message expired, message wait time in queue exceeds limit, potentially due to remote server(your Exchange server ) being unavailable.
    If your organization has correct MX record in ISP. We could refer to the following link to check if MX record is correct:
    http://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx
    If we could telnet Exchange server by the following command: telnet mail.domain.com 25
    If there is a receive connector on Exchange 2013 to receive Internet emails, we could create a receive connector to receive message from the Internet by the following link:
    http://technet.microsoft.com/en-us/library/jj657447(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • N8 Mail for Exchange (can not send mails)

    Hi guys,
    I just got my new Nokia N8. I already setup Mail for Exchange via IMAP to sync the mails, contacts and the calendar of my private mailbox.
    Everything runs alright. But I can not send mails via Mail for Exchange. If I push on "New Mail" the program say the command can not be executed and breaks down.
    Does someone know how to fix that problem?
     Thanks from Liechtenstein.
    Phil

    Hi,
    I also had problems with unable to send emails.
    I was getting error messages in the Mail for Exchange (MfE) log files such as
    Setting DISK FULL status to false
    Error occurred during sending mail. Setting status to waiting for reconnect
    HTTP failure while sending messages.
    I figured out a work around. The problem seemed to be with the certificate.
    I ended up deleting the certificate and then only selecting "Accept this time only" which made everything work.
    I am using a Nokia 5800.
    To delete a certificate goto
    Setting > Phone > Phone mgmt > Security > Certificate Management > Trusted site certificates
    find the offending certificate and delete it.
    The next time I tried to synchronize my emails with Mail for Exchange, I was asked to select whether to accept the certificate... press the option button.
    Then select "accept this time only".
    After doing that, the emails in the outbox were sent properly.
    I have to figure out how to get this to work permanently, but for the moment it was a quick fix.
    [I hope this helps. I tried to be as descriptive as possible and write with correct spelling so that search engines will collect it.]

Maybe you are looking for