Closed Massedil closed 1 year ago
X-CRYPTO is a field used by Kmail/Kolab to specify if the contact wants emails encrypted or not. Because SnappyMail supports PGP the fields are added when editing the contact in SnappyMail.
Removing the PHOTO property should not happen, so i wonder why Sabre or SnappyMail removes it. I will try to test this.
PHOTO problem is caused by v3 vs v4.
v3 = PHOTO;ENCODING=b;TYPE=jpeg:…
v4 = PHOTO:data:image/jpeg;base64,…
When SnappyMail received a remote vCard, it didn't check the VERSION and PHOTO properly. Then vCard is put back as VERSION = 4.0 which causes an invalid PHOTO value.
I've added a check and a converter to v4
Thanks !
Is it fixed for all V3 property with your update or it is possible it happens for another property?
Can the V3 to V4 conversion have an impact on other clients?
By the way, is it possible to display the contact photo on the contact list and on emails if present?
If clients don't support v4 then it would have issues with the PHOTO value and fail. Since v4 is already available for a very long time, i doubt other clients didn't update.
Eventually the image (also BIMI) might get added at some places.
Describe the bug Snappymail remove photos of my contacts when synchronizing.
To Reproduce Steps to reproduce the behavior:
Snappymail update nearly all contacts it knows (why ?), but it destroys information :
Before :
After :
New field :
X-CRYPTO
,Updated field :
VERSION
PRODID
REV
Lost data :
PHOTO;ENCODING
Expected behavior
X-CRYPTO
?)Please complete the following information: