On 3/30/2013 4:08 PM, Reindl Harald wrote: > > Am 30.03.2013 19:28, schrieb Dennis Putnam: >> On 3/30/2013 2:07 PM, Gerald Vogt wrote: >>> Sorry, but maybe you should not try to configure a mail server/relay for >>> the internet if you have trouble understanding this simple error >>> message. It seems a very bad idea to run an internet server if you have >>> so many difficulties with the absolute basics (like providing the >>> information requested multiple times by now...) There are already too >>> many open relays in the internet... >>> As the error message says, it times out while receiving the initial >>> server greeting. There is no dialog. It doesn't even start. There is not >>> even the initial greeting. So figure what could be the problem for >>> that... Should be pretty straight forward to understand... > +1 > >> I know very well what the error message means. It is the underlying >> events that I don't understand. How am I supposed to know if this is a >> timeout trying to open a port as opposed to making a successful socket >> connection and then not receiving a response to the HELO command? > by "telnet in.mailjet.com 25" as everybody looks if a tcp connection > itself is succesful > >> E7B1E1FA81: conversation with in.mailjet.com[46.105.158.233] timed out >> while receiving the initial server greeting > but since we here NOT se a different port as 25 and you refuse MULTIPLE > tims to post your damned config i guess again that you do not try to > configrue youre server to submit euthenticated messages to port 587 > and coming from a IP which is not allowed to submit via port 25 for > whatever reason on the destination - but what do i know because you > refuse to help others helping you all the time > > so come back with output of "postconf -n" and the both config > files for "smtp_sender_dependent_authentication" replaced only > the username and passwort or read manuals and solve your > troubles at your own > Sorry but I wanted to try to figure this out on my own first. That is the way I learn. That is also why all my questions were asking how to debug this rather than ask for a solution. I did not mean to come across as uncooperative or ungrateful but my mind was just in a different solving mode than yours.
postconf -n alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases, hash:/var/lib/mailman/data/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 3 debug_peer_list = 127.0.0.1 html_directory = no inet_interfaces = all inet_protocols = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost mynetworks_style = host newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES relayhost = [smtp.att.yahoo.com] sample_directory = /etc/postfix sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relay sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_generic_maps = hash:/etc/postfix/generic smtp_helo_name = home.bellsouth.net smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = smtp_sender_dependent_authentication = yes smtp_tls_policy_maps = hash:/etc/postfix/tls_policy smtpd_banner = $myhostname ESMTP $mail_name ($mail_version) (CentOS Linux) syslog_name = postfix unknown_local_recipient_reject_code = 550 sasl_passwd [in.mailjet.com] 21a8f6casdasdasdadad850539efca7:ea330afe99asdasdasdasdasdfbbd3fd69 sender_relay myu...@mydomain.com [in.mailjet.com]:587 P.S. There is not a socket connection problem. telnet to port 587 works fine as does authentication and commands to send a test email.
signature.asc
Description: OpenPGP digital signature
