?
Solved

timed out while recieving the initial server greeting

Posted on 2009-05-03
9
Medium Priority
?
3,312 Views
Last Modified: 2013-11-30
Have a Webmin, Postfix, Mutt server that I want to be the smtp relay to send out my emails.
Have successfully configured the postfix/mutt mail relay, can send out.  Having problems getting my other server to connect to my mail relay and send out said email I keep getting the aforementioned error what am I missing?
timed out while receiving the initial server greeting)

Open in new window

0
Comment
Question by:Illyankesh
  • 5
  • 4
9 Comments
 
LVL 19

Expert Comment

by:bevhost
ID: 24292901
Is there anything reported in the log of the other (connecting) server?
0
 

Author Comment

by:Illyankesh
ID: 24293054
Ok the top bit is from the receiving server, that is supposed to be doing the relaying, and the bottom bit is from the server that is sending.

I'm sure I've got enough holes to drive a truck through, but I have kind of lost my way...looking at the relay server logs looks messy...where should I start?
This is the last couple of lines from /var/log/mail.log on the relay server.
 
 
May  4 07:14:08 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: process /usr/lib/postfix/smtpd pid 14126 exit status 1
May  4 07:14:08 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
May  4 07:15:08 domU-12-31-38-00-9D-F7 postfix/smtpd[14128]: warning: database /etc/aliases.db is older than source file /etc/aliases
May  4 07:15:08 domU-12-31-38-00-9D-F7 postfix/smtpd[14128]: warning: database /etc/postfix/canonical.db is older than source file /etc/postfix/canonical
May  4 07:15:08 domU-12-31-38-00-9D-F7 postfix/smtpd[14128]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_do$
May  4 07:15:09 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: process /usr/lib/postfix/smtpd pid 14128 exit status 1
May  4 07:15:09 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
May  4 07:16:09 domU-12-31-38-00-9D-F7 postfix/smtpd[14143]: warning: database /etc/aliases.db is older than source file /etc/aliases
May  4 07:16:09 domU-12-31-38-00-9D-F7 postfix/smtpd[14143]: warning: database /etc/postfix/canonical.db is older than source file /etc/postfix/canonical
May  4 07:16:09 domU-12-31-38-00-9D-F7 postfix/smtpd[14143]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_do$
May  4 07:16:10 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: process /usr/lib/postfix/smtpd pid 14143 exit status 1
May  4 07:16:10 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
 
 
This is the last couple of lines from the server I was sending the email from.
 
May  4 07:28:21 domU-12-31-38-01-D5-C2 postfix/postfix-script[2012]: refreshing the Postfix mail system
May  4 07:28:21 domU-12-31-38-01-D5-C2 postfix/master[20991]: reload configuration /etc/postfix
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: A9F26420EB: skipped, still being delivered
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: A9F26420EB: skipped, still being delivered
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: B3A4D420E6: from=<root@geomatejr.com>, size=438, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: 51D9A420DC: from=<root@geomatejr.com>, size=438, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: 0D9BA420E5: from=<root@geomatejr.com>, size=438, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: 64AA2420DA: from=<root@geomatejr.com>, size=438, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: 6FC14420D6: from=<root@geomatejr.com>, size=443, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: 7EBFD420D2: from=<root@geomatejr.com>, size=443, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: D6F10420CC: from=<root@geomatejr.com>, size=438, nrcpt=1 (queue active)
May  4 07:28:49 domU-12-31-38-01-D5-C2 postfix/qmgr[2149]: B0C44420E0: from=<root@geomatejr.com>, size=443, nrcpt=1 (queue active)

Open in new window

0
 

Author Comment

by:Illyankesh
ID: 24293077
I see one error, I changed the canonical file without updating the canonical db...am I even using canonical?
0
Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

 

Author Comment

by:Illyankesh
ID: 24293159
Ok, cleaned up the differences, and my postfix I'm now down to the

"smtpd_recipientrestrictions":  specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit

0
 

Author Comment

by:Illyankesh
ID: 24293614
The server that is sending the email I get queue active no more errors, and it is set to relay to the relay, however I am still getting the below...
May  4 09:54:47 domU-12-31-38-00-9D-F7 postfix/smtpd[15960]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working$
May  4 09:54:48 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: process /usr/lib/postfix/smtpd pid 15960 exit status 1
May  4 09:54:48 domU-12-31-38-00-9D-F7 postfix/master[1205]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

Open in new window

0
 
LVL 19

Expert Comment

by:bevhost
ID: 24293765
You need to fix this one.
warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

It means that postfix has a fatal configuration error that prohibits it from running.

try commenting out things in your main.cf that you're not sure of.

0
 
LVL 19

Expert Comment

by:bevhost
ID: 24293771
postconf -n
will display config lines not set to the default value.
0
 

Author Comment

by:Illyankesh
ID: 24297603
Ok, line by line I found the culprit and commented him out.   Ok, now I get the following error, and it is the ip of the server I'm having forward it's mail to be relayed...  I assume I need to add it by hand to some authorized user argument?
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_mynetworks permit_inet_interfaces permit_$
#smtpd_client_restrictions = hash:/etc/postfix/access, reject_maps_rbl
smtpd_client_restrictions = permit_mynetworks, reject_unknown_client,permit_sas$
sender_canonical_maps = hash:/etc/postfix/canonical
recipient_canonical_maps = hash:/etc/postfix/canonical
 
 
May  4 18:00:53 domU-12-31-38-00-9D-F7 postfix/smtpd[17787]: lost connection after CONNECT from unknown[174.***.***.***]
May  4 18:00:53 domU-12-31-38-00-9D-F7 postfix/smtpd[17787]: disconnect from unknown[174.***.***.***]

Open in new window

0
 
LVL 19

Accepted Solution

by:
bevhost earned 1500 total points
ID: 24301801
Try this
smtpd_client_restrictions =
        #  hash:/etc/postfix/access,
          reject_maps_rbl

To check that it is the access file.  If so you better check the file is right.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

The new Gmail Phishing Scam going around is surprising even the savviest of users with its sophisticated techniques.
Last month Marc Laliberte, WatchGuard’s Senior Threat Analyst, contributed reviewed the three major email authentication anti-phishing technology standards: SPF, DKIM, and DMARC. Learn more in part 2 of the series originally posted in Cyber Defense …
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month16 days, 5 hours left to enroll

850 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