Jump to:
| Project: | Listhandler |
| Version: | master |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Hi,
I understand that this module is aimed at working with mailhandler to integrate a forum with a mailinglist (eg mailman).
However, mailhandler can also be used to add other node-types (and comments) than forum posts.
Is the 6.x version of Listhandler (HEAD) able to match this functionality to allow - for example - nodes of type 'event' and comments on those nodes to integrate with a mailinglist the same way as nodes of type 'forum post' and their comments?
One thing I can see that could be a requirement is giving all of our custom node-type a specific Taxonomy ID (just like what's used to organize forum topics). Because, just like the ideal set up for forum/mailinglist integration, we don't want our users to have to add the node ID as an email command... but rather have this automatic and invisible to the user.
So my questions are - 1. Is this scenario possible? and 2. Do you have any advice for setting this up?
I'm happy to help test and contribute as much as I'm able...
Thanks :)
Scott
Comments
#1
Listhandler's main aim is to send out an email when a node is submitted on a site.
At the moment that node has to be a forum posting, but it could be expanded with two cavets:
If it is incoming email traffic only then Mailhandler will adequetly meet your needs. If it's outgoing as well then you will need another module - maybe Listhandler, maybe something else - to send the outgoing emails.
Regards.
P.
#2
@philipnet: Hi... this was a while ago, but I'm still interested. I see the last commit was the same day as your reply.
Those two caveats seem manageable (for now):
1. Ignoring publishing status isn't ideal but this feature would be more ideal than having to use a forum for all mailing list integration. Do you have any tips about what the difficulty is in checking the published status before posting to the list?
2. It makes sense that we'd need to add the correct Taxonomy term to correspond with each list when creating nodes.
I also have a few more Qs:
* Would we still be equally able to add email/mailing list replies as comments on the correct node?
* Would new posts to the list (not replies) still create a new node (rather than a comment on an existing one)?
* If so, how would drupal know which content-type to create? Assuming this would be a new configuration which could be selected per list?
* Overall, what do you think would be involved in expanding Listhandler to work with other content-types? Does it make sense to split the job into separate tasks?
I may be able to help with this stuff, but pointers from you (since no one knows the code better than you) would make my ability to contribute much more realistic.
BTW, I have more time than usual the rest of this week (today & tomorrow) & over this weekend - if you happen to be around :)
#3
@philipnet: actually... about one thing i said above:
I think this is already sorted out right? The default TID is configured by Listhandler per list, unless literally overridden with mailhandler commands in the email. That's my understanding anyway.
Also, if other content-types are used instead of only forum posts... we're not necessarily restricted to a single TID (forums are strict Taxonomy hierarchies... but other content-types can have multiple terms per node). This could allow the same node to go to multiple lists - which would be a huge bonus for announcements (keeping all comments in one place etc).
Here's a thought about how this might work:
* Listhandler continues to provide default information about mailing-list posts to Mailhandler (default TID etc) per list.
* Listhandler continues to send new Drupal node content to the specified mailing-lists
-- But now the same Drupal post could be sent to multiple mailing lists (perhaps global content-type defaults that are overridden by per-node settings if users have appropriate override permission?).
* Listhandler continues to differentiate mailing-list email replies from new emails (non-replies) and handles them accordingly.
-- New emails would use the specified content-type configured per mailing list, and be assigned the appropriate Taxonomy term.
-- Reply emails would continue to appear as comments and be sent to all lists whose terms are assigned to the node
-- comments from users one one list (who are not a member of another list) gets sent to all associated lists, and authorship can be handled the same as it is now (anonymous, from the site etc).
What do you think?
#4
Change title to make the valid support request a little clearer.