Comments on: Solving the Email Signature Problem for Exchange Mailbox Users

By: Tony Redmond

Tony Redmond — Mon, 24 Apr 2023 12:19:02 +0000

In reply to Dennis.

From the Code Two people:

The workaround is explained here: https://www.codetwo.com/kb/configuring-tnef-conversion-options/#powershell. You’re right about the cause of the problem and it is required to change TNEF conversion options for remote domains to fix it. The key is to do that for all domains Dennis is using to send emails – that might be the missing piece.

Code Two say that you can contact them if you’re still having problems…

By: Dennis

Dennis — Mon, 24 Apr 2023 09:23:34 +0000

I have found out that the routing of emails via systems like Codetwo and Exclaimer for email signatures breaks Exchange message recalls when trying to recall emails from an internal Exchange online recipient. I tried the solution supplied by CodeTwo, which does not work.

By: Mahmoud Adel

Mahmoud Adel — Thu, 12 May 2022 14:02:09 +0000

is there any news on this topic?

By: Göran Alfvén

Göran Alfvén — Sun, 25 Oct 2020 08:57:53 +0000

I’m just another person walking this planet frustrated with the fact that e-mail signatures aren’t easily managed centrally for all possible devices.
It’s 2020.
I mean – it’s t w e n t y t w e n t y …

By: Marc

Marc — Mon, 08 Jun 2020 14:40:03 +0000

In reply to zubair. Not sure if you ever got this sorted, but you need to remove the users ability to create their own signature. It sounds like they are adding their own in OWA on top of your exchange signature.

By: boe

boe — Fri, 22 May 2020 19:48:45 +0000

I’m looking for this capability right now – I set up everyone’s OWA signature without realizing it wouldn’t work in outlook

By: zubair

zubair — Sat, 19 Jan 2019 17:22:28 +0000

i assign the signature for my company user using office 365 exchange.that signature works when he sends email from outlook desktop application. but when user uses outlook web. there are two email signatures under email.
the issue is i want same signature while user send email from outlook desktop application or outlook web application,
can any body help me to resolve this problem,waiting for your kind response.
thank you.

By: Brian Christensen

Brian Christensen — Fri, 02 Nov 2018 18:07:34 +0000

Great article. However, none of those 3rd party solutions in the article have pricing for a single user, and I believe there are many single users of Office 365 (such as myself). That is just one more reason why it would be great if signatures *could* eventually be stored on the Exchange server natively. Also, the link for the specific idea on User Voice in the article seems to be broken?…..it just says “This idea is awaiting moderator approval.” I’d love to vote for that idea, if I can find the idea on User Voice! Thanks!

By: Rafael Meyer

Rafael Meyer — Wed, 24 Oct 2018 15:08:47 +0000

Having exchange online for a small business makes a lot of sense, but not being able to manage signatures, if not through a disclaimer workaround which does not propagate to Outlook or OWA is a disappointment.

If he external vendors had a reasonable pricing for just signatures I would use them, but as of now it’s not something worth considering.

By: Frank

Frank — Wed, 09 May 2018 03:26:23 +0000

Some of my clients cant afford Exclaimer of Code2. The price sometimes defeats the savings in migrating them to Exchange Online not to mention is another vendor, app documentation and support skills to bring onboard.