You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we found a issue with the way fider handels encoding in mail headers. In our testings we used the Invitations feature to test this.
Steps to reproduce:
Send invitaion to User
Use non-ASCII characters in the "Subject" field
Send the invite
After sending a test invite with the subject "Test ä ö ü", i've checked the mail on our test server (Postfix/Dovecot/rspamd/amavis). Here is an example:
Which is fine, as it gets displayed correctly when viewed directly on the mail server. However this is not according to spec. Subjects with non-ASCII characters should be encoded as described in RFC 1342 e.g. =?charset?encoding?encoded-text?=
Although fider uses SMTPUTF8 if the server prodivdes it this is not an option for most people. SMTPUTF8 is not supported in some software, and can lead to issues with downstream SMTP Servers that don't support it.
Is there a way you could implement a Subject encoding like this as described here:
Hi,
we found a issue with the way fider handels encoding in mail headers. In our testings we used the Invitations feature to test this.
Steps to reproduce:
After sending a test invite with the subject "Test ä ö ü", i've checked the mail on our test server (Postfix/Dovecot/rspamd/amavis). Here is an example:
Which is fine, as it gets displayed correctly when viewed directly on the mail server. However this is not according to spec. Subjects with non-ASCII characters should be encoded as described in RFC 1342 e.g. =?charset?encoding?encoded-text?=
Although fider uses SMTPUTF8 if the server prodivdes it this is not an option for most people. SMTPUTF8 is not supported in some software, and can lead to issues with downstream SMTP Servers that don't support it.
Is there a way you could implement a Subject encoding like this as described here:
Some further information can be found here.
Any thoughts?
The text was updated successfully, but these errors were encountered: