ipop3

[Rick Stevens]

On Thu, 2006-09-28 at 07:45 -0400, Dan Doucette wrote:
> > On Tue, 2006-09-26 at 13:54 -0400, Dan Doucette wrote:
> > >
> > > > -----Original Message-----
> > > > From: redhat-install-list-bounces at redhat.com [mailto:redhat-install-
> > list-
> > > > bounces at redhat.com] On Behalf Of Rick Stevens
> > > > Sent: Tuesday, September 26, 2006 1:01 PM
> > > > To: Getting started with Red Hat Linux
> > > > Subject: Re: ipop3
> > > >
> > > > On Tue, 2006-09-26 at 10:28 -0400, Dan Doucette wrote:
> > > > > Hello,
> > > > >
> > > > > We just completed a network upgrade and appears that most of the
> > clients
> > > > at
> > > > > these sites can not check e-mail after the upgrade has been done.
> > Some
> > > > can
> > > > > some can't, it's a mixture of OE and regular Outlook. After the
> > server
> > > > is
> > > > > rebooted that seems to correct the problem. The error message I'm
> > seeing
> > > > is;
> > > > >
> > > > > : Command stream end of file while reading line user=dstevens
> > > > > host=[192.168.7.102]
> > > > >
> > > > > The server is running RedHat 9 with the default pop server ipop3d
> > > > >
> > > > > Has anyone run into this issue?
> > > >
> > > > Did you check your firewall settings?  You'll have to make sure that
> > > > TCP port 110 is open.  For IMAP, use TCP port 143.
> > >
> > > Yes, it is open. I can telnet from the problem machines to port 110
> > without
> > > an issue. I also tried a different client, thunderbird.
> > 
> > Did thunderbird work correctly?  If so, then you should verify that the
> > Outlook clients are indeed running POP3 and that they're not using any
> > special authentication mechanisms.  You may also need to change the
> > timeout in Outlook.
> 
> Thunderbird did not work correctly. The only thing that seems to fix the
> issue is a server reboot. I'm wondering if it has anything to do with the
> change in IP address scheme? Most of these clients used to connect through
> the internet versus over our WAN.

A server reboot?  Hmmm.  Well, yes, if you changed IP addresses, it's
possible that the clients either cached the old IP address (and if
they're Windows machines, they will summarily ignore the TTL on DNS
records) or the routers, switches or client ARP tables had invalid data
for the server.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens at vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-           grep me no patterns and I'll tell you no lines           -
----------------------------------------------------------------------