E-mail not working

[JMauclair]

Hi guys,

After setting up our e-mail settings, nothing is sent through Leantime (testing with email invitations for users).

LEAN_EMAIL_RETURN = 'c******@e-polaz.com'                            
LEAN_EMAIL_USE_SMTP = true // tested with false too   
LEAN_EMAIL_SMTP_HOSTS = '****.e-polaz.com'                         
LEAN_EMAIL_SMTP_AUTH = true                
LEAN_EMAIL_SMTP_USERNAME = 'c****@e-polaz.com'                 
LEAN_EMAIL_SMTP_PASSWORD = '****'                   
LEAN_EMAIL_SMTP_AUTO_TLS = true
LEAN_EMAIL_SMTP_SECURE = 'TLS'  // tested with SSL too                  
LEAN_EMAIL_SMTP_SSLNOVERIFY = false  //test with true too
LEAN_EMAIL_SMTP_PORT = '587'  // tested with 465 too

We tried with SMTP, without, with TLS, SSL, SSLNOVERIFY true, false, and nothing is working.
We have special chars in our password, maybe this could be an issue ?

Our mail server is running with Mailcow.

[marcelfolaron]

Thanks for reaching out.

Generally special characters are not a problem with the exception of single quotes. If you use single quotes they would need to be escaped using a \

Can you try setting LEAN_DEBUG to 1 and check the output in storage/logs/
The debug mode will give you detailed SMTP logs and should tell us where it fails exactly.

[Geolle]

seem issue with me , please help

 LEAN_EMAIL_RETURN: xxxxx@163.com
  LEAN_EMAIL_SMTP_AUTH: "true"
  LEAN_EMAIL_SMTP_AUTO_TLS: "true"
  LEAN_EMAIL_SMTP_HOSTS: smtp.163.com
  LEAN_EMAIL_SMTP_PASSWORD: xxxxxxxxxxxxxx
  LEAN_EMAIL_SMTP_PORT: "465"
  LEAN_EMAIL_SMTP_SECURE: SSL
  LEAN_EMAIL_SMTP_SSLNOVERIFY: "true"
  LEAN_EMAIL_SMTP_USERNAME: xxxxxx@163.com
  LEAN_EMAIL_USE_SMTP: "true"

[2025-04-08 16:48:37] production.DEBUG: 4 SMTP -> get_lines(): select timed-out in (300 sec)  
[2025-04-08 16:48:37] production.DEBUG: 2 SERVER -> CLIENT:   
[2025-04-08 16:48:37] production.DEBUG: 3 Connection: closing due to error  
[2025-04-08 16:48:37] production.DEBUG: 3 Connection: closed  
[2025-04-08 16:48:37] production.DEBUG: 4 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting  
[2025-04-08 16:48:37] production.INFO: Cron Schedule Output: 
 2025-04-08 16:43:16 Running [plugins:checkLicense] ............. 5.99ms DONE
 2025-04-08 16:43:16 Running [queue:emails] ..................... 5分钟20秒 DONE
 2025-04-08 16:48:37 Running [reports:telemetry] ................ 0.75ms DONE
 2025-04-08 16:48:37 Running [reports:dailyIngestion] .......... 67.90ms DONE

 
[2025-04-08 16:48:52] production.DEBUG: 4 SMTP -> get_lines(): select timed-out in (300 sec)  
[2025-04-08 16:48:52] production.DEBUG: 2 SERVER -> CLIENT:   
[2025-04-08 16:48:52] production.DEBUG: 3 Connection: closing due to error  
[2025-04-08 16:48:52] production.DEBUG: 3 Connection: closed  
[2025-04-08 16:48:52] production.DEBUG: 4 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting  


[2025-04-08 17:43:00] production.DEBUG: 3 Connection: opening to smtp.163.com:465, timeout=20, options=array (
 'ssl' => 
 array (
   'verify_peer' => false,
   'verify_peer_name' => false,
   'allow_self_signed' => true,
 ),
)  
[2025-04-08 17:43:00] production.DEBUG: 3 Connection: opened  
[2025-04-08 17:43:21] production.DEBUG: 4 SMTP INBOUND: ""  
[2025-04-08 17:43:21] production.DEBUG: 2 SERVER -> CLIENT:   
[2025-04-08 17:43:21] production.DEBUG: 3 Connection: closing due to error  
[2025-04-08 17:43:21] production.DEBUG: 3 Connection: closed  
[2025-04-08 17:43:21] production.DEBUG: 4 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting  
[2025-04-08 17:43:21] production.DEBUG: 3 Connection: opening to smtp.163.com:465, timeout=20, options=array (
 'ssl' => 
 array (
   'verify_peer' => false,
   'verify_peer_name' => false,
   'allow_self_signed' => true,
 ),
)  
[2025-04-08 17:43:21] production.DEBUG: 3 Connection: opened  
[2025-04-08 17:43:41] production.DEBUG: 4 SMTP INBOUND: ""  
[2025-04-08 17:43:41] production.DEBUG: 2 SERVER -> CLIENT:   
[2025-04-08 17:43:41] production.DEBUG: 3 Connection: closing due to error  
[2025-04-08 17:43:41] production.DEBUG: 3 Connection: closed  
[2025-04-08 17:43:41] production.DEBUG: 4 SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting  

[marcelfolaron]

The connection seems to be failing. Try using TLS instead of SSL and also see if they have port 587 available. 465 is deprecated for smtp usage and keeps causing issues.

[mkleger]

I have the same problem, when I test via the console with the following command I get an e-mail:
./leantime email:testemail --address=xyz@xyz.dd

But when I set the due date via the UI on a task, nothing happens in the log or anything else.
What exactly has to be done to receive an e-mail?

[marcelfolaron]

To reduce the noise update notification emails would create we are sending emails via through the following process:

1. emails added to a queue and then sent out at the interval the user selects under the edit profile section for notifications.
2. emails are not sent to the person performing the update.

So if you are updating the task you would not receive an update email since we assume you know you made the update :)

Since your command line test worked it means email is set up correctly.

One thing to check though is that the cron job for the email queue is running. If you are using docker it should run for you and you would see that in the logs. If this is a non docker set up you should run the schedule:run command (https://docs.leantime.io/installation/configuration?id=cron-jobs). With that said we are triggering the job through the UI as well but that requires someone to be logged in and creating requests.

[mkleger]

But if I plan a task in the future (days, weeks or even months) I have done this myself, will I not receive any e-mails or does this only apply to things that are happening right now?

I can see the queue for the e-mails in the log, so I think the whole thing should work:

  2025-07-16 16:30:00 Running [queue:emails] ..................... 5.82ms DONE
  2025-07-16 16:30:00 Running [queue:httprequests] ............... 4.97ms DONE
  2025-07-16 16:30:00 Running [queue:default] .................... 1.14ms DONE
  2025-07-16 16:30:00 Running [reports:telemetry] ................ 1.24ms DONE
  2025-07-16 16:30:00 Running [reports:dailyIngestion] ........... 3.04ms DONE```