You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you parse emails, you detect signature by -- (dash-dash-space). But, Gmail for some odd reason, adds asterisks before and after signature delimiter, you should, probably, support this as well. In raw email it looks like this: *-- *.
I realise this is a very old issue, but if this is still affecting folks I would like to hear more detail because I've been unable to reproduce this. As far as I can tell, Gmail does use the standard signature delimiter, -- \n.
I've reported this almost ten years ago, I no longer have access to the systems I used to run this on, and email accounts, so I cannot reproduce this problem.
Looks like gmail doesn't add -- automatically prior to signature, I have to add, and if I do, and mark text as bold, I will end up with *-- * instead.
Unable to verify with the original message, as I no longer have access to that email account. Well, it was almost ten years ago :)
I appreciate it was a long time ago! Thank you for replying.
Looks like gmail doesn't add -- automatically prior to signature, I have to add, and if I do, and mark text as bold, I will end up with *-- * instead.
When you say that you mark the text as bold, are you selecting the -- , too? Or just the text underneath the delimiter?
I just tried it by only marking the text under the delimiter as bold, and it correctly renders the raw email when sent.
--
*my sig*
If you are selecting the delimiter, too, then that is the cause and there is not much that can be done about that. The delimiter must be -- \n to conform to the standard used by all mail client/servers.
Obviously, in this case I'm selecting -- as bold to demonstrate the issue right now. I don't think I selected it in the past, but who knows what was happening. I'm surprised, Google doesn't automatically adds -- prior to signature right now, perhaps in the past they did.
My point is, no matter how smart the program is, there are always users, who manage to break things. While I don't think adding *-- * delimiter is correct thing to do, it might be a way to kill a class of failures of the module.
Activity
crimsonvspurple commentedon Apr 6, 2017
Any love for this?
peter-evans commentedon Feb 11, 2025
👋 @sashkab @crimsonvspurple
I realise this is a very old issue, but if this is still affecting folks I would like to hear more detail because I've been unable to reproduce this. As far as I can tell, Gmail does use the standard signature delimiter,
-- \n.sashkab commentedon Feb 11, 2025
I've reported this almost ten years ago, I no longer have access to the systems I used to run this on, and email accounts, so I cannot reproduce this problem.
Looks like gmail doesn't add
--automatically prior to signature, I have to add, and if I do, and mark text as bold, I will end up with*-- *instead.Unable to verify with the original message, as I no longer have access to that email account. Well, it was almost ten years ago :)
peter-evans commentedon Feb 11, 2025
I appreciate it was a long time ago! Thank you for replying.
When you say that you mark the text as bold, are you selecting the
--, too? Or just the text underneath the delimiter?I just tried it by only marking the text under the delimiter as bold, and it correctly renders the raw email when sent.
If you are selecting the delimiter, too, then that is the cause and there is not much that can be done about that. The delimiter must be
-- \nto conform to the standard used by all mail client/servers.sashkab commentedon Feb 12, 2025
Obviously, in this case I'm selecting
--as bold to demonstrate the issue right now. I don't think I selected it in the past, but who knows what was happening. I'm surprised, Google doesn't automatically adds--prior to signature right now, perhaps in the past they did.My point is, no matter how smart the program is, there are always users, who manage to break things. While I don't think adding
*-- *delimiter is correct thing to do, it might be a way to kill a class of failures of the module.