No offense taken good Sir ofc.
I would argue tho that http-use-htx works as intended, dropping capitalization.
It’s the Outlook that doesn’t conform to that, granted 11 years old client…
No offense intended either…
Obviously, it is Outlook that causes the error through erratic behavior, while http-use-htx does what it is supposed to. But that doesn’t matter at the end of the day if both are incompatible and I can’t turn off http-use-htx (anymore).
But luckily there is the option to correct via “h1-case-adjust”.
Ahh you’ve upgraded to 2.1.+.
And I do agree, in the end it falls on to us to fix it, not matter who’s at “fault”…
Big cheers on your post tho. Gave me a workaround (that I could have just Googled but too lazy/busy to do) that will work till the 2019 upgrade…
1 Like