Filtering system causing problems with upstream modules

Hi,

It's probably a bug in the print module.. However, I do need the mimemail's module maintainer to tell me what the problem is and what's the best way to solve it.. Keep in mind that the print module prepares a MIME email to be sent out, so that may explain why the mimemail prevents a good delivery..

João

Hi,

The way I see it, the print module is sending out a nice MIME e-mail perfectly at this moment, using Drupal e-mail capabilities. The presence of the mimemail module (and specifically, the option to use mime mail for all messages) seems to break this capability.

Taking into account the above, it's either a bug in the print module that only occurs in the presence of the mimemail module, or it's a bug in the mimemail module that is incapable of detecting and dealing with already MIMEd messages.

I don't see waht can be done inside the print module, anyway...

João

I've researched this a little more and the problem seems to be the input filters.. If the input filter is set to PHP, the original HTML is allowed through without problems and the e-mail is correctly rendered.

However, if any of the more restrictive filters is used, the e-mail gets mangled in different levels..

My question is: why is this module applying the input filters to it's output?? There's nothing to be gained in filtering the outgoing mails.. That's a task that should be left to the upstream modules. I see no reason that a message (with whatever content) should be filtered, as it's trivial to send messages with whatever contents to the recipient (like using a mail program in their machine).

The 'Use mime mail for all messages' and the use of the filters are just a source of issues for other modules which create e-mail from inside Drupal. At least disable the filters for the 'all messages' sources..

João

I just checked in a change which should correct this issue. Before performing the call to check_markup(), I'm first checking the message header being provided through drupal_mail to make sure I'm dealing with a text/plain message. If I'm not, then we skip the check_markup() call.

This fix will be in the next development build. If you could test and provide feedback it'd be greatly appreciated!

Thanks,

Jer Davis
Advantage Labs, Inc.

Hi,

Thanks for the change. I have just tested it and the problem no longer occurs with the new version.

I guess this can be closed now.

João