Solved

Mdaemon mail server issue

Posted on 2009-04-08
1
2,214 Views
Last Modified: 2012-05-06
there are 50 mail servers with me they lie in the same data centre but in that 1 mdaemon mail server is creating a problem for me.

the mdaemon mail server is not able to send mails to other 49 mail servers (the mails do come but after lot of delay) but we are able to send mails from other mail servers to this mdaemon mail server.

there is only 1 domain on this mdaemon mail server but when they send mails to any other domains outside our data centre network the mails work perfectly fine.

Also it gives Winsock error 10060 in the logs sometimes.

Wed 2009-04-08 10:32:29: Session 4160; child 23
Wed 2009-04-08 10:31:29: Parsing message <d:\mdaemon\queues\remote\pd35000464616.msg>
Wed 2009-04-08 10:31:29: *  From: user1@domain.com
Wed 2009-04-08 10:31:29: *  To: user1@domain1.com
Wed 2009-04-08 10:31:29: *  Subject: ***
Wed 2009-04-08 10:31:29: *  Message-ID: <004c01c9b808$27dec5d0$779c5170$@com>
Wed 2009-04-08 10:31:29: Attempting SMTP connection to [mazeweb.com]
Wed 2009-04-08 10:31:29: Resolving MX records for [mazeweb.com] (DNS Server: 203.124.230.12)...
Wed 2009-04-08 10:31:29: *  P=005 S=000 D=mazeweb.com TTL=(40) MX=[razor2.spamrazor.net] {202.87.50.172}
Wed 2009-04-08 10:31:29: Attempting SMTP connection to [202.87.50.172:25]
Wed 2009-04-08 10:31:29: Waiting for socket connection...
Wed 2009-04-08 10:31:29: *  Connection established (203.201.252.36:3209 -> 202.87.50.172:25)
Wed 2009-04-08 10:31:29: Waiting for protocol to start...
Wed 2009-04-08 10:32:29: *  Error: 60 second wait for protocol timeout exceeded
Wed 2009-04-08 10:32:29: This message is 1 minutes old; it has 0 minutes left in this queue
Wed 2009-04-08 10:32:29: Remote queue lifetime exceeded; message placed in retry queue
Wed 2009-04-08 10:32:29: SMTP session terminated (Bytes in/out: 0/0)

+++++



Wed 2009-04-08 10:48:13: Session 6222; child 25

Wed 2009-04-08 10:47:52: Parsing message <d:\mdaemon\queues\remote\retry\pd90000013892.msg>

Wed 2009-04-08 10:47:52: *  From: user1@domain.com

Wed 2009-04-08 10:47:52: *  To: user1@domain1.com
Wed 2009-04-08 10:47:52: *  Subject: ***
Wed 2009-04-08 10:47:52: *  Message-ID: <004c01c9b808$27dec5d0$779c5170$@com>
Wed 2009-04-08 10:47:52: Attempting SMTP connection to [mazeweb.com]
Wed 2009-04-08 10:47:52: Resolving MX records for [mazeweb.com] (DNS Server: 203.124.230.12)...
Wed 2009-04-08 10:47:52: *  P=005 S=000 D=mazeweb.com TTL=(23) MX=[razor2.spamrazor.net] {202.87.50.172}
Wed 2009-04-08 10:47:52: Attempting SMTP connection to [202.87.50.172:25]
Wed 2009-04-08 10:47:52: Waiting for socket connection...
Wed 2009-04-08 10:48:13: *  Winsock Error 10060 The connection timed out.
Wed 2009-04-08 10:48:13: This message is 0 days old; it has 1 days left to get delivered
Wed 2009-04-08 10:48:13: SMTP session terminated (Bytes in/out: 0/0)
0
Comment
Question by:vedant0500
1 Comment
 
LVL 31

Accepted Solution

by:
moorhouselondon earned 500 total points
ID: 24100575
By the look of it you are sending out using IP 203.201.252.36

If the recipient does a Reverse DNS check on that address before any commitment is made to accept your message there seems to be a big delay in that response.  See the following trace which was carried out using DNSStuff

Preparation:
The  reverse DNS entry for an IP is found by reversing the IP, adding it to "in-addr.arpa", and looking up the PTR record.
So, the reverse DNS entry for 203.201.252.36 is found by looking up the PTR record for
 36.252.201.203.in-addr.arpa.
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.

How I am searching:
Asking g.root-servers.net for 36.252.201.203.in-addr.arpa PTR record:  
       g.root-servers.net says to go to ns3.apnic.net. (zone: 203.in-addr.arpa.)
Asking ns3.apnic.net. for 36.252.201.203.in-addr.arpa PTR record:  
       ns3.apnic.net [202.12.28.131] says to go to hyddns.tatanova.com. (zone: 252.201.203.in-addr.arpa.)
Asking hyddns.tatanova.com. for 36.252.201.203.in-addr.arpa PTR record:  Timed out [at 203.124.250.70].  Trying again.
Asking mumdns.tatanova.com. for 36.252.201.203.in-addr.arpa PTR record:  Reports mail.tataamc.com. [from 203.124.230.21]

Answer:
203.201.252.36 PTR record: mail.tataamc.com. [TTL 99999s] [A=203.201.252.36]
0

Featured Post

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Zimbra is famous for its platform independency, ability to manage multiple user accounts, easy assimilation with 3rd party applications, social network certification etc. Here, we discuss about how users can move multiple Zimbra user accounts to Exc…
The advancement in technology has been a great source of betterment and empowerment for the human race, Nevertheless, this is not to say that technology doesn’t have any problems. We are bombarded with constant distractions, whether as an overload o…
This tutorial gives a high-level tour of the interface of Marketo (a marketing automation tool to help businesses track and engage prospective customers and drive them to purchase). You will see the main areas including Marketing Activities, Design …
In this Experts Exchange video Micro Tutorial, I'm going to show how small business owners who use Google Apps can save money by setting up what is called a catch-all email address in their Gmail accounts. By using the catch-all feature, small busin…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question