GLPI Email Notifications: Complete Configuration Guide

How to configure email notifications in GLPI: SMTP, Gmail and Office 365 OAuth, templates, and troubleshooting undelivered emails.

Email notifications are GLPI's most critical communication channel with users. An email that doesn't arrive means an ignored ticket. This guide resolves the most common configuration issues.

Basic configuration: SMTP

Go to Configuration > Notifications > Email configuration:

  • Sending mode: SMTP
  • SMTP server: address of your email server
  • Port: 587 (STARTTLS) or 465 (SSL)
  • Authentication: Login + Password or OAuth
  • Sender email: glpi@suaempresa.com

Gmail (OAuth 2.0)

  1. Go to Google Cloud Console > APIs & Services > Credentials
  2. Create an OAuth 2.0 Client ID (type: Web Application)
  3. Add the GLPI redirect URI
  4. In GLPI, configure the OAuth provider with Client ID and Client Secret
  5. Authorize access by clicking the authorization button

Important: App Passwords still work, but OAuth is the recommended and more secure method.

Office 365 / Microsoft 365

  1. In the Azure Portal, register an application (App Registrations)
  2. Grant the Mail.Send permission (delegated or application)
  3. Create a Client Secret
  4. In GLPI, configure SMTP: smtp.office365.com, port 587, OAuth
  5. Enter Tenant ID, Client ID and Client Secret

Notification templates

Customize emails at Configuration > Notifications > Notification templates:

  • New ticket: notifies the requester that the ticket has been registered
  • Assignment: notifies the assigned technician
  • Follow-up: notifies all parties when there is an update
  • Resolution: notifies the requester with the solution
  • Satisfaction: sends a satisfaction survey after closure

Use variables such as ##ticket.title##, ##ticket.description##, ##ticket.url## in templates.

Troubleshooting

Emails not arriving

  1. Check the email queue: Administration > Email queue
  2. Check that the GLPI cron is running (front/cron.php)
  3. Test sending directly: send a test email from the interface
  4. Check GLPI and SMTP server logs
  5. Check the recipient's spam/junk folder

Authentication error

Gmail and Office 365 block basic authentication (login + password). Use OAuth 2.0 or App Passwords.

Beyond email

For real-time notifications, consider the Smart Notify module (bell in the navbar) or sending via WhatsApp and Telegram.

Frequently Asked Questions

The most common causes are: SMTP not configured, incorrect credentials, port blocked by firewall, or Gmail/Office 365 blocking due to 'less secure app'. Use OAuth instead of an app password.

Use OAuth 2.0: create credentials in the Google Cloud Console, configure the OAuth provider in GLPI and authorize access. App passwords work, but OAuth is more secure.

Configure OAuth via Azure AD: register an application, grant Mail.Send permission, and configure the credentials in GLPI. Direct SMTP requires modern authentication.

Yes. Under Configuration > Notifications > Notification templates, you can customize the HTML for each notification type (new ticket, follow-up, resolution, etc.) with dynamic variables.

Need help?