none
New Exchange 2013 can receive ok but will not send mail to the internet

    Question

  • Hi All,

    I've recently installed EX2013 and when I tested mailflow I can send mail into our EX2013 mailboxes but for some reason I 

    18/01/2016 10:56:35 - Remote Server at gmail.com (2404:6800:4008:c01::1a) returned '550 4.4.7 QUEUE.Expired; message expired'
    18/01/2016 10:43:01 - Remote Server at gmail.com (2404:6800:4008:c01::1a) returned '441 4.4.1 Error encountered while communicating with primary target IP address: "Failed to connect. Winsock error code: 10065, Win32 error code: 10065." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 2404:6800:4008:c01::1a:25'

    Any help will be greatly appreciated it.

    Thank you.

    Monday, January 18, 2016 4:18 PM

Answers

  • Hi,

    I was correct there was a rule denying the new server, once I added an explicit rule for the server it worked!

    :) Thanks again for all your help.

    Tuesday, January 19, 2016 10:59 AM

All replies

  • did you do send connector? https://technet.microsoft.com/en-us/library/jj657457%28v=exchg.160%29.aspx


    Monday, January 18, 2016 4:39 PM
  • Hi, yes definitely created a send connector.
    Monday, January 18, 2016 4:48 PM
  • post result:

    get-receiveconnector | fl

    Monday, January 18, 2016 5:01 PM
  • Hi,

    Please confirm if you can't send to all domains or the specific domain.

    If your send connector uses DNS on the Internet to route mail, please use Nslookup to to verify MX record configuration:https://technet.microsoft.com/en-us/library/aa998082(v=exchg.65).aspx

    If you enable the protocol logging on the sender connector , please check the logs to see if anything helps to troubleshoot.

    We can try to run Microsoft Remote Connectivity Analyzer to check the issue, please select outbound SMTP email to test.

    https://testconnectivity.microsoft.com/

    Regards,

    David 

    Tuesday, January 19, 2016 7:06 AM
    Moderator
  • Hi,

    Thank you all for your helpful input, I'm trying to test the new mail server when I can (in between supporting users!) I've dedicated tomorrow all day to hopefully get it working.

    I've got a feeling it's something to do with our Cisco FW, as our current mail server can send but the new one can't when I run a packet trace it fails on the new server so trying to find the rule and will update you accordingly.


    Tuesday, January 19, 2016 9:56 AM
  • [PS] C:\Windows\system32>Get-SendConnector | fl


    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    CloudServicesMailEnabled     : False
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : False
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         :
    FrontendProxyEnabled         : False
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : OurServer
    Identity                     : <OurServer> SendMail
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    MaxMessageSize               : 35 MB (36,700,160 bytes)
    Name                         : <OurServer> SendMail
    Port                         : 25
    ProtocolLoggingLevel         : None
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {OurServer}
    TlsAuthLevel                 :
    TlsCertificateName           :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False

    AddressSpaces                : {SMTP:*;1}
    AuthenticationCredential     :
    CloudServicesMailEnabled     : False
    Comment                      :
    ConnectedDomains             : {}
    ConnectionInactivityTimeOut  : 00:10:00
    DNSRoutingEnabled            : True
    DomainSecureEnabled          : False
    Enabled                      : True
    ErrorPolicies                : Default
    ForceHELO                    : False
    Fqdn                         :
    FrontendProxyEnabled         : False
    HomeMTA                      : Microsoft MTA
    HomeMtaServerId              : OurServer
    Identity                     : NH-SendMail
    IgnoreSTARTTLS               : False
    IsScopedConnector            : False
    IsSmtpConnector              : True
    MaxMessageSize               : 35 MB (36,700,160 bytes)
    Name                         : NH-SendMail
    Port                         : 25
    ProtocolLoggingLevel         : Verbose
    RequireOorg                  : False
    RequireTLS                   : False
    SmartHostAuthMechanism       : None
    SmartHosts                   : {}
    SmartHostsString             :
    SmtpMaxMessagesPerConnection : 20
    SourceIPAddress              : 0.0.0.0
    SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
    SourceTransportServers       : {OurServer}
    TlsAuthLevel                 :
    TlsCertificateName           :
    TlsDomain                    :
    UseExternalDNSServersEnabled : False
    Tuesday, January 19, 2016 10:00 AM
  • Hi,

    I was correct there was a rule denying the new server, once I added an explicit rule for the server it worked!

    :) Thanks again for all your help.

    Tuesday, January 19, 2016 10:59 AM
  • Well mail is now flowing, but Outlook 2013 fails to connect. Well it sets the profile up fine but when I fire up OL it "says "Cannot start MS Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The information store could not be opened"

    Does anyone have any ideas please?

    Tuesday, January 19, 2016 12:16 PM
  • try Outlook.exe /resetnavpane
    Tuesday, January 19, 2016 12:19 PM
  • Thanks but no it didn't make a difference.
    Tuesday, January 19, 2016 1:23 PM
  • Hi,

    I understand you have a outlook connectivity issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently. Concerning your other question, I suggest you create a new thread.

    Thank you for your understanding.

    Regards,

    David 

    Wednesday, January 20, 2016 1:08 AM
    Moderator