Work is ongoing on an approach that relies on fewer classes than the previous proposals. It still uses a plugin manager and YAML plugins. But the focus lies on ease of use. To define a custom mail, it should be enough to add a YAML block which points to a template - nothing else. This is not fully implemented just yet, but should be ready within a week. A meeting is scheduled for 17. December to discuss the new approach.
Drupal 11.3 will not include the experimental mailer module. It fails to meet the beta requirements at this time. So, the new target for core inclusion will be 11.4/12.0.
It has been mentioned lately in the core-development slack channel that the feature deadline for the next release is either as early as March 17 or May 15 depending on whether progress on Drupal 12 goes well or not. The window for getting the mailer to beta might be a bit shorter this time.
Issue #3397420: Add a way to capture mails sent through the mailer transport service during tests has been committed and issue #3397418: Ensure origin headers of mails sent using the symfony-based mailer service comply to RFC5322 is RTBC.
Regrettably, the session proposal for DrupalCon Chicago 2026 was rejected. @znerol will submit one for DevDays in Athens 2026.
Next coding meeting takes place: December 17th 2025 4PM UTC+1.
Next planning meeting takes place January 7th 2026 at 4PM UTC+1.
Comments
Comment #2
znerol commentedComment #4
znerol commented