I believe this is implemented specifically on each mail server and client, so there is no standard for it: See https://www.chilkatsoft.com/p/p_471.asp for details
You can set these headers, but there's no guarantee the client or receiving server will take note of them
Thanks for your comments, and you are correct in assessing this is for a specific use case (I'm migrating data between 2 structures and want to make sure the exported JSON is EXACTLY the same).
For the first point, I really only care that all values in the source are also in the target. If I wanted to be thorough, I woudl run the compare in both directions, but since I'm expecting that the target will contain additional properties, I only need a 1 way compare)
For the second point, I actually define the ordering of exporting of arrays explicitly, so I would expect a like for like compare. For other cases, additional logic would need to be added, as you pointed out
For the last point, this should return a mismatch, which is good enough for my use case, but again, might not be ideal for other use cases
That would be an easy adjustment to make. In my use case I'm also interested in knowing which fields are mismatching, and there may be multiple mismatches (hopefully not) per export
Log in or create a new account to continue