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
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.
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.
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
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 =
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
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
