I looked through a lot of the questions but I can't seem to find anything related to this. I basically have a bunch of invoices which is represented by invoice hashes: 36 character hex with dashes, i.e. (notice the 3D in the 2nd block)
F1111CBD-13D1-11F1-11C2-A1111E111111
So this hash gets emailed out to customers so they can click the link and get their invoices. For some reason, customers who are getting the link with an invoicehash that contains the characters "3D" are getting errors. We found that "3D" was getting truncated when reviewing the emails forwarded to us by the customers. We have our own copies of each and every single email sent out and our emails show the correct hash. I even checked the SQL email logs and see that hashes with "3D" was definitely sent out correctly to the applicable customers.
Does anyone have a clue why "3D" is specifically filtered out from customer emails? My first thought is that the customer's email service has a filter that specifically targets "3D". Maybe their incoming server has some setting that filters it out.
More info:
- the 36 character hash is generated on table insert as a uniqueidentifier type with a default value of "newid()"
- a cursor grabs the hash all applicable invoices monthly. The hash is set to a variable that is varchar(100) so there is more than enough to take in a 36 character hash (plus this does not happen to invoice hashes that do NOT have "3D" in it...maybe nvarchar is needed for compatibility?)
- this randomly started happening (don't believe we had issues with this before)
Any help on this would be appreciated. Thanks in advance!