Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
Zitat von Christopher Adams adam...@gmail.com: Hello all, I had Postfix 2.3 installed on CentOS 5.5. I had Postfix running, but wasn't able to send mail through it. I recompiled and upgraded to 2.8.2. I have verified that Postfix is running, port 25 is open, and I have net connectivity. However, I can't send mail. root 4551 0.0 0.2 54172 2272 ?Ss 22:59 0:00 /usr/libexec/postfix/master postfix 5699 0.0 0.2 54248 2224 ?S23:39 0:00 pickup -l -t fifo -u postfix 5804 0.0 0.2 55208 2272 ?S23:43 0:00 qmgr -l -t fifo -u The maillog shows just this, from the startup: May 3 23:38:58 localhost postfix/postfix-script[5667]: refreshing the Postfix mail system May 3 23:38:58 localhost postfix/master[4551]: reload -- version 2.8.2, configuration /etc/postfix I have checked some of the troubleshooting tips mentioned in the docs and see that the accepted protocol is to generate data from postconf -d. I will do that if needed, but I just wanted to check to see what steps I should take next. How do you try to send mail? Local submission eg. invoking sendmail With a mailclient across the network My bet would be inet_interfaces=localhost ... Regards Andreas smime.p7s Description: S/MIME Cryptographic Signature
Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
On 5/4/2011 1:50 AM, Christopher Adams wrote: I have checked some of the troubleshooting tips mentioned in the docs and see that the accepted protocol is to generate data from postconf -d. This is wrong. We don't care about postconf -d, but we are very interested in postconf -n output. Where did you find this incorrect information? The source needs to be corrected. http://www.postfix.org/postconf.1.html postconf -d = compiled-in defaults. We know what these are. postconf -n = your settings. I will do that if needed, but I just wanted to check to see what steps I should take next. Please see: http://www.postfix.org/DEBUG_README.html#mail -- Noel Jones
Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
Okay, I remembered wrong about postconf. Here is posconf -n: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 5 debug_peer_list = hpl.osl.state.or.us default_privs = nobody html_directory = no mail_owner = postfix mail_spool_directory = /var/spool/mail mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man message_size_limit = 400 mydestination = $myhostname, localhost.$mydomain, localhost, hpl.$mydomain mydomain = osl.state.or.us myhostname = hpl.osl.state.or.us mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop unknown_local_recipient_reject_code = 550 On Wed, May 4, 2011 at 5:57 AM, Noel Jones njo...@megan.vbhcs.org wrote: On 5/4/2011 1:50 AM, Christopher Adams wrote: I have checked some of the troubleshooting tips mentioned in the docs and see that the accepted protocol is to generate data from postconf -d. This is wrong. We don't care about postconf -d, but we are very interested in postconf -n output. Where did you find this incorrect information? The source needs to be corrected. http://www.postfix.org/postconf.1.html postconf -d = compiled-in defaults. We know what these are. postconf -n = your settings. I will do that if needed, but I just wanted to check to see what steps I should take next. Please see: http://www.postfix.org/DEBUG_README.html#mail -- Noel Jones -- Christopher Adams adam...@gmail.com
Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
On 5/4/2011 10:20 AM, Christopher Adams wrote: Okay, I remembered wrong about postconf. Here is posconf -n: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 5 debug_peer_list = hpl.osl.state.or.us default_privs = nobody html_directory = no mail_owner = postfix mail_spool_directory = /var/spool/mail mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man message_size_limit = 400 mydestination = $myhostname, localhost.$mydomain, localhost, hpl.$mydomain mydomain = osl.state.or.us myhostname = hpl.osl.state.or.us mynetworks_style = subnet newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop unknown_local_recipient_reject_code = 550 Please don't top post. Show postfix logging of the problem, and mailq output. Please also show non-comment lines of master.cf. The output of this should do that. grep -v '^#' master.cf
Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
On 5/4/2011 11:10 AM, Christopher Adams wrote: Running mailq says that the queue is empty. Here is the output from master.cf smtp inet n - n - - smtpd -v Don't top post. Put your answers in-line, or at the end. Remove the -v from the above. Verbose logging is seldom necessary, and can hide problems in a flood of unrelated information. Ok, so what's the problem? Show evidence. -- Noel Jones
Re: getting Postfix 2.8.2 on CentOS 5.5 to send and receive
Thanks for your reply. I figured out that there is a perimeter firewall, in addition to the iptables local firewall, so I have created a bypass rule for mail incoming and outgoing. Now, I have mail coming in. Actually, I am trying to set this up as a temporary relay for testing problems with an Exchange server. I will start a new thread dealing with that. Thanks again. On Wed, May 4, 2011 at 10:16 AM, Noel Jones njo...@megan.vbhcs.org wrote: On 5/4/2011 11:10 AM, Christopher Adams wrote: Running mailq says that the queue is empty. Here is the output from master.cf smtp inet n - n - - smtpd -v Don't top post. Put your answers in-line, or at the end. Remove the -v from the above. Verbose logging is seldom necessary, and can hide problems in a flood of unrelated information. Ok, so what's the problem? Show evidence. -- Noel Jones -- Christopher Adams adam...@gmail.com
