You are not logged in.
Ok. This one is solved before it's started. Or maybe it is just a work-aoround. I find it hard to tell. I can find many posts and other articles about outgoing emails not working as expected. I have had quite a fight with it myself. I have to say I am not a good developer nor am I very skilled in IaC. I am an old-fashioned system admin and engineer learning my way around in the coded virtual world. I decided to add my bit to the community hoping this helps others and it may provide me with a more knowledgeable answer.
To get all this to work GLPI has been the most complex way of finding my way around to make sure all email settings are correct. What I understand now is this:
1. To Fetch emails setup an IMAP or POP connection via --> Setup/Authentication/Mailservers (in the path you will read 'Mailservers')
2. To send out email via the SMTP go to --> Setup/Notification/Email Followups Configuration (in the path you will NOT see 'Email Followups Configuration')
3. Hoover over every info 'Í' and let it sink in what it explains. The Administrator email address is an address of a mailbox that get's all the Super-Admin email.
4. The 'Email sender address' is the address of an email-account that will be used to receive replies and add those replies to ticket-conversations.
5. The 'No-Reply address' is used if sent emails cannot be replied on. GLPI has an extensive amount of email (~reply) templates to work with.
It is likely you did not create any yourself and so it's a little tough to understand all the fields to fill in.
6. Be specific using TLS and/ or SSL. SMTP+TLS means port 587. Make sure to have configured that in you emailserver setup!
7. Send a test email to the administrator.
If this works it is NOT a guarantee your notification-que will be send!
8. I have setup a service within my docker-compose environment to run cronjobs. This service (Dockerfile) needs to have the same (www-data) user as the GPLI service is using! Remember that running the job is not the same as running the service. It took me some time to get this right. The job-user needs to be chown-ed to the website-folders or the front-folder. Since this cron-service was setup and all tasks were set to run-mode CLI received emails (IMAP) were turned into tickets.
For some reason though, the CLI-mode could not setup a TLS connection for SMTP. Instead of finding my mailserver (mail.somewhere.us) it tried to confirm the environment URL (environement.somethingelse.us) to the certificate and failed. My environment is setup with Traefik as an Edge router. The email server container is outside of the Edge because Traefik can not yet proxy a TLS connection.
9. Set all automatic actions --> 'Setup/Automatic actions', concerning incoming email to GLPI-mode. For me this last one caused email communications between my ITSM solution via email to start working.
10. Go to --> 'Setup/General' and click on the tab 'Assistance' and find 'Allow anonymous ticket creation (helpdesk.receiver)' & 'Allow anonymous followups (receiver)' to decide Yes/No if emails sent by non-users (--> 'Administration/Users') can be serviced via email.
I would really like to understand why or maybe more important, how, an outbound email-job in GLPI-mode tries a different route in CLI-mode.
I can imagine easily this has to do with my specific setup but in every post I find CLI-mode as the final solution to send out email via SMTP. For some reason it took me a week of creating some focus on the problem every day for a few hours to discover my GLPI started to do the so craved for job of sending emails out to users email Inboxes.
Offline