Problem/Motivation

The Mail System module is a hard dependency and adds a UI that may allow site admins to change desired functionality

In addition, the REAME for this module describes how a mail key can be set programmatically, so there is no actual need for the Mail System module.

In addition, Mail System apparently writes out PHP class files to the public files directory, which seems a bit dubious in terms of security.

Proposed resolution

Remove Mail System as a requirement, maybe just give a requirement warning if it's absent and mention it in docs.

Remaining tasks

write patch

User interface changes

none

API changes

none

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pwolanin created an issue. See original summary.

pwolanin’s picture

Issue summary: View changes
pwolanin’s picture

Status: Active » Needs review
FileSize
316 bytes

Quick 1st pass patch

pwolanin’s picture

Hmm, expect that will fail since it looks at though a theme setting is used also from mailsystem

pounard’s picture

For two reasons this should be done:

The only use Mimemail has for the mailsystem module is UI driven configuration, which is good for site builders, but not required for the rest of the world, and finding the theme for sending mails, hopefully I added the mimemail_theme variable to fallback on in case there's not the mailsystem module enabled.

pounard’s picture

Hum there's chances that tests won't pass because some seem to enable the mailsystem module.

pounard’s picture

pounard’s picture

Title: Remove Mail System as a hard dependency since it's not actually needed » Mail System dependency should be optional
pounard’s picture

New version that get rids of a PHP notice