You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
... I have understood that answers are voluntary and community-driven, and not commercial support.
... I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description
I wanted to add a mailbox and used a random password that was *not* conforming to the password policy I set up earlier. When I was done with my changes in the "Add mailbox" dialog, I clicked "Add", and the dialog was dismissed. The supposedly just-created mailbox was not visible in the list of existing mailboxes. I didn't even notice a message saying "Password does not meet the policy" in the bottom-right corner of the screen, even though it used a red background. I clicked "Add mailbox" again, and the dialog opening up showed my previous input.
From a UX point of view, this design can be greatly improved.
The modal dialog *should* only close when the mailbox could actually be created. As long as this is not the case, it should stay open, and any fields with incorrect input should be highlighted, e.g. using a red rectangle.
Logs:
n/a
Steps to reproduce:
1. Follow clickpath "Email" -> "Configuration" -> "Mailboxes"
2. Click "Add mailbox" button
3. Enter a non-existing username and a password of "1" (two times)
4. Click "Add".
5. Observe that the dialog closes, even though a one-character password violates the default password policy.
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12.7
Server/VM specifications:
AWS m5.large: 8 GB RAM, 2 vcores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
AWS EC2
Docker version:
27.3.1
docker-compose version or docker compose version:
v2.29.7
mailcow version:
2024-08a
Reverse proxy:
none
Logs of git diff:
n/a
Logs of iptables -L -vn:
n/a
Logs of ip6tables -L -vn:
n/a
Logs of iptables -L -vn -t nat:
n/a
Logs of ip6tables -L -vn -t nat:
n/a
DNS check:
n/a
The text was updated successfully, but these errors were encountered:
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12.7
Server/VM specifications:
AWS m5.large: 8 GB RAM, 2 vcores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
AWS EC2
Docker version:
27.3.1
docker-compose version or docker compose version:
v2.29.7
mailcow version:
2024-08a
Reverse proxy:
none
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: