+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 25
Enterprise Software Thread, Exchange External mail not flowing in Technical; Hi, URGENT HELP NEEDED! we have a client we look after at work that is having mail routing problems. Internal ...
  1. #1

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Exchange External mail not flowing

    Hi, URGENT HELP NEEDED!
    we have a client we look after at work that is having mail routing problems. Internal mail in fine, it is simply anything that is leaving the organisation or coming into the organisation.
    I am pretty new to exchange and have been lumbered with this problem and am under pressure to get it fixed. below are the results of another engineers testing smtp port 25

    [I]Testing inbound SMTP mail flow for domain 'administrator@DOMAIN.com.au'.
    The Microsoft Connectivity Analyzer failed to test inbound SMTP mail flow.
    Test Steps
    Attempting to retrieve DNS MX records for domain 'DOMAIN.com.au'.
    One or more MX records were successfully retrieved from DNS.
    Additional Details


    Testing Mail Exchanger mail.DOMAIN.com.au.
    One or more SMTP tests failed for this Mail Exchanger.
    Test Steps
    Attempting to resolve the host name mail.DOMAIN.com.au in DNS.
    The host name resolved successfully.
    Additional Details

    Testing TCP port 25 on host mail.DOMAIN.com.au to ensure it's listening and open.
    The port was opened successfully.
    Additional Details


    Analyzing SMTP Capabilities for server mail.DOMAIN.com.au:25
    SMTP Capabilities were analyzed successfuly.
    Additional Details


    Attempting to send a test email message to administrator@DOMAIN.com.au using MX mail.DOMAIN.com.au.

    Delivery of the test email message failed.

    Additional Details

    The server returned status code -1 - The operation has timed out.
    Exception details:
    Message: The operation has timed out.
    Type: System.Net.Mail.SmtpException
    Stack trace:
    at System.Net.Mail.SmtpClient.Send(MailMessage message)
    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTe st.PerformTestReally


    There have been multiple tests run, some email gets into the exchange server, but can take several hours. I have had an email from an engineer that is now on annual leave to tell me what he has tried to do, some of which is:

    - Disable Antivirus services
    - Enable POP3 and IMAP4 services
    - Restarted MS Exchange AD topology and Information Store services
    - Reboot server
    - Disable Windows firewall private and Public profile
    - Created new recipient connector
    - Created new SNMP connector for port 587
    - Changed FQDN of all recipient connectors From remote.DOMAIN.com.au to mail.DOMAIN.com.au and vice versa
    - Changed remote server Ip addressed range to allow all connection for recipient connector

    All have been tried and tested yet no joy. he suspects maybe MX hosting service provider issue where email gets delayed or dropped. but not sure where to go with this.

    Any advise people?

    thanks in advance!!





  2. #2

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,047
    Thank Post
    160
    Thanked 913 Times in 716 Posts
    Blog Entries
    3
    Rep Power
    271
    Hey Mate,

    Drop me an IM if you want and I'll give you a hand this morning... I could do with the domain and I'll do some digging and then try and guide you as to what to check.

    SMTP Test:

    SMTP_Test.png

    Inbound Email seems to be coming in ok:

    SMTP_Test.png

    Outbound Email seems to be ok:

    SMTP_Test.png

    I must admit, when it's doing a reverse lookup on the IP address it is contacting a different domain to the one you have configured in your MX records and so that probably isn't helping things.

    Thanks,
    James.
    Last edited by EduTech; 8th September 2013 at 11:47 AM.

  3. Thanks to EduTech from:

    local-lad-steve (9th September 2013)

  4. #3

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    not sure if it helps, but if i do a tracert to the affected mail server it connects.

    if i do it from the mail server back to my domain it times out.

    Any further thoughts?

  5. #4

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,852
    Thank Post
    583
    Thanked 2,162 Times in 987 Posts
    Blog Entries
    23
    Rep Power
    627
    Moving to Enterprise Software forum.

  6. #5

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    update: its taking upto 3 days for external email to route into the domain. having looked at the exchange server today, I found that disk space was down to 4%. BUT, surely if exchange doesn't allow for disk space to go below a threshold then internal mail would also stop working??

    Also i found that there is a certificate issue. its looking for 'mail.domain.com.au' where as the certificate is 'remote.domain.com.au' could this be the issue?? if so, how do we go about fixing the certificate?? See attachment.....

    Exchange is running on an SBS server 2008 and exchange is running on sp1 - I believe.

    im in desperate need to get this resolved..any suggestions appreciated!!!!!!

    thanks!!
    Attached Images Attached Images

  7. #6

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    James, I also got a successful test today for inbound email. 5 mins later I got a failed one. there is no consistency. is fails more often than I connects.

  8. #7

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    10 mins ago a test email was received into the administrator mailbox.

    BUT, the following error has just occurred in the last few mins having run testing again:

    " Attempting to send a test email message to administrator@domain.com.au using MX mail.domain.com.au.
    Delivery of the test email message failed.

    Additional Details
    The server returned status code -1 - The operation has timed out.
    Exception details:
    Message: The operation has timed out.
    Type: System.Net.Mail.SmtpException
    Stack trace:
    at System.Net.Mail.SmtpClient.Send(MailMessage message)
    at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTe st.PerformTestReally() "

    Has anyone see this before?

  9. #8

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Further update:

    I sent 8 test emails from my external email address to the administrator mailbox one after the other and labelled the subject line 1 to 8 as per email. within 2 mins, emails number 3 and 6 came through. after 10 mins, emails number 4 and 7 came through, then 12 mins later emails 1 and 2 came through.

    bizarre behaviour.

    can anyone suggest what might be causing this???

  10. #9

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,047
    Thank Post
    160
    Thanked 913 Times in 716 Posts
    Blog Entries
    3
    Rep Power
    271
    What Priority are your MX Records, It is my understanding you only have 1 MX Record which points to an A Record which they points to an IP Address. Is that the IP address of your Exchange Server? which I presume is NATd on a Firewall within your infrastructure?

    James.

  11. #10

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    From my understanding, the MX records sits with the isp? no? there is only a single exchange server in this organisation. i guess i would need access to the the DNS of the isp to find out about the mx records, which i dont have.

    ...and emails "5" and "8" came through 2 hours later than the others.....

    im completely lost as to what is going off here...

  12. #11

    Join Date
    Jul 2006
    Location
    London
    Posts
    1,256
    Thank Post
    111
    Thanked 242 Times in 193 Posts
    Blog Entries
    1
    Rep Power
    74
    If your server is resource constrained, which in your case is quite possible since you only have 4% disk space left on an oldish server, then backpressure may be in effect.

  13. Thanks to psydii from:

    local-lad-steve (10th September 2013)

  14. #12

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks! This is something that i have looked into today. so i have managed to create another 60Gb of space on the drive and nothing changed, but, i am going to restart the server in 2 hours time to see if a kick will bring the box back into life.

  15. #13

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    having cleared space and give the server a reboot, exchange emails came in when I sent some test messages and I thought we were at the finish line... however it stopped working again.....

    james, details u requested earlier as follows:

    Domain name: obbc.com.au
    ip address: 203.89.201.60
    mail server host name: mail.obbc.com.au
    priority: 10

    host/alias Record type ip/hostname
    adsl.obbc.com.au CNAME mail.obbc.com.au
    mail.obbc.com.au A 14.201.14.48
    oldmail.obbc.com.au A xxx.xxx.xxx.xxx
    oldremote.obbc.com.au A xxx.xxx.xxx.xxx
    remote.obbc.com.au A 14.240.126.117
    Financial planning, Business Leasing & Asset Purchase, Auditing, Business Loans, O A 203.89.201.60

    if I do a remote connectivity test analyser, sometimes it connects and sometimes it fails.

    any more thoughts folks?

  16. #14

    EduTech's Avatar
    Join Date
    Aug 2007
    Location
    Reading
    Posts
    5,047
    Thank Post
    160
    Thanked 913 Times in 716 Posts
    Blog Entries
    3
    Rep Power
    271
    The only thing that I wonder, is that your Reverse DNS Lookup points to 14-201-14-48.static.tpgi.com.au as oppose to mail.obbc.com.au

    I have a feeling that it is DNS Related to be honest, and that is what is causing the delay on your email delivery. I have also noticed that sometimes it mail.obbc.com.au will also resolve to remote.obbc.com.au which is a different IP completely.

    In that list their, I do not see an MX Record?

    James.

  17. #15

    Join Date
    Mar 2010
    Location
    UK
    Posts
    43
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    having spent two days trying to clear up the exchange box, I was thinking the same and that I was looking in the wrong place. from the email I received today, the above list fell under the mx records for the domain. that's all I was provided with. With regards the remote/mail.obbc.com.au...there are event viewer errors for this, but its just for sending mail I think and outbound mail is fine. I reckon it is a DNS issue....so do you think we need to be contacting the service provider?

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Exchange 2010 not sending external mail
    By sfoord in forum Windows Server 2008
    Replies: 9
    Last Post: 21st August 2013, 02:53 PM
  2. Replies: 3
    Last Post: 19th November 2008, 09:45 PM
  3. External E-mail not being sent
    By faza in forum How do you do....it?
    Replies: 9
    Last Post: 10th August 2008, 02:08 PM
  4. Replies: 6
    Last Post: 3rd May 2007, 02:29 PM
  5. Replies: 4
    Last Post: 5th March 2007, 09:09 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •