GLPI plugin — Send bulk HTML emails to all registered users or filtered groups
Mail Blast lets any GLPI administrator compose and send a bulk HTML email to every active user that has a default email address registered — directly from GLPI's interface, using its native SMTP configuration.
No external services or extra runtime dependencies beyond GLPI itself.
| Feature | Details |
|---|---|
| Recipient filtering | Send to all users, specific organizations, specific profiles, or hand-picked individual users. Recipient count updates live as you change the selection. |
| Send from | Uses the address configured in GLPI's Email notification settings (linked from the config page); no per-send override. |
| Reply to selector | Pick any active GLPI user with a registered email address. When selected, it is used as both the From: and Reply-To: address for that send. |
| Rich-text body editor | TinyMCE 7 (GLPI 11) — bold, italic, tables, images, lists, indentation, text alignment |
| Text alignment | Left, center, right and justify buttons in the toolbar |
| Footer editor | Native contenteditable editor with bold, italic and underline; line breaks preserved |
| Inline images | Images inserted in the body are converted to base64 at send time and immediately deleted from the server |
| Attachments | Drag-and-drop or file picker; bytes travel as base64 — never stored on the server |
| Attachment size limit | Configurable maximum combined attachment size (default 15 MB); enforced in the browser before any upload |
| GLPI MIME validation | Only file types allowed by GLPI's document type config are accepted |
| Test send | Send to your admin address or up to 5 comma-separated addresses before the mass mailing |
| Sending report (XLSX) | Download a formatted Excel report after every send with date, subject, email, status and reason for each recipient |
| AJAX progress modal | Real-time progress bar, sent / errors / pending counters, elapsed time, per-address error list |
| Cancel mid-send | Two-click cancel button stops the queue at the next batch |
| Queue-based sending | Recipients processed in configurable batches; the browser never freezes |
| Configurable batch size | Batch size and inter-batch delay adjustable from the plugin configuration page |
| Form persistence | Subject and footer saved in glpi_configs and restored on next visit |
| Multi-send safe | CSRF token rotated after each AJAX call |
| Cooldown protection | 30-second cooldown after each send prevents accidental duplicate blasts from concurrent browser tabs |
| Duplicate recipient guard | Within-batch deduplication skips users sharing an email address so no recipient receives the same message twice |
| Send history | Configurable history of 10–100 mass sends stored and displayed on the configuration page (default: 10) (date, subject, sent count, failed count) with server-timezone timestamps |
| Full i18n | Base language: en (without dedicated .po/.mo); translations: es_MX, fr_FR, de_DE |
| Update check | Configuration page checks GitHub releases (cached 6h) and shows an alert linking to the latest release when a newer version is available |
| Requirement | Version |
|---|---|
| GLPI | ≥ 11.0 |
| PHP | ≥ 8.2 |
| SMTP | Must be configured under Setup → Notifications → Email followups |
- Download the zip file from the releases page.
- Extract its contents into your GLPI plugins directory:
glpi/plugins/mailblast/ - In GLPI go to Setup → Plugins, find Mail Blast and click Install, then Enable.
- The plugin appears in the Administration menu as Mail Blast.
cd /path/to/glpi/plugins
git clone https://github.com/monta990/mailblast.gitThen install and enable from Setup → Plugins.
| Field | Notes |
|---|---|
| Subject | Required. Plain text, max 250 characters. |
| Message body | Required. Full HTML — paste images, insert tables, format text, align paragraphs. Images inserted here are automatically embedded as base64 at send time and removed from the server. |
| Footer | Optional. Plain text with bold, italic and underline. Appended below the body separated by a horizontal rule. Persisted between sessions. |
Drag files into the drop zone or click browse. Selected files appear in a list with size and a remove button. Only MIME types allowed by GLPI's document configuration are accepted.
The total combined size of all attachments is validated against the configured limit (default 15 MB) directly in the browser — files that would exceed the limit are rejected before any data is sent. Files are read into browser memory and transmitted as base64 JSON — nothing is saved to the server's filesystem or database.
Before sending to everyone, verify layout and attachments:
- Send to my address — delivers to the default email of the currently logged-in administrator.
- Send to a specific address — enter one or up to 5 comma-separated email addresses.
Result is shown inline without page reload.
Use the Send to selector to narrow who receives the email:
| Option | Behaviour |
|---|---|
| All active users | Every active user with a default email address (original behaviour, default). |
| Specific organizations | Only users that belong to the selected organizations. Entity recursion is handled automatically — users assigned to a parent entity with Recursive enabled are included when any of their child entities is selected. Hold Ctrl / Cmd to select multiple. |
| Specific profiles | Only users that have one of the selected profiles assigned. Hold Ctrl / Cmd to select multiple. |
| Specific users | Only the individual users you pick from the list. Hold Ctrl / Cmd to select multiple. |
The recipient count badge updates live via AJAX as you change the selection. The Send button is disabled automatically when the count is 0.
The From address always follows GLPI's own Setup → Notifications (front/notificationmailingsetting.form.php) configuration. There is no per-send override on this page; a link to that settings screen is shown on the plugin's configuration page instead.
A Reply to dropdown lists every active GLPI user with a registered email address. Selecting a user sets the Reply-To: header, so replies from recipients are delivered to that mailbox instead of the default notification address — and it is also used as the From: header for that send, so recipients see the same address in From: and Reply-To:. Leaving it at Default keeps GLPI's notification configuration completely unchanged. Applies to both the mass send and the test send.
Note: Some SMTP relays force the envelope sender /
Sender:header to match the authenticated SMTP account regardless of theFrom:override, which can make mail clients show "sent on behalf of". Check with your SMTP provider if this is a concern.
Click Send to selected recipients. A confirmation dialog shows the recipient count. The plugin sends only to active, non-deleted users with a default email address.
A progress modal shows real-time status. You can cancel at any time — emails already sent are not recalled.
Access the configuration page via the gear icon in the plugin list (Setup → Plugins) or via the settings button in the plugin's card header.
| Setting | Default | Range | Description |
|---|---|---|---|
| Batch size | 15 | 1–100 | Number of emails sent per batch. Lower values reduce SMTP load on slow servers; higher values speed up large sends. |
| Delay between batches | 120 ms | 0–5000 ms | Wait time between consecutive batches. Increase this if your SMTP provider enforces rate limits (e.g. 500 ms for restrictive providers). |
| Max attachment size | 15 MB | 1–100 MB | Maximum combined size of all attachments. Enforced in the browser. Prevents SMTP timeouts caused by large payloads being sent to hundreds of recipients. |
The configuration page also shows a send history table with the last 10 mass sends (date, subject, sent count, failed count). Timestamps use the server's configured PHP timezone; the column header shows the timezone identifier for clarity.
Browser PHP / GLPI
│ │
├─ queue_init POST ──────────────────► │ prepare campaign payload
│ │ buildHtmlBody() → HTML5 wrapper
│ │ html2text() → plain-text alt body
│ ◄── { send_id, html, plain, … } ─── │ store only queue metadata in glpi_configs
│ │
├─ queue_process POST (offset=0) ────► │ SELECT users LIMIT batch_size OFFSET 0
│ │ send batch via Symfony Mailer
│ ◄── { done, next_offset, … } ───── │
│ │
├─ [wait batch_delay_ms] ─────────── → │
├─ queue_process POST (offset=N) ────► │ SELECT … LIMIT batch_size OFFSET N
│ … │ …
└─ done ◄───────────────────────────── │ cleanupJob()
Sending to hundreds of recipients in a single HTTP request would hit PHP's max_execution_time and the browser's request timeout. The queue approach splits the work into small batches, each completing in under a second. The browser drives the loop — no background process or cron job needed.
- Attachments — read as base64 in the browser, posted as JSON, decoded to a per-request temp file, attached to the email via Symfony Mailer, deleted immediately after the email is sent.
- Body images — uploaded to
glpi_documentsby TinyMCE's native handler during composition. At queue initialization they are read into the campaign payload as inline CID data and are not persisted in the queue. The current implementation does not delete arbitrary GLPI documents referenced by message content.
Access requires the GLPI right config: UPDATE (full administrator profile). No additional rights configuration needed.
See CHANGELOG.md.
Edwin Elias Alvarez — GitHub
If you like my work, you can support me by a donate here:
GPL v3 or later. See LICENSE.
Report bugs or request features on the issue tracker.