Hello Discourse, [imagem] Troubleshoot reply by email Self-Hosting If your Discourse does not have incoming email set up, see these topics: Set up reply by email with POP3 polling Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver information_source If you already have basic reply via email set up (which is common on hosting plans), and you want to add the ability to start a new topic via email, see this topic. Logging and Errors All incoming emails are logged and are visible in your admin panel at /admin/email/received.… Is there a preexisting code base out there for pushing emails to Discourse’s incoming email API? Thanks, Andrew

From the output of rake routes You can send a POST request to admin/email/handle_mail Here is the controller method from handle_mail: app/controllers/admin/email_controller.rb main # frozen_string_literal: true class Admin::EmailController < Admin::AdminController def index end def server_settings data = { delivery_method: delivery_method, settings: delivery_settings } render_json_dump(data) end def test params.require(:email_address) begin message = TestMailer.send_test(params[:email_address]) Email::Sender.new(message, :test_message).send render json: { sent_test_email_message: I18n.t("admin.email.sent_test") } rescue => e render json: { errors: [e.message] }, status: :unprocessable_entity end end def preview_digest params.require(:last_seen_at) params.require(:username) user = User.find_by_username(params[:username]) raise Discourse::InvalidParameters unless user renderer = Email::Renderer.new(UserNotifications.digest(user, since: params[:last_seen_at])) render json: MultiJson.dump(html_content: renderer.html, text_content: renderer.text) end def advanced_test params.require(:email) receiver = Email::Receiver.new(params["email"]) text, elided, format = receiver.select_body render json: success_json.merge!(text: text, elided: elided, format: format) end def send_digest params.require(:last_seen_at) params.require(:username) params.require(:email) user = User.find_by_username(params[:username]) raise Discourse::InvalidParameters unless user message, skip_reason = UserNotifications.public_send( :digest, user, since: params[:last_seen_at], skip_unsubscribe_links: true, ) if message message.to = params[:email] begin Email::Sender.new(message, :digest).send render json: success_json rescue => e render json: { errors: [e.message] }, status: :unprocessable_entity end else render json: { errors: skip_reason } end end # TODO (martin) Remove this in 3.7.0, this endpoint has been broken for years # and was used only in the public mail-receiver's fast rejection code, # which is removed in https://github.com/discourse/mail-receiver/pull/33 def smtp_should_reject render json: { reject: false } end def handle_mail deprecated_email_param_used = false if params[:email_encoded].present? email_raw = Base64.strict_decode64(params[:email_encoded]) elsif params[:email].present? deprecated_email_param_used = true email_raw = params[:email] else raise ActionController::ParameterMissing.new("email_encoded or email") end # If it isn't valid UTF-8, reinterpret as ISO-8859-1 so it can be serialized to JSON. email_raw = email_raw.dup.force_encoding("UTF-8") email_raw = email_raw.encode("UTF-8", "ISO-8859-1") if !email_raw.valid_encoding? Jobs.enqueue(:process_email, mail: email_raw, retry_on_rate_limit: true, source: "handle_mail") if deprecated_email_param_used warning = "warning: the email parameter is deprecated. all POST requests to this route should be sent with a base64 strict encoded email_encoded parameter instead. email has been received and is queued for processing" Discourse.deprecate(warning, drop_from: "3.3.0") render plain: warning else render plain: "email has been received and is queued for processing" end end private def delivery_settings action_mailer_settings.reject { |k, _| k == :password }.map { |k, v| { name: k, value: v } } end def delivery_method ActionMailer::Base.delivery_method end def action_mailer_settings ActionMailer::Base.public_send "#{delivery_method}_settings" end end

[imagem] sudoman: Is there a preexisting code base out there for pushing emails to Discourse’s incoming email API? [imagem] Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver Self-Hosting Discourse is all about enabling civilized discussion. While plenty of people like a web interface, e-mail is still the “hub” of many people’s online lives. That’s why sending e-mail is so important, and when you’re sending e-mail, you really want to be able to receive it, too. There are several reasons why: If e-mails “bounce” (they can’t be delivered for some reason), you need to know about that. Repeatedly sending e-mails that bounce will get your e-mails flagged as spam. Receiving e-ma…

For a non-technical user I’d need to understand the capabilities of inbound email via API: What I’ve done already: Inbound Emails via POP3 polling to main domain (not subdomain) Working inbound email via the postfix mail module but that only works for subdomain - in my case, xxx@community.eleoptics.com - which we can not use, need primary domain. Current Setup: Inbound email: G Suite Google “Groups” email address forwarding to free Gmail accounts (to avoid paying for a Gsuite account per email address). POP3 polling Outbound email: SMTP Relay Forwarding via GSuite validated by the IP of my Discourse server install on Google Cloud. This works but the free Gmail pop3 polling accounts is something I’d like to get away from. We plan to use the Google Cloud Platform Email API to handle email in-out ideally for larger scale deployment and service. Where is the documentation I could send my tech employees on how to get inbound email going directly to discourse? If that is already linked in the post above then thank you. Otherwise my guess is there needs to be a greater contextualized explanation. [imagem] blake: Here is the controller method from handle_mail : github.com discourse/discourse/blob/master/app/controllers/admin/email_controller.rb#L124 params.require(:email) user = User.find_by_username(params[:username]) message, skip_reason = UserNotifications.public_send(:digest, user, since: params[:last_seen_at] ) if message message.to = params[:email] begin Email::Sender.new(message, :digest).send render json: success_json rescue => e render json: { errors: [e.message] }, status: 422 end else render json: { errors: skip_reason } end end def smtp_should_reject

Código para receber e-mails via Discourse API

Suporte ao Produto

mpalmer (Matt Palmer) 10 Setembro , 2018 23:31 3

Tópico		Respostas	Vistas
No received mails in new Discourse installation Self-hosting	4	2048	9 Dezembro , 2019
Set up reply by email with POP3 polling Self-Hosting email , how-to	1	304267	2 Setembro , 2025
Receiving emails into Discourse messages. Can this be done? Product Support email	3	1262	23 Fevereiro , 2023
Simple email inbox for discourse Product Support email	17	1077	30 Outubro , 2023
Trying to set up reply by email: ActionController::RoutingError (No route matches [POST] "/admin/email/handle_mail") Self-hosting	3	2519	15 Junho , 2018

Código para receber e-mails via Discourse API

Related topics