Could you clarify how the incoming mail processor determines the break point? I understand that it is probably a complex algorithm, given the diversity of email formats, but perhaps there are some rules of thumb? Because intuitively I often have a hard time understanding why an email was rendered the way it was. In this case, for example, I might expect the separating line (--------) to be interpreted as the beginning of an email footer (although it would be better if only up to, say, four dashes are interpreted in this way, but not more), but that’s clearly not what happened.
So what did happen? Let’s see.
- The first line with the link to the web version was ignored, which makes sense. Indeed, it suggests that there is some advanced processing going on.
- The second line was included in the post though the Horde screenshot doesn’t really help here because it looks like it replaces all images with their alt text (“U.S. Food & Drug Administration Header”). Based on the actual post, This second line of the email was an image with an underlying link and that seems to have been accurately rendered in the post.
- Everything after that was interpreted as a signature/previous email.
Unfortunately, the Horde view of the mail doesn’t allow us to see why this is so (you need to look at the raw email body, which you find in your incoming emails in the admin section), but my guess is that it has something to do with tables. Either the header was in a different table than the rest of the email and discourse only looks at the first table (which might make sense) or, if the email consists of a single table, discourse may only be looking at the first row (which would seem more problematic).