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 see no files under maildir so looks like messages are not persisted
When I leave http://localhost:8025 open for some time I see a bunch of email collected there, but as soon as click on "inbox", all the messages disappear.
When I send a message to mailhog with this configuration I get "Unable to store message" error
I can fix issue #2 if I remove storage related configuration from the docker
So here is the setup which doesn't work:
mail:
container_name: sp-mail
image: mailhog/mailhog
restart: always
privileged: true
tty: true
command: ["-storage=maildir", "-maildir-path=/maildir"]
ports:
- 1025:1025
- 8025:8025
volumes:
- "/home/user/mailhog/maildir:/maildir"
So here is the setup that works:
mail:
container_name: sp-mail
image: mailhog/mailhog
ports:
- 1025:1025
- 8025:8025
Please see if you can spot some issues there.
Thanks!
The text was updated successfully, but these errors were encountered:
The issues is solved by providing user: root to the docker-compose file.
The reason for that is the folder /maildir has the root owner/group and 755 permission.
By default the Mailhog process is started as "mailhog" user so it doesn't have write permission to the /maildir folder. So we need to start it as a "root" user
hi,
I have two questions:
I can fix issue #2 if I remove storage related configuration from the docker
So here is the setup which doesn't work:
mail:
container_name: sp-mail
image: mailhog/mailhog
restart: always
privileged: true
tty: true
command: ["-storage=maildir", "-maildir-path=/maildir"]
ports:
- 1025:1025
- 8025:8025
volumes:
- "/home/user/mailhog/maildir:/maildir"
So here is the setup that works:
mail:
container_name: sp-mail
image: mailhog/mailhog
ports:
- 1025:1025
- 8025:8025
Please see if you can spot some issues there.
Thanks!
The text was updated successfully, but these errors were encountered: