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
in 1.46.4 (maybe also before), an email address written into quotes becomes tappable including the quotes.
tapping, the email address including the quotes is set as address to the core. the quotes in the alert are part of the address, not to surround the placeholder:
even if " can be a valid characters of the local part (never seen such an address), the top-level-domain de" is definitely invalid.
interestingly, messages can still be sent, despite of the wrong address - either core or some relays are graceful here - maybe accidentally and also buggy? -, but we should not depend on that.
filing the issue here as it is unclear if it is message-parser or sth. else and how to fix. android/ios do not have the issue.
The text was updated successfully, but these errors were encountered:
r10s
changed the title
quoted email address is parsed to greedy and is wrong by that
quoted email address is parsed too greedy and is wrong by that
Jun 15, 2024
another case is trailing dots like reach me at [email protected].... or not... your choice..., there the email parsing is too greedy and returns: [email protected]... (last dot is correctly ignored but the extra dots before that not)
in 1.46.4 (maybe also before), an email address written into quotes becomes tappable including the quotes.
tapping, the email address including the quotes is set as address to the core. the quotes in the alert are part of the address, not to surround the placeholder:
even if
"
can be a valid characters of the local part (never seen such an address), the top-level-domainde"
is definitely invalid.interestingly, messages can still be sent, despite of the wrong address - either core or some relays are graceful here - maybe accidentally and also buggy? -, but we should not depend on that.
filing the issue here as it is unclear if it is message-parser or sth. else and how to fix. android/ios do not have the issue.
The text was updated successfully, but these errors were encountered: