Checking a mailbox with POP3 commands
To check the email in an account's inbox using
Post Office
Protocol version 3 (POP3) commands
from a
command-line interface (CLI), if the POP3 server, e.g.,
Dovecot, is
listening on the default
well-known port of 110 by connecting to the POP3 server using
Telnet and issuing the
following commands:
Authentication
-
user <username> - enter the username for the account
-
pass <password> - enter the password for the account
Mailbox Status & Information
-
stat - see the number of messages in the inbox
-
list [msg] - lists all messages or a specific message number along with its
size
-
uidl [msg] <n> - returns the unique message ID for tracking a specific
email
-
capa - request a list of the server's capabilities
Mail Retrieval
-
retr <msg> – the retrieve command downloads/displays the full content of
the specified message number
-
top <msg> <n> – retrieves the message header plus a specified
number (n) of body lines.
Mail Management & Session Control
-
dele <msg> - delete a particular message
-
rset - Unmarks any messages that were previously marked for deletion
during the session
-
noop - performs no operation (can be used as a keep-alive check)
-
quit - disconnect from the POP3 server
E.g.:
# telnet 127.0.0.1 110
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
+OK Dovecot ready.
capa
+OK
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
AUTH-RESP-CODE
STLS
USER
SASL PLAIN
.
user nell
+OK
pass thePassword
+OK Logged in.
stat
+OK 278 59431689
retr 278
+OK 691 octets
Return-Path: <jdoe@moonpoint.com>
Received: from moonpoint.com (localhost [127.0.0.1])
by moonpoint.com (8.14.7/8.14.7) with ESMTP id 6A4122DY022073
for <nell@moonpoint.com>; Tue, 3 Nov 2026 20:02:02 -0500
Received: (from jdoe@localhost)
by moonpoint.com (8.14.7/8.14.7/Submit) id 6A4122iG022070
for nell@moonpoint.com; Tue, 3 Nov 2026 20:02:02 -0500
Date: Tue, 3 Nov 2026 20:02:02 -0500
From: jdoe <jdoe@moonpoint.com>
To: nell@moonpoint.com
Subject: Example email
Message-ID: <20261104010202.GA21379@moonpoint.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
This is an example email.
.
dele 278
+OK Marked to be deleted.
rset
+OK
noop
+OK
quit
+OK Logging out, messages deleted.
Connection closed by foreign host.
#
Or, if you want to see the size of a particular message, its unique
message ID, or just a portion of the message rather than the entire message:
[jdoe@moonpoint ~]$ telnet 127.0.0.1 110
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
+OK Dovecot ready.
user nell
+OK
pass thePassword
+OK Logged in.
stat
+OK 292 60503043
list 292
+OK 292 713
uidl 292
+OK 292 00026d86481e759f
top 292
+OK
Return-Path: <abigail@moonpoint.com>
Received: from moonpoint.com (localhost [127.0.0.1])
by moonpoint.com (8.14.7/8.14.7) with ESMTP id 6A60FcqT005571
for <nell@moonpoint.com>; Thu, 5 Nov 2026 19:15:38 -0500
Received: (from abigail@localhost)
by moonpoint.com (8.14.7/8.14.7/Submit) id 6A60FcLW005570
for nell@moonpoint.com; Thu, 5 Nov 2026 19:15:38 -0500
Date: Thu, 5 Nov 2026 19:15:38 -0500
From: Abigail Adams <abigail@moonpoint.com>
To: nell@moonpoint.com
Subject: Test email
Message-ID: <20261106001538.GA5472@moonpoint.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
.
top 292 5
+OK
Return-Path: <abigail@moonpoint.com>
Received: from moonpoint.com (localhost [127.0.0.1])
by moonpoint.com (8.14.7/8.14.7) with ESMTP id 6A60FcqT005571
for <nell@moonpoint.com>; Thu, 5 Nov 2026 19:15:38 -0500
Received: (from abigail@localhost)
by moonpoint.com (8.14.7/8.14.7/Submit) id 6A60FcLW005570
for nell@moonpoint.com; Thu, 5 Nov 2026 19:15:38 -0500
Date: Thu, 5 Nov 2026 19:15:38 -0500
From: Abigail Adams <abigail@moonpoint.com>
To: nell@moonpoint.com
Subject: Test email
Message-ID: <20261106001538.GA5472@moonpoint.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
A test message.
Abigail
.
dele 292
+OK Marked to be deleted.
quit
+OK Logging out, messages deleted.
Connection closed by foreign host.
[jdoe@moonpoint ~]$
[/network/email]
permanent link
Checking on dpkg package updates
You can check the version of a
Debian package (dpkg) on a
Linux system using the command dpkg -s
pkgName where pkgName is the name of the package.
If you wish to check on whether an upgrade is available for the
package, you should first update your local package index to ensure
your system knows about the latest versions available in the
repositories
with the sudo apt update command. If updates
are available you will see something like
19 packages can be upgraded. Run 'apt list
--upgradable' to see them.
If you want to see whether an update is available for a particular
dpkg package, e.g., winetricks, you can use the command
apt-cache policy pkgName. Because
dpkg manages local .deb files and doesn't
directly check remote repositories, you need to use
APT, which is the
frontend for dpkg to compare the installed version against what is available
in the repositories.
alice@Wonderland:~$ apt-cache policy winetricks
winetricks:
Installed: 20250102-1build1
Candidate: 20250102-1build1
Version table:
*** 20250102-1build1 500
500 http://us.archive.ubuntu.com/ubuntu resolute/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu resolute/universe i386 Packages
100 /var/lib/dpkg/status
alice@Wonderland:~$
The Installed and
Candidate lines indicate whether an update is
available.
- Installed: The version currently running on your system.
- Candidate: The highest version available in the repositories that your
system is ready to install.
If the Candidate version is newer (higher) than the Installed version, an
update is available. If the version is the same then a newer version is not
available.
Alternatively, you can use the command apt list
--upgradable pkgName to check on whether an update is
available for a single package. If it returns the package name, an update is
available. If it returns nothing, the package is already up-to-date.
alice@Wonderland:~$ apt list --upgradable winetricks
alice@Wonderland:~$
To see a list of all packages that you can upgrade, you can use
apt list --upgradable.
[ More Info ]
[/os/unix/linux/utilities/package]
permanent link
Deluge's location for the incoming port number on Windows systems
When Deluge
is run on a system running the Microsoft Windows operating system,
it stores the location it uses for the incoming port number(s) in
a configuration file, core.conf
under the user's %APPDATA%\deluge
directory. The %APPDATA% environment variable usually
expands to something like the following, where YourUserName
is the user name for the relevant Windows account:
C:\Users\YourUsername\AppData\Roaming\deluge\core.conf
Note: You can see the value for %APPDATA%
by issuing the command echo %APPDATA%
in a command prompt window.
The %APPDATA% directory is a hidden
directory, but you can see the contents of the Deluge configuration directory
in the Windows
file manager even if you haven't turned on the display of hidden folders by putting %APPDATA%\deluge in the address field in
the file manager. You can then right-click on the file and choose to open
it with the Windows Notepad. You can also access the directory by pressing
the Win + R
keys.
By default, Deluge uses a random
network
port or the 6881-6889 range (frequently defaulting to 6881
in many setups like Docker). You can check or change the exact
active incoming port when Deluge is running under Preferences
→ Network. If you open the configuration file in a text editor, such as
Windows Notepad,
you will see something similar to the following:
"listen_ports": [6881, 6891],
"random_port": false
- listen_ports —
The incoming port range. If both numbers are the same, Deluge uses a single
configured port.
- random_port —
If true, Deluge selects a port randomly at
startup; the configured range may not reflect the active port. If
false, it uses the configured
listen_ports range.
If you need to change the port before starting Deluge, e.g., to match an
incoming port provided by a VPN provider, you can change the values.
E.g., if you wanted Deluge to use port 39755, you could put the following
entries in the file and then start Deluge:
"listen_ports": [
39755,
39755
],
"listen_random_port": null,
"listen_reuse_port": true,
Note: If you need the actual port Deluge is listening on right now, rather
than its saved setting, check Deluge's Preferences → Network →
Incoming Ports. With random port selection enabled, the active port can differ
from the saved value if you haven't restarted Deluge after updating the
port number.
When you start Deluge, you can see if there are incoming connections to
that port using the netstat
command. E.g., netstat -an | find "39755".
C:\Users\Jill>netstat -an | find "39755"
TCP 10.164.7.152:39755 0.0.0.0:0 LISTENING
TCP 10.164.7.152:39755 10.43.22.249:64621 TIME_WAIT
TCP 10.164.7.152:39755 10.157.104.168:49659 TIME_WAIT
TCP 10.164.7.152:39755 10.157.104.168:57171 TIME_WAIT
TCP 10.164.7.152:39755 10.169.234.135:49738 TIME_WAIT
TCP 10.164.7.152:39755 10.169.234.135:55102 TIME_WAIT
TCP 10.164.7.152:39755 10.175.210.63:50713 TIME_WAIT
TCP 10.164.7.152:39755 10.194.155.52:14534 SYN_RECEIVED
TCP 10.164.7.152:54686 178.93.201.240:39755 SYN_SENT
TCP 127.0.0.1:39755 0.0.0.0:0 LISTENING
TCP 192.168.1.7:39755 0.0.0.0:0 LISTENING
UDP 10.162.7.159:39755 *:*
UDP 127.0.0.1:39755 *:*
UDP 192.168.1.7:39755 *:*
C:\Users\Jill>
References:
-
Deluge FAQ
Deluge
-
Deluge User Guide
Deluge
[/network/p2p]
permanent link