Hello all, I have looked at several topics (e.g., 1) and I don’t see that this need has been addressed previously. I am using some forums as direct mailing list replacements. For example, we have a mailing list that we used for some users asking all others if they would like their shifts (e.g., “Shift tomorrow for trade”). In GNU/Mailman, the correct setting would be to set “reply to sender”. I have clearly articulated in a tutorial how I think people should use the mailing list, but it’s clear that’s not happening. People are still sending to the forum, and because all users are by default “watching”, everybody receives messages that used to be sent privately. Instead of making life better, at this point the lists have made things at best net neutral, though worse for most. So, what I would like is for either: The messages in this category to automatically get sent as PMs; or Messages to come back via email to that individual user. Is this already possible? If not, any thoughts on how I could make it happen? I think for my purposes, this might be a killer for our users if we can’t resolve it..

[imagem] erlend_sh: Is that really how “normal mailing lists” work? Google Groups, easily the most popular mailing list platform in existence, does not appear to work this way. By default, my reply will be to the mailing list address and noone else. I just took a look at a few lists I’m on. Of about ~ 15 google groups, all of them have reply-to-list as their default (not sure that reply-to-sender is an option). Of about ~ 15 GNU/Mailman lists, all of them had reply-to-individual as default. I don’t have enough yahoo group subscriptions to make any statements about them. So perhaps it’s a philosophical choice that the different list providers make on behalf of list admins?

I’ve been playing around with the code, and arrived at this: In line 148 of lib/email/message_builder.rb, this would result in what I would like to do: if allow_reply_by_email? result['X-Discourse-Reply-Key'] = reply_key result['Reply-To'] = "test1@test.com" result['CC'] = reply_by_email_address else result['Reply-To'] = from_value end However, now I’m trying to figure out what the ‘sender email address’ variable would be in ruby world..

After lots of support and help from others, I have finally sorted out the rawest form of how to accomplish this. It is presented below as a patch: diff --git a/lib/email/message_builder.rb b/lib/email/message_builder.rb index f099b11..2a69249 100644 --- a/lib/email/message_builder.rb +++ b/lib/email/message_builder.rb @@ -147,7 +147,15 @@ module Email if allow_reply_by_email? result['X-Discourse-Reply-Key'] = reply_key - result['Reply-To'] = reply_by_email_address + if @opts[:private_reply] == true + result['Reply-To'] = reply_by_email_address + else + p = Post.find_by_id @opts[:post_id] + result['Reply-To'] = "#{p.user.name} " + result['CC'] = reply_by_email_address + end else result['Reply-To'] = from_value end This patch does the following: By default, users who hit ‘reply to’ will only reply to the sending user. For a user to post a public message to the mailing list / topic, they would have to hit ‘reply all’. It does not act on private messages. Note: This exposes the sender’s email address to all recipients. Unfortunately, I will implement this patch for our use-case effective immediately. However, I recognize that it would be amazing if the following were true: A per-category or site-wide option to select this A per-category or site-wide option to expose email addresses. Integration into personal messages rather than via email directly. When the responding user hits ‘reply all’ and selects both the list and the sending user, the sending user should not receive an email notification from Discourse. Currently, two messages - one via email and one via Discourse - will arrive. I hope the patch as it is helps somebody. If I could make it a per-category option, would you guys consider folding it into the master branch, @erlend_sh?

Maybe @zogstrip can chime in here since he’s been our :e-mail: guy extraordinaire as of late. If at all possible, I’d much rather have this tweak done in the form of a plugin. No other reply-by-email solution I’ve ever tried works this way. Your use case is valid, but incredibly rare.

[imagem] erlend_sh: If at all possible, I’d much rather have this tweak done in the form of a plugin. No other reply-by-email solution I’ve ever tried works this way. Your use case is valid, but incredibly rare. It’s less a question of desire than ability. I’ve searched for documentation about how to develop a plugin as a Rails novice, but had no luck. Obviously I would really prefer not to have to patch core every time.. Could you point me to a simple plugin I could manipulate / use as a base to do this?

[imagem] tarek: I’ve searched for documentation about how to develop a plugin as a Rails novice, but had no luck [imagem] Beginner’s Guide to Creating Discourse Plugins Part of our important work with Rails Girls in 2014 and 2015 was not just to mentor and encourage new developers, but also evolve Discourse into a platform that’s generally friendly and easy for developers to build on.

Hello all, I am trying to understand how to properly make this plugin. I’m currently stuck in my plugin.rb, as it seems that I cannot properly replace the MessageBuilder class. Here is the current plugin.rb (and the repo in general): plugin.rb master # name: replyto-individual plugin # about: A plugin that allows exposure of the sender's email address for functionality # similar to GNU/Mailman's Reply_Goes_To_List = Poster # version: 0.1 # authors: Tarek Loubani # license: aGPLv3 PLUGIN_NAME ||= "replyto-individual".freeze after_initialize do Email::MessageBuilder.class_eval do attr_reader :template_args ALLOW_REPLY_BY_EMAIL_HEADER = 'X-Discourse-Allow-Reply-By-Email'.freeze def build_args args = { to: @to, subject: subject, This file has been truncated. show original I have tried to understand how to do this by reading a few topics I could find in searches, but as of yet no luck: Beginner’s Guide to Creating Discourse Plugins 1 2 3 4 5 6 Basic plugin template Plugin Tutorial #1 - How to manipulate the text in the composer? Plugin Tutorial #3 - How to add a button after every posts? When I run the plugin, I get the following, which I suspect reflects that the class is not properly replaced: /vagrant/lib/email/message_builder.rb:20: warning: already initialized constant Email::MessageBuilder::REPLY_TO_AUTO_GENERATED_HEADER_KEY /vagrant/lib/email/message_builder.rb:20: warning: previous definition of REPLY_TO_AUTO_GENERATED_HEADER_KEY was here /vagrant/lib/email/message_builder.rb:21: warning: already initialized constant Email::MessageBuilder::REPLY_TO_AUTO_GENERATED_HEADER_VALUE /vagrant/lib/email/message_builder.rb:21: warning: previous definition of REPLY_TO_AUTO_GENERATED_HEADER_VALUE was here Any thoughts or advice?

[imagem] tarek: Any thoughts or advice? I replaced a class method so it might need to be done a bit differently (i.e. instance_eval instead of class_eval ?) * and yes, the names are counter-intuitive [imagem] Kinder Guardian - let New members message Staff Plugin Without this plugin, New members can only contact Staff by email or by replying to their Welcome message This plugin allows them to message Staff from either the Staff members User Card, or the Staff members Profile page. It does not let them send messages to non-Staff members. display the Flag icon or it’s option to send a message from its modal. let them send messages from their own Profile page. let them send messages if the site has them disabled https://github.com/Mittineague/discour…

Take a look at this for how I have reopened the Email::Sender class: plugin.rb master # name: discourse-twilio-notifications # about: sends sms notifications through twilio from Discourse # version: 0.1 # authors: scossar # A proof-of-concept for integrating twilio sms notifications with Discourse. # This plugin assumes that user.custom_fields["enable_sms"] and user.custom_fields["mobile"] # have been set through SSO. enabled_site_setting :twilio_notifications_enabled gem 'twilio-ruby', '4.9.0' after_initialize do Email::Sender.class_eval do def account_sid SiteSetting.twilio_notifications_account_sid end def auth_token This file has been truncated. show original https://rubymonk.com/learning/books/5-metaprogramming-ruby-ascent/chapters/24-eval/lessons/68-class-eval

Simon, that seems to definitely change things, but now the class is totally unusable with the error: Jobs::HandledExceptionWrapper: Wrapped NameError: uninitialized constant MessageBuilder I’ve posted a Gist of the changes I made to mimic yours here: https://gist.github.com/tareko/c94b7dd8a24e9845617e157ec0899e43 Definitely this seems like a step forward, since at least I’m manipulating the class, but not sure what I’m doing wrong here. I will also try to understand @Mittineague 's solution and see if I can implement it.

Allow reply-to individual instead of topic/forum (mailing list feature)

Product Support

codinghorror (Jeff Atwood) 6 Junho , 2016 20:55 23

Discourse Needs help resources and documentation

Tópico		Respostas	Vistas
Confusion between Reply To and Reply List in email responses UX	45	7502	13 Outubro , 2021
Email Notification recipients unclear when PM is sent to multiple users Feature email	38	12044	4 Maio , 2018
Migrating from Google Groups Migration	15	7827	16 Fevereiro , 2015
Reply by email - additional addresses Product Support	28	3324	19 Agosto , 2019
Replacing Mailing lists: Email-In Feature	66	18068	4 Outubro , 2014

Allow reply-to individual instead of topic/forum (mailing list feature)

Related topics