Merge #1188

1188: You have to delete the Admin Pod, not the Imap pod r=muhlemmer a=fionera

## What type of PR?

documentation

## What does this PR do?

### Related issue(s)

## Prerequistes
Before we can consider review and merge, please make sure the following list is done and checked.
If an entry in not applicable, you can check it or remove it from the list.

- [ ] In case of feature or enhancement: documentation updated accordingly
- [ ] Unless it's docs or a minor change: add [changelog](https://mailu.io/master/contributors/guide.html#changelog) entry file.


Co-authored-by: Fionera <fionera@fionera.de>

docs/kubernetes/mailu/index.rst

@@ -210,11 +210,11 @@ If the login problem still persists, or more specific, happens now and then and
 - Depending on your network configuration you could still see some ``allow_nets check failed`` results in the logs. This means that the IP is not allowed a login
 - If this is happening your network plugin has troubles with the Nginx Ingress Controller using the ``hostNetwork: true`` option. Known cases: Flannel and Calico.
 - You should uncomment ``POD_ADDRESS_RANGE`` in the ``configmap.yaml`` file and add the IP range of your pod network bridge (the range that sadly has failed the ``allowed_nets`` test)
-- Delete the IMAP pod and wait for it to restart
+- Delete the Admin pod and wait for it to restart
 
 .. code:: bash
 
     kubectl -n mailu-mailserver get po
-    kubectl -n mailu-mailserver delete po/mailu-imap...
+    kubectl -n mailu-mailserver delete po/mailu-admin...
 
 Happy mailing!