cannot received email from pop3

Dear all,

Our redhat 9 server runs smoothly¡M However, recently, the outlook express
cannot connect to such server to receive email, Anyway, when I test the pop
server by using telnet "192.168.0.11 110"
the server can give

[root@ns etc]# telnet 192.168.0.10 110
Trying 192.168.0.10...
Connected to ns.xx-xx.com (192.168.0.10).
Escape character is '^]'.
Connection closed by foreign host.

It seems not to refuse the request but close the connection immediately.

Why? Please give me helping hand, thanks.

Regards,
Simon

Dear all,

Our redhat 9 server runs smoothly¡M However, recently, the outlook express
cannot connect to such server to receive email, Anyway, when I test the pop
server by using telnet "192.168.0.11 110" the server can give

[root@ns etc]# telnet 192.168.0.10 110
Trying 192.168.0.10...
Connected to ns.xx-xx.com (192.168.0.10).
Escape character is '^]'.
Connection closed by foreign host.

It seems not to refuse the request but close the connection immediately.

[root@ns etc]# netstat -lt|grep pop
tcp 0 0 *op3s *:* LISTEN
tcp 0 0 *op2 *:* LISTEN
tcp 0 0 *op3 *:* LISTEN

Why? Please give me helping hand, thanks.

Regards,
Simon

>
>

On Sep 11, 12:09 pm, "John" <John...@yahoo.com> wrote:
> Dear all,
>
> Our redhat 9 server runs smoothly¡M However, recently, the outlook express
> cannot connect to such server to receive email, Anyway, when I test the pop
> server by using telnet "192.168.0.11 110"
> the server can give
>
> [root@ns etc]# telnet 192.168.0.10 110
> Trying 192.168.0.10...
> Connected to ns.xx-xx.com (192.168.0.10).
> Escape character is '^]'.
> Connection closed by foreign host.
>
> It seems not to refuse the request but close the connection immediately.
>
> Why? Please give me helping hand, thanks.
>
> Regards,
> Simon

Their could be lot of reasons, what mail server are you using?

On 2007-09-11, John <(E-Mail Removed)> wrote:
> [root@ns etc]# netstat -lt|grep pop
> tcp 0 0 *op3s *:* LISTEN
> tcp 0 0 *op2 *:* LISTEN
> tcp 0 0 *op3 *:* LISTEN
>
> Why?

why what?

most of the time the pop server runs from Xinetd (or inetd) so the
server always listen on that port and then 'spawn' the real server
when requested, you should check if that can be spawned and eventually
what problems does it have.

>Please give me helping hand

You have to help yourself, is your server not ours. we can point you in
some direction but you have to do the job.

Davide

--
I'm an apatheist. The question is no longer interesting, and the
answer no longer matters.
-- from alt.sysadmin.recovery

John schrieb:
> Dear all,
>
> Our redhat 9 server runs smoothly¡M However, recently, the outlook express
> cannot connect to such server to receive email, Anyway, when I test the pop
> server by using telnet "192.168.0.11 110" the server can give
>
> [root@ns etc]# telnet 192.168.0.10 110
> Trying 192.168.0.10...
> Connected to ns.xx-xx.com (192.168.0.10).
> Escape character is '^]'.
> Connection closed by foreign host.
>
> It seems not to refuse the request but close the connection immediately.
>
> [root@ns etc]# netstat -lt|grep pop
> tcp 0 0 *op3s *:* LISTEN
> tcp 0 0 *op2 *:* LISTEN
> tcp 0 0 *op3 *:* LISTEN
>
> Why? Please give me helping hand, thanks.

Difficult if you give so precious little information about your setup.
But in general terms:
- Check the network connection between the client and server.
- In particular check if there are any firewalls/filters active between
or on either of them.
- Check the log of your POP3 server software (whatever it is) for any
traces of your connection attempts and reasons for rejection.
- Run netstat with the -p option to see if the process listening on the
POP3 port is the one you think it is.
- As the problem started recently, find out what (was) changed between
the last time it worked correctly and the first time it didn't work
anymore.
HTH
T.

--
Please excuse my bad English/German/French/Greek/Cantonese/Klingon/...

In comp.mail.imap John <(E-Mail Removed)> wrote:
> [root@ns etc]# telnet 192.168.0.10 110
> Trying 192.168.0.10...
> Connected to ns.xx-xx.com (192.168.0.10).
> Escape character is '^]'.
> Connection closed by foreign host.

> It seems not to refuse the request but close the connection immediately.

A common reason for such behaviour is TCP wrappers. Whappers. Have you
changed your hosts.allow or hosts.deny?

/NIels

--
Niels Baggesen -- @home -- Århus -- Denmark -- (E-Mail Removed)
The purpose of computing is insight, not numbers -- R W Hamming

On Tue, 11 Sep 2007 15:31:27 +0800, John wrote:

> Our redhat 9 server runs smoothly¡M

RHL-9 was EOL'd years ago and no updates are now available. Install an
OS which is currently supported. If you do not wish to pay Red Hat their
license fee for RHEL then consider using CentOS which is almost identical
to the Red Hat product.

> [root@ns etc]# telnet 192.168.0.10 110 Trying 192.168.0.10...
> Connected to ns.xx-xx.com (192.168.0.10). Escape character is '^]'.
> Connection closed by foreign host.

The default installation of RHL provides a firewall (iptables) which
blocks incoming port 110. Edit your iptables rules file to permit access
to port 110 and execute /etc/init.d/iptables restart.

In article <(E-Mail Removed)>,
Dave Uhring <(E-Mail Removed)> wrote:

> On Tue, 11 Sep 2007 15:31:27 +0800, John wrote:
[...]
> > [root@ns etc]# telnet 192.168.0.10 110 Trying 192.168.0.10...
> > Connected to ns.xx-xx.com (192.168.0.10). Escape character is '^]'.
> > Connection closed by foreign host.
>
> The default installation of RHL provides a firewall (iptables) which
> blocks incoming port 110. Edit your iptables rules file to permit access
> to port 110 and execute /etc/init.d/iptables restart.

That underlying cause would not be consistent with a connection opening
but immediately closing. That sort of behavior is idiosyncratic of a
service that is running out of inetd/xinetd accessed from an address
which is prohibited by TCP wrapper config.

--
Now where did I hide that website...

On Wed, 12 Sep 2007 22:30:55 -0400, Bill Cole wrote:

> In article <(E-Mail Removed)>,
> Dave Uhring <(E-Mail Removed)> wrote:
>
>> On Tue, 11 Sep 2007 15:31:27 +0800, John wrote:
> [...]
>> > [root@ns etc]# telnet 192.168.0.10 110 Trying 192.168.0.10...
>> > Connected to ns.xx-xx.com (192.168.0.10). Escape character is '^]'.
>> > Connection closed by foreign host.
>>
>> The default installation of RHL provides a firewall (iptables) which
>> blocks incoming port 110. Edit your iptables rules file to permit
>> access to port 110 and execute /etc/init.d/iptables restart.
>
> That underlying cause would not be consistent with a connection opening
> but immediately closing. That sort of behavior is idiosyncratic of a
> service that is running out of inetd/xinetd accessed from an address
> which is prohibited by TCP wrapper config.

Yeah, I realized that after a more careful look at his telnet session.

Hello,

Bill Cole a écrit :
>
>>> [root@ns etc]# telnet 192.168.0.10 110 Trying 192.168.0.10...
>>> Connected to ns.xx-xx.com (192.168.0.10). Escape character is '^]'.
>>> Connection closed by foreign host.
>
> That sort of behavior is idiosyncratic of a
> service that is running out of inetd/xinetd accessed from an address
> which is prohibited by TCP wrapper config.

Or a service which segfaults because of a disk cache corruption in RAM.
I've had that a couple of time on a machine with faulty RAM which caused
one error average per year. Took time to diagnose.