A signature defect that three mailboxes agreed was not there

A CRM email signature was rendering its logos centred instead of left aligned, and the usual way of checking said it was fine. What makes it worth writing up is not the fix, it is that the check itself was blind. The same message looks correct in Outlook whichever account it arrives through, so opening […]

In this series · Part 10 of 27

1Dynamics 365 CRM: API integration + change-control repo2Dynamics 365 CRM: Last Contact Engagement tracking on Accounts3Turning a sales-intelligence export into a clean CRM data model4Dynamics 365 CRM: contacts inherit their company’s website, and emails timestamp by send time5Your SEO health now lives as a dashboard inside the CRM6Contact form duplicate detection now reads the request, not just the address7Marketing list members now show engagement and account fit8Campaign responses now create leads behind a confirmation step9Three CRM automations passed their tests without running the code that had just changed10A signature defect that three mailboxes agreed was not there11Why a corrected email signature kept sending the old one12A read-only CRM endpoint for scoring outside the desktop13Choosing what runs the AI layer in the CRM sales process14Asking whether a partner is involved, instead of inferring it15An email step in the sales process can now be excused, not only sent16The rehearsal that guards every process change had been failing silently17A one to one email from a lead left the engagement record blank18Two local dependencies, and only one was obvious19Filing a generated document to the record automatically20One meeting that served two process steps, recorded as two21A setting that stored correctly, read back correctly, and was never in force22Generating a product catalogue from one canonical file23Three date fields that existed on every row, and had never once been written24Unused, unreferenced, and still not safe to delete25A measure that could not record early26A sales automation that runs as itself, not as an administrator27A stage change that was refused, and reported as a success

On this page

Free Revenue Lifecycle Assessment

Connect with Marissa Wright to receive a free Revenue Lifecycle Assessment Report on your own business.

Book a consult →

A CRM email signature was rendering its logos centred instead of left aligned, and the usual way of checking said it was fine. What makes it worth writing up is not the fix, it is that the check itself was blind. The same message looks correct in Outlook whichever account it arrives through, so opening it in a second mailbox would have confirmed the wrong answer twice.

  • The defect was invisible in the one place it was being checked. The editor that composes these emails wraps every inserted image in a block that carries two separate instructions to centre it. Gmail, Apple Mail and mobile webmail all obey those instructions. Outlook renders with a different engine that ignores both, so it quietly left aligns and shows a clean result. An earlier review had raised the centring and been told it could be ignored, on the grounds that it was not showing up in Outlook. That reasoning used the one client blind to the fault as the judge of whether a fault existed.
  • Patching the stored record did not work, three times, and the record was not the problem. The signature is held in three separate fields. Each was corrected and verified, and two subsequent sends still arrived centred with no trace of the correction. In the same message, a content card inserted by a small script came through correctly aligned. That contrast was the whole diagnosis: inserting a signature makes the editor redraw the images and reapply its own default, discarding whatever was stored, while the script writes the entire body as one value and the editor accepts it unchanged.
  • So the fix had to move to the only write that survives. The card script already rebuilds the whole body each time it runs, so it now normalises alignment in the same pass. The trade is stated rather than hidden: it straightens every image in the body, not only the two logos, and it only runs when a card is inserted. Both are acceptable here and both are recorded, because an undocumented side effect becomes a defect the moment somebody wants a centred image.
  • One behaviour explained three separate symptoms, and a finding that was true elsewhere was false here. Paragraph spacing was collapsing, the logos were centred, and a gap above the card kept vanishing. All three came from the same normalising pass: it zeroes margins on paragraphs, collapses empty lines, and rewraps bare images. Earlier work had established that a plain paragraph keeps the mail client's own spacing, which is correct on the path where the text is written directly into the record and wrong on the path that goes through the editor. Same markup, opposite result, because different software touches it.