Cannot Send Mail

[iali99-svg]

Debug mode

• [X] I have enabled debug mode
• [X] I have read checked the Common Issues page

Describe the bug

hello, i installed snipe but i can't send mail with external smtp, i tried with custom smtp and outlook, but it doesn't go, using mailhog instead, i can see the mail start from mailhog logs, but the recipients don't receive anything.

Going into debug mode, i see this error when i try to use my smtp:

trying mailhog instead, it tells me mail sent and from debug mode I see the same error, but no one receives the mail Thanks

Reproduction steps

hello, i installed snipe but i can't send mail with external smtp, i tried with custom smtp and outlook, but it doesn't go, using mailhog instead, i can see the mail start from mailhog logs, but the recipients don't receive anything.

Going into debug mode, i see this error when i try to use my smtp:

trying mailhog instead, it tells me mail sent and from debug mode I see the same error, but no one receives the mail Thanks

Expected behavior

hello, i installed snipe but i can't send mail with external smtp, i tried with custom smtp and outlook, but it doesn't go, using mailhog instead, i can see the mail start from mailhog logs, but the recipients don't receive anything.

Going into debug mode, i see this error when i try to use my smtp:

trying mailhog instead, it tells me mail sent and from debug mode I see the same error, but no one receives the mail Thanks

Screenshots

No response

Snipe-IT Version

v6.1.2 - build 10938 (master)

Operating System

centos

Web Server

docker

PHP Version

8.1.20

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

[welcome[bot]]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[snipe]

That's a warning level notification, so it shouldn't be interfering with the actual send. What do you see in your app logs?

[iali99-svg]

hi @snipe i have this error:

The email could not be sent. No additional error message provided. Check the mail settings and the app log.

The log file was not created, but from the container logs I see the following, how can I fix it?

2023-07-30 23:37:56,260 WARN received SIGTERM indicating exit request 2023-07-30 23:37:56,260 INFO waiting for exit_on_any_fatal, apache, run_schedule to die 2023-07-30 23:37:57,263 INFO stopped: run_schedule (terminated by SIGTERM) 2023-07-30 23:37:57,295 INFO stopped: apache (terminated by SIGTERM) 2023-07-30 23:37:57,300 INFO stopped: exit_on_any_fatal (terminated by SIGTERM) Module ssl already disabled Nothing to migrate. Configuration cache cleared! Configuration cache cleared! Configuration cached successfully! 2023-07-30 23:37:59,813 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2023-07-30 23:37:59,816 INFO supervisord started with pid 1 2023-07-30 23:38:00,819 INFO spawned: 'exit_on_any_fatal' with pid 36 2023-07-30 23:38:00,822 INFO spawned: 'apache' with pid 37 2023-07-30 23:38:00,824 INFO spawned: 'run_schedule' with pid 38 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.21.0.6. Set the 'ServerName' directive globally to suppress this message No scheduled commands are ready to run. 2023-07-30 23:38:02,222 INFO success: exit_on_any_fatal entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-30 23:38:02,223 INFO success: apache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-07-30 23:38:02,223 INFO success: run_schedule entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

[snipe]

Hi, thanks for this - those looks like docker logs. What I need to see is what’s in your storage/logs/laravel.log that would give me insight as to what might be happening.

[iali99-svg]

no log file is generated, and you can't even see it from the debug logs. From the old installation I was seeing the following, which I am experiencing with both gmail and custom smtp with port 465

[2023-07-30 17:28:40] production.ERROR: Connection could not be established with host smtp.gmail.com :stream_socket_client(): Unable to connect to tcp://smtp.gmail.com:587 (Operation timed out) {"exception":"[object] (Swift_TransportException(code: 0): Connection could not be established with host smtp.gmail.com :stream_socket_client(): Unable to connect to tcp://smtp.gmail.com:587 (Operation timed out) at /var/www/html/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Transport/StreamBuffer.php:261) [stacktrace]

[snipe]

Are you tucked behind a firewall or anything? The connection error isn’t Snipe-IT’s error, the underlying mail system cannot connect to your mail servers. That’s usually a firewall, networking or DNS issue. From your container, can you ping the mail servers? What’s the response?

[iali99-svg]

From inside the container I can telnet to my mail server on port 465 without any problems