---
name: "ipopd"
section: "8"
platform: "linux"
package: "ipopd"
version: "8:2007e~dfsg-3.1"
release: "Debian 6.0 (Squeeze)"
platforms: ["linux"]
url: "https://new.carta.tech/ipopd"
---

# ipopd(8)

Post Office Protocol server

## NAME

IPOPd - Post Office Protocol server

## SYNOPSIS

**/usr/sbin/ipop2d**

**/usr/sbin/ipop3d**

## DESCRIPTION

*ipop2d* and *ipop3d* are servers which support the **POP2** and **POP3** remote mail access protocols respectively. *ipop2d* and *ipop3d* can also be used by **POP2** and **POP3** clients respecitively to access mailboxes on **IMAP** servers by specifying a login user name in the form \<host\>:\<user\> e.g., **SERVER.WASHINGTON.EDU:SMITH.**

These daemons contain CRAM-MD5 and APOP support.  See the md5.txt documentation file for additional information.

*ipop2d* and *ipop3d* are invoked by the internet server (see [*inetd*(8)](/inetd/8.md)), normally for requests to connect to the **POP** port as indicated by the */etc/services* file (see [*services*(5)](/services/5.md)).

## SEE ALSO

[imapd(8)](/imapd/8.md)

## BUGS

The **POP2** and **POP3** protocols are intrinsically less flexible than **IMAP** and do not maintain \`read' vs \`unread' state on the server.  As a result, most **POP** based software transfers all the mail from the server to the client and deletes it from the server.  This necessarily locks the user into using only a single client.

**POP3** does not allow you to specify an alternate folder from the user's default.