When no signatures are created, leave out the signature block

I am experiencing a critical issue with Front's automatic signature injection that significantly impacts our professional communication and workflow efficiency.

Problem Description: When composing new messages, Front automatically adds a default signature block (either a user-defined signature or the 'Sent from Front' default), even if no signature is explicitly selected or defined by the user in Front.

Conflict with External Signature Management: This behavior directly conflicts with our server-side email signature management solution (e.g., Exclaimer, CodeTwo, WiseStamp). These solutions append our official, professionally formatted company signature on the server-side, after the message leaves Front.

Negative Impact: The result is that every outbound email from Front often includes two signatures: Front's automatically injected one, followed by our official, server-appended signature. This creates a highly unprofessional appearance and undermines our brand's consistency.

Inefficient Workaround: The only current workaround is to manually click the 'X' to remove Front's signature block from every single composed message. This is not only a repetitive and time-wasting task but is also highly error-prone, as users frequently forget, leading to unintended double signatures.

Feature Request: We urgently need an option to disable Front's automatic signature injection entirely, either globally for all accounts/channels or at a granular level per inbox/channel. This would allow us to rely solely on our server-side signature management solution, ensuring professional, consistent communication without manual intervention.

This feature is crucial for any organization using professional email signature solutions and is essential for maintaining a high standard of external communication.