The Mime Mail module should use the Mail System module

The idea is very good (I developed a similar helper module for testing), but the module lack's the support for messages with different $key in the message ID, which looks like this: {$module}_{$key}

However I don't want to make this a requirement and use it in the installation process. Mime Mail can work without it just fine and I think Mail System can do it's job without patching up Mime Mail.

Is your patch in #5 still valid?

IMO if we use the Mail System module we can (or more like should) remove the "Use as default mail system." option from the settings page and let just Mail System handle this question to avoid confusion.

As for 6.x I think this will not get into the 1.x branch, we are too close to a stable release now.

The 25,000 sites using your 6.x branch will lose the advantage of being able to use Mime Mail with SMTP Authentication Support.

You just said that the biggest advantage would be the comfort to maintain similar codes. Why would we lose the SMTP support if we don't backport this for 6.x? The Mime Mail API provides support for different mail engines and SMTP implements it just fine. I don't understand why would that happen?

Committed to the master branch. Thank you!

For now I leave this open for 6.x.

I am marking this as fixed for D7.

At this time there is no consensus about the support of Mail System on D6. We will see if there will be a 6.x-2.x branch of Mime Mail, but I would like to have a stable and final release for D6 and concentrate on D7.

However, pillarsdotnet thanks for your work on Mail System!

I strongly recommend to use "phpmailer.module" for Drupal 7. After lots of WTF's I decided to change from SMTP to PHPMailer and everything worked fine ad hoc.

At this time there is no consensus about the support of Mail System on D6.

Mail System for D6 is the de-facto solution for handing mail in a stable way; HTMLMail for d6 (this module's competitor) uses it. I'm reopening this as "Patch to be ported" and am working on an actual working patch. The D6 patch on comment #10 above is essentially a patch that takes the Drupal 7 version and poorly converts it to Drupal 6. There were many issues that I had to resolve and so I finally decided that that methodology is not sustainable, and I'd rather write a maintainable patch that adds Mail System support to the 6.x-1.x-dev branch, to maintain backward compatibility, instead of breaking a bunch of extra stuff and doubling or tripling my workload.

If desired this could be used as a basis for starting a 6.x-2.x branch, but I seriously doubt this will happen since d6 is losing momentum and official support in a matter of months.

Patch for D6 to integrate MailSystem with MimeMail.

Note: If you've copied mimemail-message.tpl.php to your own theme to override the default HTML, and your messages are showing up with the default template HTML, try out my patch on #2115299-6: Theme to render the emails settings does not apply anymore.

Whoops, forgot to include the new file mimemail.mail.inc in the patch!

Here is a fix.

Patch was prevented from applying due to the stuff in the info file added automatically by Drupal.org.

This should fix it.

Looks like the constant FILTER_DEFAULT_FORMAT is actually FILTER_FORMAT_DEFAULT.

It looks like the check_markup functionality will strip the message body and replace it with 'n/a' if the email is triggered by an anonymous user, if anonymous users are not allowed to use the input format specified by the mimemail_format variable.

To fix this we should run through check_markup but don't do the access check (pass the third parameter FALSE).

Also, unrelated it looks like the test functionality was switched over to ci.drupal.org and tests are currently failing, but has nothing to do with this code.

Fixed the patch in 28 it was empty. The interdiff-26-28.txt is still relevant.

Hi I was trying to send email with attachments and when tried to install Mime Mail I got the following error.
Mime Mail requires Drupal version 6.29 or higher. (Currently using Drupal 6.22)
there is any way to get those modules working without update my drupal version ??

Sorry, I doubt you'll find an answer to your question, but why would you *not* update to the latest version of Drupal 6? There are known security holes in older versions of Drupal.

Patches have already been committed to 8.x-1.x and 7.x-1.x for this issue.

Drupal 6 is no longer supported, for more than two years now.

Marking this D6 issue as won 't fix.