-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"null" is an invalid mailbox name #5737
Comments
I think it is indeed a bug as it takes the null as the value null (0 value) for a variable which is not allowed. |
I've looked at the request when you press the add mailbox button. The "local_part" in the payload gets sent as the value null instead of the string "null". |
I have the same error while migration my account with [email protected] (zero@...)
I guess I can work around this with an email alias and give the mailbox another name, but this is not ideal. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Push |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Push |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
😔 |
Not stale but out of scope sorry. @FreddleSpl0it |
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:
Proxmox VE 8.1.4 (Based on Debian 12.2)
Server/VM specifications:
64gb memory, 4 cores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
None
Docker version:
25.0.1
docker-compose version or docker compose version:
v2.24.2
mailcow version:
2024-01b
Reverse proxy:
Nginx
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: