Users are discussing issues with email signature stripping in Discourse when posting via email. Manfred_Bayer-Lemerz reports that signatures aren’t being removed, prompting a conversation about the lack of a universal standard for signature detection. zogstrip explains that stripping is automated but challenging due to varied formats. gerhard clarifies that Discourse uses HTML detection for signatures and recommends the -- standard for plain text. Paul_King notes persistent issues with Outlook 2016 signatures, including images and formatting problems, and questions whether the email_reply_trimmer library can be customized. omarfilip confirms that some signatures, especially from Outlook, evade the trimmer. Cozdabuch and pacharanero suggest a manual list of signatures to be stripped, while nathank and Jonathan5 debate the correct signature delimiter. outofthebox asks about trimming automated web form messages, and riking suggests using -- to mimic a signature. jeff_y seeks alternatives to horizontal rules that don’t trigger trimming. markcoley proposes a moderator-driven system to identify and hide signatures across posts. nathank and sam emphasize the need for real-world examples to improve the system, but note privacy concerns with sharing them publicly.
Signature stripping is done automatically. Since there’s no standard, it’s hard to get it right for all the billions signature formats out there. Can you PM me the raw email so that I can have a look?
For our group it would be helpful to understand what the preferred signature format is. For example, we could let folks know that anything after ten dashes ---------- would be parsed as a signature. We could then be in contact with our most difficult signature offenders (those that include images as part of their signature) and ask them to prepend their signature line with ten dashes. I realize this method wouldn’t work for everyone, but it would be very helpful for our smaller group (300 members).
Or possibly include something in the Admin that allowed us to specify our own local signature formats that would be stripped from incoming emails.
Usenet signature cut lines are standardized. How many people get it right (follow suit) in email is another matter. The quoted text in the first post does appear to be a standard Usenet cut line: hyphen-hyphen-space.
A solution that I’ve mused about is that there couple be a use setting that included the text to remove. People could then paste their sig in there and have it removed when they posted.
Its still rather fiddly,but easier than machine learning.
Not sure, if this behaviour really belongs to this change: Emails are not accepted because of a invalid main body or a body, that is too short. In fact, the body is long enough according to the rules (min. 20 characters) and I cannot see a reason, why it should not be accepted. Maybe we strip out too much of the content?
Discourse uses HTML emails by default and it automatically detects and strips email signatures of the most popular email clients. So, this should work out of the box as long as your users send HTML emails and use their email client to insert signatures.
For plain text emails it’s always a good idea to start signatures with the de facto standard of two dashes and a space.
Hi @gerhard, for the life of me I can’t seem to get automatic signature trimming to work. Emails tested just have standard Microsoft Outlook type signatures containing images and/or text appended at the bottom of any new email sent.
Does it happen on all incoming emails? The email signature trimmer works well on the majority of mine, but a few random ones get through, along with a persistent one sent from X-Mailer: Microsoft Outlook 16.0.