TCP Port 25 (smtp)?
Pete Goodeve
I'm trying to set up a new server to replace an older one that needs
to be retired (through no need or desire of mine... (:-/) It's working
fine!) The older machine is RH 7.3 (I think) running Postfix for its
mail server, and it works without trouble. On the replacement I have
installed RH 9 Server version, with (initially) Medium Firewall --
www and smtp both enabled. Both machines are dual-(network)ported,
one port on the internet and the other a local network. At the moment I am
trying to get the new machine working without connecting the global net
at all (so I don't have to mess with switching global IP addresses yet).
I told the RedHat installation tool to use Postfix rather than sendmail,
but it seemed to fail to do so. I tried to send mail (over the local net)
anyway, but got no joy. Didn't worry much because in fact our version of
Postfix was newer and I wanted to install that to match the current machine.
I deinstalled the sendmail RPM and built our Postfix (2.0.16). (The older
Postfix RPM wouldn't deinstall because of a couple of dependencies that
shouldn't affect operation, so I just overwrote it.)
Unfortunately, I'm getting (apparently) exactly the same glitch with
Postfix as I did with sendmail -- nothing comes in! Internal mail
works as it should, and trying to send *out* looks like it's basically
working (but the receiver gets confused because of other routing problems).
Incoming mail simply doesn't even reach smtpd. Nothing appears in the
maillog(s) and the sender's log reports "Connection refused (Port 25)".
If I run tcpdump on that interface, all I see (aside from some ARP
requests and responses that look OK) is the initial SYN request from the
sender to port 25 and an RST back!
I've looked everywhere for something that might be blocking that port.
Other ports seem to be open -- I can ssh happily into the machine, and
apache seems to be serving stuff out -- though I'm now having slowness
problems with that that weren't apparent last week. I tried turning off
the Firewall completely (with "redhat-config-securitylevel") but it made
no difference.
Doing an 'iptables -L' shows a proper looking ACCEPT line for 'dpt:smtp',
so what the hell is lacking??
Hellppp!!!
-- Pete --
ynotssor
news:ea658v$8hq$1...@jwgibbs.CChem.Berkeley.EDU
> Unfortunately, I'm getting (apparently) exactly the same glitch with
> Postfix as I did with sendmail -- nothing comes in! Internal mail
> works as it should, and trying to send *out* looks like it's basically
> working (but the receiver gets confused because of other routing
> problems).
>
> Incoming mail simply doesn't even reach smtpd. Nothing appears in the
> maillog(s) and the sender's log reports "Connection refused (Port
> 25)".
As root:
netstat -nap | grep :25
or
lsof -i :25
to see what (if anything) is listening on port 25.
Greg Hackney
Not sure about RH9, but some distributions of Postfix only enable the
loopback interface. Run the command "postconf inet_interfaces" and make
sure it says "all". If not, configure in main.cf. Reference: "man 5 postconf"
From the same machine that Postfix is on, try connecting up manually
with "telnet 127.0.0.1 25" and also "telnet your_nic_IP_address 25" to make
sure it's responding. Use "quit" to exit.
Run the command "postfix check" to look for errors.
Take a look at /var/log/maillog or /var/log/messages
--
Greg
Pete Goodeve
Greg Hackney <hac...@swbell.net> wrote:
>
>
>Not sure about RH9, but some distributions of Postfix only enable the
>loopback interface. Run the command "postconf inet_interfaces" and make
>sure it says "all". If not, configure in main.cf. Reference: "man 5 postconf"
Well, thanks oh so much...! Yep, that was it, but now the question
becomes how the heck did that setting get in there?! I took the tar source
over from the running machine and recompiled it, so I expected things to
be much the same. The new main.cf had the line "inet_interfaces=localhost"
right there, but on its ancestor there isn't a trace of any such entry
(even in the source configurations...)!
There are certainly other differences that caught me by surprise -- the
new one is chroot for example -- so there may have been ./configure
settings I made on the original and forgot.
Now I have the same routing problem to solve on the new machine (or not,
because it's an artefact of the local-net temporary setup) but at least
I can see some maillog messages now!
Thanks again.
-- Pete --
Greg Hackney
> Well, thanks oh so much...! Yep, that was it, but now the question
> becomes how the heck did that setting get in there?! I took the tar source
> over from the running machine and recompiled it, so I expected things to
> be much the same.
When you did a "make install", it probably overwrote your /etc/postfix config
files using the stock source code package versions.
If you are just replacing the old system, for the most part, you should be
able to copy everything in /etc/postfix from the old system to the new one,
and make any minor changes as needed.
If you want to manually compare every configuration difference between the 2 systems,
compare the output of "postconf -n" on both systems, and also compare the contents
of master.cf.
--
Greg
Pete Goodeve
Greg Hackney <hac...@swbell.net> wrote:
>Pete Goodeve wrote:
>
>> Well, thanks oh so much...! Yep, that was it, but now the question
>> becomes how the heck did that setting get in there?! I took the tar source
>> over from the running machine and recompiled it, so I expected things to
>> be much the same.
>
>When you did a "make install", it probably overwrote your /etc/postfix config
>files using the stock source code package versions.
assumed that the install would just overwrite the older version, but what it
seems to have done is to take all the settings from that and use those to
configure the installation! (A large number of the files in /etc/postfix
predate my install.)
>
>If you are just replacing the old system, for the most part, you should be
>able to copy everything in /etc/postfix from the old system to the new one,
>and make any minor changes as needed.
that I took the new main.cf and adjusted that.
I think what I'd better do is push the old/current installation completely
aside and try to rebuild it as I expected things to be!
-- Pete --