Commas in Display Name causing parsing errors

Khurrum

If someone has a display name that has commas eg:

`Lastname, Firstname (INFO)[MoreINFO]

then it seems like Sogo has a parsing error where Sent items shows up as
INFO=2E0 <=?utf-8?q?Lastname=2C_Firstname_@MISSING_DOMAIN>, because it assumes that Lastname, is an email address. That is it’s unquoted so it’s parsing it incorrectly.

And then the recipient gets the email, but there is a phantom to address called lastname@domain.com in the to field in addition to the intended recipient.

I am using the latest version of mailcow.

Has anyone encountered this bug before? I am able to repeat this with many different accounts on the same mailcow server and many different recipients all who have their Display Name in the format: ``Lastname, Firstname (INFO)[MoreINFO]`

Is there a work around or a fix for this? Or shall I create a bug report?

Thanks,
K

DocFraggle

Khurrum To be honest, I never saw this specific display name format before… but as this seems to be a SoGo problem you should raise an issue with them, mail is just uses SoGo

ETNyx

Well, Khurrum how much did you test it? Coma is not the problem, get rid of () and [] and you will see that coma itself is just fine,…

Khurrum

DocFraggle Will do, thanks. In the mean time I have added an outbound filter that adds quotes around the names so at least the phantom email address is gone

ETNyx Thanks, yes, comma is fine after removing the square brackets. Removing just the square brackets makes the parenthesis disappear but the display name renders fine and there is no phantom email.

thanks, all

I’ll post to sogo mailing lists.