Topic created by incoming email, doesn't include most of the content

Support
1

I’m using a webform to collect some content. On submit, it sends an email that creates a topic, but only shows the first couple of lines of the message. The rest is there under the email link, but not in the Topic. I’m working with older women, and they don’t want to have to be told to click on another thing, when the point of this is to have all that type of content in one place.

I’ve tried all of the settings that seem relevant (don’t trim is the only thing I’ve found that seems like it should make a difference) with no change.

image
image1808×1174 186 KB

The part of the message displayed ends at Submitted values are: (basically it’s showing the text I don’t care about, but none of what I want displayed to users).

I’ve tried changing and removing those intro lines, with the same result.

Is this the way incoming email messages are supposed to work?

2

Okay - I switched the output of the email to text from HTML and it shows up. :frowning: but at least it’s displayed. I will look for a setting that allows HTML in incoming email.

3

There is such a setting, so I’ve tried it but there’s no change in the display.

4

The body is likely being detected as part of another email, quote, or something similar like that.

The best way to get a detailed answer here is to post a full raw email here (email addresses, etc. can be redacted, but test data is fine) along with post source for what Discourse decided to generate from that email.

Is the email being sent by the end users’ system or by yours on form submission?

5

It’s coming from a webform on my site that also saves the data in our CiviCRM. I checked the HTML and it’s splitting at the <section …>.

<html>
<head>
  <title>Subscriber New homeowner listing</title>
</head>
<body>
<p>Submitted on Mon, 04/13/2026 - 14:05</p>
<p>Submitted by: Subscriber</p>
<p>Submitted values are:</p>
**`<section class="js-form-item form-item js-form-wrapper form-wrapper webform-section" id="homeowners_questions--civicrm_1_contact_1_fieldset_fieldset">`**
        <h2 class="webform-section-title">Homeowner listing info</h2>
    <div class="webform-section-wrapper">
                  <b>Username</b><br>test subscriber<br><br>

I’ve consulted the volunteer who is doing this manually, and it’s about 90% better than what she’s doing now (it comes from the correct username, and makes the Topic/title, so she can just copy/paste the rest of the body from the email. It’s a few extra seconds of effort, but only happens a few times a week at most, so we’ll just have to watch for new Topics in that Category.

6

It might be simpler and more maintainable if instead of going webform → crm → html → email → email parser → post you go webform → crm → markdown → post via API.

Specifically, you could create a markdown template using the form data and use an API key to submit a post via API. You’d have very consistent results.

7

Thank you for the suggestion. It’s good to know there are options.

As a volunteer without access to either platform backend, I’m going with the most “built-in” method currently available by clicking on configuration settings. The webform is sending other emails and the selections there are text or HTML so that’s what I’ve got to work with. :slight_smile: