chaas/ispmail-workaround-org
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

re-add bookworm and add deprecation notice on every page

Browse source
This commit is contained in:
Christoph Haas 2025-11-02 14:15:40 +01:00
parent 7bb8bc74b7
commit 8f4bef9908
52 changed files with 3925 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

34
src/content/docs/ispmail-bookworm/150-testing-imap.mdx Normal file
View file

@ -0,0 +1,34 @@
---
title: Testing IMAP
lastUpdated: 2023-10-04
slug: ispmail-bookworm/testing-imap
sidebar:
order: 150
---
You have already completed the configuration of Dovecot. So fetching emails via IMAP should already work. Let’s give it
a try using a simple-looking but powerful IMAP client: _mutt_.
```
mutt -f imaps://john@example.org@webmail.example.org
```
The connection URL may look a little confusing because of the two “@” characters. Usually _mutt_ expects the format
`imaps://user@server`. And as we use the email address as the “user” part you get this look.
You should get prompted for the password which we set to “summersun”. If you get any certificate warnings then check if
you used the correct server name to connect to and if you completed the certificate/LetsEncrypt part earlier in this
guide.
After logging in you will see an empty inbox:
![The mutt mail client showing an empty inbox](images/testing-imap-mutt-empty-inbox.png)
Or if you have played around with quotas in the previous section you will see a couple of emails plus the quota
warnings:
![The mutt mail client showing quota warning emails](images/testing-imap-mutt-inbox-quota-mails.png)
Very good – IMAP connections and authentication works. That’s all we wanted to test. Exit _mutt_ by pressing “q”.
Congratulations. At this point your server can already receive emails.