First, what I do when I want to see what ports are being listened to is issue the following command: netstat -ap | grep LIST The p option will require root access. This will show the ports that are in the listen state. In order to have your POP3 service running, here I assume you are using xinetd to control this service, issue the following commands: cd /etc/xinetd.d edit ipop3 change disable = yes to disable = no save the file service xinetd restart This should get stuff working. -- Jim Dickenson mailto:dickenson@xxxxxxxx Computers for Marketing Corporation http://www.cfmc.com/ > From: "Ed McCorduck" <ed@xxxxxxxxxxxxxxxxxxxxxx> > Organization: State University of New York College at Cortland > Reply-To: redhat-list@xxxxxxxxxx > Date: Sat, 17 Jan 2004 07:17:14 -0500 > To: <redhat-list@xxxxxxxxxx> > Subject: RE: pop won't authenticate my password > >> -----Original Message----- >> From: redhat-list-admin@xxxxxxxxxx >> [mailto:redhat-list-admin@xxxxxxxxxx] On Behalf Of Ben Yau >> Sent: Friday, January 16, 2004 7:53 PM >> To: redhat-list@xxxxxxxxxx >> Subject: RE: pop won't authenticate my password >> >> >>> >>> Thanks, Ben. No, I'm not able to get into my pop server at >> all either >>> through the Mozilla client nor through Telnet (see my >> previous reply >>> to Rodolfo's message). Is there another way to get into my >> pop server >>> to see what's going on? >> >> Hi Ed. >> >> Here is how I would go about diagnosing: >> Log into the pop server machine: >> >> # netstat -lan >> >> That will tell what ports your machine is currently listening >> to. 110 should show up in the listing similar to: >> >> tcp 0 0 10.253.0.150:110 10.253.32.76:2952 >> TIME_WAIT >> >> If it doesn't ,then your pop daemon is not running. > > > Thanks so much, Ben. Here's part of what I got when I did netstat -lan: > > tcp 0 0 0.0.0.0:1024 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:1025 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:783 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:111 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:6000 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:80 0.0.0.0:* > LISTEN > > tcp 0 0 0.0.0.0:22 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:631 0.0.0.0:* > LISTEN > > tcp 0 0 127.0.0.1:25 0.0.0.0:* > LISTEN > > tcp 0 0 192.168.1.101:3351 192.168.1.100:139 > TIME_WAIT > > I don't see 110 anywhere, so I guess we can conclude that my pop daemon > is in fact not running and this could be the source of my problems. The > irritatingly newbie question I have now is how do I turn my pop daemon > on? I assumed this would have been done automatically when I installed > the imap-2001a-18.i3 RPM containing ipop3d that I downloaded from Red > Hat, but, as with a lot of things lately, my memory is fuzzy even as to > whether I actually installed this RPM (if indeed I had to download it > separately at all; maybe it even came with my download and install of > the whole RH9 itself--I sure wish I could remember these things). > Anyway, if you could help me get my pop server running, I'd appreciate > it. Thanks, and thanks also for your extensive response to my last post. > > > > Ed McCorduck > Department of English > State University of New York College at Cortland > ed@xxxxxxxxxxxxxxxxxxxxxx > http://mccorduck.cortland.edu > http://McCorduck.ws > > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
