Skip to content
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

[BUG] <Mail-Support for Office365 not workiing> #77

Open
1 task done
C600K3D opened this issue Dec 16, 2024 · 1 comment
Open
1 task done

[BUG] <Mail-Support for Office365 not workiing> #77

C600K3D opened this issue Dec 16, 2024 · 1 comment

Comments

@C600K3D
Copy link

C600K3D commented Dec 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I have a prod instance of snipe-it with the following mail config to enable mail support.

    MAIL_PORT_587_TCP_ADDR=smtp.office365.com
    MAIL_PORT_587_TCP_PORT=587
    MAIL_ENV_FROM_ADDR=test@mydomain.com
    MAIL_ENV_FROM_NAME=snipe-it
    MAIL_ENV_ENCRYPTION=tls 
    MAIL_ENV_USERNAME=test@mydomain.com
    MAIL_ENV_PASSWORD=MyPassword
    MAIL_ENV_DRIVER=smtp
    MAIL_ENV_AUTO_EMBED_METHOD=attachment

For some reason snipe-it cannot establish a connection to the smtp server by itself. I can however establish a connection manually with telnet and curl. I have verified that the env variables are set correctly and that the firewall is not blocking the corresponding traffic. In addition I set up a dev system using the exact same docker-compose.yml file with the result that it can send emails, although it can't send CC.
Neither docker logs nor the laravell log are of any use. The laravell log only shows that snipe-it tries to connect to the smtp server everyday at midnight unsuccessfully because the ssl handshake times out, but does not log the mail sending action and the consequent error.

Expected Behavior

Snipe-it should establish the connection to the server. If that was not possible for unforeseen reasons, snipe-it should should log why the e-mail could not be sent.

Steps To Reproduce

Environment

- OS: Debian 12
- How docker service was installed: Docker was installed with the official docker install script. The service is being run via docker compose

CPU architecture

x86-64

Docker creation

docker compose up -d

Container logs

[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
Snipe-IT: https://snipeitapp.com/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: v7.0.13-ls304
Build-date: 2024-11-11T20:35:20+00:00
───────────────────────────────────────
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Issues
Development

No branches or pull requests

1 participant