Am 30.08.2015 21:06, schrieb Michael Heydekamp:
Am 30.08.2015 18:42, schrieb A.L.E.C:
On 08/30/2015 05:09 PM, Michael Heydekamp wrote:
See subject. All of a sudden (= since today) dashes are prepended to a HTML signature...?! Two when composing a new message, three upon replying.
My signatures do contain dashes already, so I'd prefer if they wouldn't be touched in any way (as before).
Should be fixed now.
Can't confirm yet, as I have to wait for our next git-pull cron job. But thanks a lot anyway. :)
This I can confirm now, thanks again.
As to this issue:
On another issue (but most likely related): I activated the new (and very useful!) option "always, except when replying to plain text" as to when HTML messages should be composed, but: When replying to a plain text message, no sig at all is injected into the message - at least not, when it's declared as a HTML sig.
Shouldn't we need two sigs (text and HTML) then...?
Now a (converted from HTML to text) sig is injected, but it's not usable:
-- MICHAEL HEYDEKAMP
T +49 211 xxxxxxx F +49 211 xxxxxxx M +49 172 xxxxxxxxxxxxxx@xxxxxx.de http://www.xxxxxx.de
Please see attached how the original HTML sig does look like (edited, of course). It's a table, as I want to have a correct left-alignment of the numbers.
I really think that two sigs (HTML and text) would be the best and only way to REALLY solve this (also because that I could replace the logo with a company name in plain text). For now, I have reverted my setting to "always" (HTML). Which I don't like too much, but it's still the least worse solution currently.
Anyway, thanks for working on this issue at all.
Cheers,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
