![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
signature separator missing on Reply and Forward
I have signature set for an account and in "Composition & Addressing" settings I have "start my reply above the quote" and "place my signature bellow my reply (above the quote)" set.
When I start to write a new message, editor window opens with following composition:
- one empty line on the top (here I start to write the text)
- signature separator "--"
- signature text
But when I start a "reply" or "forward" on existing message, editor window opens with following composition:
- signature text
- quote of the message being forwarded or replied
So on "reply" and "forward" scenario I'm missing the initial empty line followed by signature separator line. When I start to write a reply, it is conflicting with signature and also is formatted as signature, so I need to delete signature completely or adjust formatting manually.
This was not an issue with older Thunderbird release, this behavior is present only in recent versions. Any idea, how it could be fixed?
الحل المُختار
For reference, this is a link for this issue on extension Github, if anybody finds it here by searching Thunderbird questions:
https://github.com/jeevatkm/ReplyWith.../121
Read this answer in context 👍 0All Replies (3)
I cannot duplicate what you are seeing. Possibly, the sig text itself is part of the issue? Also, to my knowledge, the separator line is intended for initial composition, not for responses, so I'm not surprised that it is absent.
Thank you for testing.
I have now discovered that this issue is related to "ReplyWithHeader" extension I'm using. When I have disabled this extension, separator line on Reply is still missing, but initial "empty line" is now present, so when I start to write the reply, it is no more conflicting with signature.
Anyway, this behavior has changed with latest Thunderbird releases. But probably I have to report it to the extension author, maybe some update to comply with new Thunderbird interface is needed.
الحل المُختار
For reference, this is a link for this issue on extension Github, if anybody finds it here by searching Thunderbird questions: