POP3 Protocol Not Running
1.POP3 is the protocol by which users are able to hit a mail server, authenticate, and pull their mail down to their client PC.
2.Users love POP3 because POP3-based mail clients are usually feature-rich and simple to use.
3. POP3 problems may be client-based or server-based, and aren't always easy to diagnose.
4. This section offers a basic troubleshooting process for POP3, and it explains what to check to ensure that your POP3 daemon will come back up when the server is rebooted.
5.First, you should ensure that the POP3 service is actually running.
6. If it's not, user mail clients will be unable to connect to the server and download waiting messages.
7. Use these commands to determine whether the service is up:
$ telnet localhost 110
Trying 127.0.0....
telnet: connect to address 127.0.0.1: Connection refused
$
$ netstat -ant | grep 110
$
The service doesn't seem to be running, so you need to turn it on:
# chkconfig --list| grep pop
ipop2: off
ipop3: off
pop3s: off
# chkconfig ipop3 on
# chkconfig --list| grep pop
ipop2: off
ipop3: on
pop3s: off
Note Pop3 is currently one of the more popular mail retrieval protocols. However, if security is a concern, pop3s is better in that it runs over an encrypted SSL session.
Once the POP3 service is on, you can repeat the first command to see whether POP3 is now functional:
$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK POP3 localhost.localdomain v2003.83rh server ready
user tweeks
+OK User name accepted, password please
pass mY1337p45swOrd
+OK Mailbox open, 3 messages
list
+OK Mailbox scan listing follows
1 122243
2 122247
3 122251
Note that the ipop3 service on Red Hat based systems is a subservice of the xinetd daemon. The current running status of xinetd can be determined with the Red Hat based command
# service xinetd status
xinetd (pid 3747) is running...
and the boot-time configuration with
# chkconfig --list xinetd
xinetd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Be sure that xinetd is running, and that it is configured to run on at least runlevels 3, 4, and 5. The output of the chkconfig -list xinetd command, when xinetd is properly configured, will look like this:
xinetd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
1.POP3 is the protocol by which users are able to hit a mail server, authenticate, and pull their mail down to their client PC.
2.Users love POP3 because POP3-based mail clients are usually feature-rich and simple to use.
3. POP3 problems may be client-based or server-based, and aren't always easy to diagnose.
4. This section offers a basic troubleshooting process for POP3, and it explains what to check to ensure that your POP3 daemon will come back up when the server is rebooted.
5.First, you should ensure that the POP3 service is actually running.
6. If it's not, user mail clients will be unable to connect to the server and download waiting messages.
7. Use these commands to determine whether the service is up:
$ telnet localhost 110
Trying 127.0.0....
telnet: connect to address 127.0.0.1: Connection refused
$
$ netstat -ant | grep 110
$
The service doesn't seem to be running, so you need to turn it on:
# chkconfig --list| grep pop
ipop2: off
ipop3: off
pop3s: off
# chkconfig ipop3 on
# chkconfig --list| grep pop
ipop2: off
ipop3: on
pop3s: off
Note Pop3 is currently one of the more popular mail retrieval protocols. However, if security is a concern, pop3s is better in that it runs over an encrypted SSL session.
Once the POP3 service is on, you can repeat the first command to see whether POP3 is now functional:
$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
+OK POP3 localhost.localdomain v2003.83rh server ready
user tweeks
+OK User name accepted, password please
pass mY1337p45swOrd
+OK Mailbox open, 3 messages
list
+OK Mailbox scan listing follows
1 122243
2 122247
3 122251
Note that the ipop3 service on Red Hat based systems is a subservice of the xinetd daemon. The current running status of xinetd can be determined with the Red Hat based command
# service xinetd status
xinetd (pid 3747) is running...
and the boot-time configuration with
# chkconfig --list xinetd
xinetd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
Be sure that xinetd is running, and that it is configured to run on at least runlevels 3, 4, and 5. The output of the chkconfig -list xinetd command, when xinetd is properly configured, will look like this:
xinetd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
0 Comments