Thank you for opening an issue with Mailu. Please understand that issues are meant for bugs and enhancement-requests.
For user-support questions, reach out to us on matrix.
To be able to help you best, we need some more information.
Before you open your issue
[X] Check if no issue or pull-request for this already exists.
[X] Check documentation and FAQ. (Tip, use the search function on the documentation page)
[X] You understand Mailu is made by volunteers in their free time — be conscise, civil and accept that delays can occur.
[X] The title of the issue should be short and simple. It should contain specific terms related to the actual issue. Be specific while writing the title.
Environment & Versions
Environment
[ ] docker-compose
[ ] kubernetes
[ ] docker swarm
Versions
To find your version, get the image name of a mailu container and read the version from the tag (example for version 1.7).
$> docker ps -a | grep mailu
370c59e1ae16 mailu/dovecot:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 110/tcp, 143/tcp, 993/tcp, 2525/tcp, 4190/tcp mailu_imap_1
659ab403323b mailu/rspamd:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 11332/tcp, 11334-11335/tcp mailu_antispam_1
2a7c6891203c mailu/postfix:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 25/tcp, 10025/tcp mailu_smtp_1
e7239bd8ebb6 mailu/clamav:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 3310/tcp mailu_antivirus_1
f12fc6bd6af1 mailu/unbound:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 53/tcp, 53/udp mailu_resolver_1
cbea3355472a mailu/admin:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 80/tcp mailu_admin_1
7f4e3f0bcb80 mailu/nginx:1.7 "/bin/sh -c /start.py" 3 weeks ago Up 3 weeks (healthy) 23.253.245.62:25->25/tcp, ::1:25->25/tcp, 23.253.245.62:110->110/tcp, ::1:110->110/tcp, 23.253.245.62:143->143/tcp, ::1:143->143/tcp, 23.253.245.62:465->465/tcp, ::1:465->465/tcp, 23.253.245.62:587->587/tcp, ::1:587->587/tcp, 23.253.245.62:993->993/tcp, ::1:993->993/tcp, 0.0.0.0:10025->10025/tcp, 23.253.245.62:995->995/tcp, ::1:995->995/tcp, 443/tcp, 0.0.0.0:10143->10143/tcp, 0.0.0.0:8088->80/tcp mail
$> grep MAILU_VERSION docker-compose.yml mailu.env
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}nginx:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}unbound:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}admin:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}dovecot:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}postfix:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}rspamd:${MAILU_VERSION:-1.7}
docker-compose.yml: image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}clamav:${MAILU_VERSION:-1.7}
docker-compose.yml:# image: ${DOCKER_ORG:-mailu}/${DOCKER_PREFIX:-}radicale:${MAILU_VERSION:-1.7}
Description
Using the mailu interface, i can not add an alias to redirect mail if the use account already exists. example. user1@domain.com exists and mail is delivered. I also wand mail addressed to user1@domain.com to be forwarded to user2@domain.com. when submitting the new alias, the page just reloads. there is no error message. i am able to create an alias on an account that does not exist at all.
Replication Steps
create a user account in the maillu UI
attempt to create an alias from that same user account to somewhere else
the page will reload but the alias will not be created
Expected behaviour
i would expect that the alias would be created and the mail would be delivered to two mailboxes. note that this appears to work if i use the command line docker-compose exec admin flask mailu alias user1 domain.com "user2@domain.com", however the mail is still only delivered to user1@domain.com
Logs
Often it is very useful to include log fragments of the involved component. You can get the logs via docker logs <container name> --tail 1000. For example for the admin container:
docker logs mailu_admin_1 --tail 1000
or using docker-compose docker-compose -f /mailu/docker-compose.yml logs --tail 1000 admin
If you can find the relevant section, please share only the parts that seem relevant. If you have any logs, please enclose them in code tags, like so:
from admin when adding to UI:
admin_1 | 172.23.0.13 - - [25/Feb/2021:14:40:20 +0000] "POST /ui/alias/create/atxlawyer.com HTTP/1.1" 200 10526 "https://mailu.libertymarketing.me/admin/ui/alias/create/atxlawyer.com" "Mozilla/5.0 (Macintosh; Intel Mac OS X 11_0_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.152 Safari/537.36"
Thank you for opening an issue with Mailu. Please understand that issues are meant for bugs and enhancement-requests. For user-support questions, reach out to us on matrix.
To be able to help you best, we need some more information.
Before you open your issue
Mailu
is made by volunteers in their free time — be conscise, civil and accept that delays can occur.Environment & Versions
Environment
Versions
To find your version, get the image name of a mailu container and read the version from the tag (example for version 1.7).
Description
Using the mailu interface, i can not add an alias to redirect mail if the use account already exists. example. user1@domain.com exists and mail is delivered. I also wand mail addressed to user1@domain.com to be forwarded to user2@domain.com. when submitting the new alias, the page just reloads. there is no error message. i am able to create an alias on an account that does not exist at all.
Replication Steps
create a user account in the maillu UI attempt to create an alias from that same user account to somewhere else the page will reload but the alias will not be created
Expected behaviour
i would expect that the alias would be created and the mail would be delivered to two mailboxes. note that this appears to work if i use the command line
docker-compose exec admin flask mailu alias user1 domain.com "user2@domain.com"
, however the mail is still only delivered to user1@domain.comLogs
Often it is very useful to include log fragments of the involved component. You can get the logs via
docker logs <container name> --tail 1000
. For example for the admin container:docker logs mailu_admin_1 --tail 1000
or using docker-composedocker-compose -f /mailu/docker-compose.yml logs --tail 1000 admin
If you can find the relevant section, please share only the parts that seem relevant. If you have any logs, please enclose them in code tags, like so: