After the recent security announcement went out as HTML email there was a bit of chatter. Here is how to make things change: - Security announcements and Drupal newsletters are sent using the simplenews module, development will happen there. - There is a decent HTML to text converter in project module. If there is a use for it in core I'd be happy to add it, but for now I'd like to see it put in an .inc file which defines the necessary function(s) if they haven't already. Then this .inc can be thrown in any contributed module that needs it. - The mime headers part of multipart messages isn't too bad to write. The part we would stumble on is the actual HTML, but we aren't doing anything too fancy and it seems that no one had issues with the quality of the markup (disclaimer: I only skimmed the complaints). -- Neil Drumm http://delocalizedham.com/
- There is a decent HTML to text converter in project module. If there is a use for it in core I'd be happy to add it, but for now I'd like to see it put in an .inc file which defines the necessary function(s) if they haven't already. Then this .inc can be thrown in any contributed module that needs it.
HTML to text is needed by any module that wants to send web content via email or SMS. i've seen custom code for this in notify, subscription, project, newsletter and organic groups modules ... moving this feature to core is best approach IMO
It would be helpful if we could get a summary of where development stands with regards to mail functionality of all sorts. I know it has been an active 6 months in this arena, but the work that's been done hasn't been publicized, and people who weren't involved in the development (like me) have no idea what is out there and what the best code to use is. 1. What happened to the initiative to make a mail.inc? 2. What are the best/newest modules that have major mail functions, like mailing lists, mailhandler, newsletter, subscription etc.? If we can generate a decent summary here, on-list, I'll do a write-up of the results on Drupal.org. -Robert
On Mar 14, 2006, at 9:57 PM, Robert Douglass wrote:
It would be helpful if we could get a summary of where development stands with regards to mail functionality of all sorts. I know it has been an active 6 months in this arena, but the work that's been done hasn't been publicized, and people who weren't involved in the development (like me) have no idea what is out there and what the best code to use is.
1. What happened to the initiative to make a mail.inc? 2. What are the best/newest modules that have major mail functions, like mailing lists, mailhandler, newsletter, subscription etc.?
Happy to help. After 4.7 ships ;-) Kieran
If we can generate a decent summary here, on-list, I'll do a write- up of the results on Drupal.org.
-Robert
Robert Douglass wrote:
It would be helpful if we could get a summary of where development stands with regards to mail functionality of all sorts. I know it has been an active 6 months in this arena, but the work that's been done hasn't been publicized, and people who weren't involved in the development (like me) have no idea what is out there and what the best code to use is.
1. What happened to the initiative to make a mail.inc?
Got put on hold since Dries didn't want it for 4.7. This includes a html2txt converter, btw, and Dries already agreed it could be in core.
2. What are the best/newest modules that have major mail functions, like mailing lists, mailhandler, newsletter, subscription etc.?
No idea, really. Allie has been working on send.module and mimemail.module. The latter took some ideas from my mail.module. The idea is that all modules should send mail through it. I think we could add it to core for 4.8. Cheers, Gerhard
Subscriptions has a mail-with-cron solution in testing right now. tdobes is queuing it up with his other testing on his 4.7 environment. It's an internally based solution that stores node changes in a table until cron runs, and then routes them through the same logic as before. -- Dan Ziemecki On 3/15/06, Gerhard Killesreiter <gerhard@killesreiter.de> wrote:
Robert Douglass wrote:
It would be helpful if we could get a summary of where development stands with regards to mail functionality of all sorts. I know it has been an active 6 months in this arena, but the work that's been done hasn't been publicized, and people who weren't involved in the development (like me) have no idea what is out there and what the best code to use is.
1. What happened to the initiative to make a mail.inc?
Got put on hold since Dries didn't want it for 4.7. This includes a html2txt converter, btw, and Dries already agreed it could be in core.
2. What are the best/newest modules that have major mail functions, like mailing lists, mailhandler, newsletter, subscription etc.?
No idea, really. Allie has been working on send.module and mimemail.module. The latter took some ideas from my mail.module. The idea is that all modules should send mail through it. I think we could add it to core for 4.8.
Cheers, Gerhard
Op woensdag 15 maart 2006 06:31, schreef Moshe Weitzman:
HTML to text is needed by any module that wants to send web content via email or SMS. i've seen custom code for this in notify, subscription, project, newsletter and organic groups modules ... moving this feature to core is best approach IMO
Moshe is correct. This is a function set that is used very often, having it in core is a good idea. Maybe its a good plan (AFTER 4.7 ;) ) to set up a forum thread or email discussion to get a list of requirements and functional description. If we have agreed upon what APIs are required, which ones are nice but not used often. Waht parameters we should be able to change. etc., we will IMO be able to get something done. :) Bèr
On 15 Mar 2006, at 00:59, Neil Drumm wrote:
After the recent security announcement went out as HTML email there was a bit of chatter. Here is how to make things change:
- Security announcements and Drupal newsletters are sent using the simplenews module, development will happen there.
Simplenews has basic html2txt functionality. As far as I know, these functions are the same as in the development version of Gerhard's mail.inc. All previous newsletters and security announcements were sent this way (created as an html node and converted to text by simplenews). Why were yesterday's announcements sent as html? Was there a problem? I agree that we should move to using multipart/alternate instead of html only. Dries Knapen
On 15 Mar 2006, at 13:27, Dries Knapen wrote:
Simplenews has basic html2txt functionality. As far as I know, these functions are the same as in the development version of Gerhard's mail.inc.
Both of which used the code from my html2txt module which I've since substantially improved: http://drupal.org/project/html2txt I'd suggest adding that to core as an include file. Best regards, Robert Castelo Services Manager Cortext Communications http://www.cortextcommunications.com
Hi Guys, On Tue, 2006-03-14 at 15:59 -0800, Neil Drumm wrote:
After the recent security announcement went out as HTML email there was a bit of chatter. Here is how to make things change:
- Security announcements and Drupal newsletters are sent using the simplenews module, development will happen there.
- There is a decent HTML to text converter in project module. If there is a use for it in core I'd be happy to add it, but for now I'd like to see it put in an .inc file which defines the necessary function(s) if they haven't already. Then this .inc can be thrown in any contributed module that needs it.
- The mime headers part of multipart messages isn't too bad to write. The part we would stumble on is the actual HTML, but we aren't doing anything too fancy and it seems that no one had issues with the quality of the markup (disclaimer: I only skimmed the complaints).
The mime-mail module already does an excellent job at both of these things (and is already used as a back-end by several other modules).
From http://drupal.org/node/37911 This is a Mime Mail component module (for use by other modules). * It permits users to recieve HTML email and can be used by other modules. The mail functionality accepts an HTML message body, mime-endcodes it and sends it. * If the HTML has embedded graphics, these graphics are MIME-encoded and included as a message attachment. * Adopts your site's style by automatically including your theme's stylesheet files in a themeable HTML message format * If the recipient's preference is available and they prefer plaintext, the HTML will be converted to plain text and sent as-is. Otherwise, the email will be sent in themeable HTML with a plaintext alternative.
I think it would be great if we could get this (or a version of it) in core :) - Owen
participants (10)
-
Bèr Kessels -
Dan Ziemecki -
Dries Knapen -
Gerhard Killesreiter -
Kieran Lal -
Moshe Weitzman -
Neil Drumm -
Owen Barton -
Robert Castelo -
Robert Douglass