Email with "=====" characters is truncated unexpectedly.
We use a semi-Markdownish format when generating our plain text emails. Some of them included ====== style horizontal rules. When sent to Tender, everything after the first instance of '==' is truncated. I've noticed when looking at other problems that you seem to have a signature ripper that depends on '==' marking the start of the signature. While this may be a convention used by some, it is definitely not a standard that users reliably adhere to. How can I disable this processing, or at least access the original un-truncated email?
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by rick on 10 Jun, 2009 04:09 PM
Hmm there is no way. However, the
====processing should only work if there are 50 of them. Markdown doesn't support that does it? I'll look into changing it to something less offensive.2 Posted by PhallGuy on 10 Jun, 2009 06:35 PM
Hmm...there is a way. My emails were truncated. If there is a specific pattern that you're code is looking for we can modify ours to avoid it.
3 Posted by rick on 10 Jun, 2009 06:49 PM
I just did a test, and anything below
=================================================(count them, there 49) was not truncated. Try leaving a blank space between the// Add your reply above hereline. It truncates any full lines above that line to take as much of the standard email client garbage as possible. Do you have a tender URL so I can see the original email?4 Posted by PhallGuy on 15 Jun, 2009 04:52 PM
I've deleted the original emails since they contained personal information...I'll check to see if our template uses 50 in a row (if memory serves it might use something pretty close).
5 Posted by rick on 19 Jun, 2009 05:02 PM
I told you in another thread -- but I'm rewriting the parser so nothing gets hidden anymore. This thread was one of the factors that lead to that decision. Can't say when I'll have something ready, I have a feeling there will be a lot of edge cases to deal with. But they're all better than missing text.