Closed vttranlina closed 4 months ago
Bug of repo https://github.com/apache/james-mime4j But I can not create new issue on that repository. Please move it if creation the issue here is incorrect
We can keep the isues here.
And what if... To: invalid
how would mime4j parse this?
The current use case would be to: [{name: null, email: "invalid"}]
.
So this corner case is not a blocker.
I think have a confusion here. Currently, Tmail does not approve invalid email addresses when saving a draft However, this behavior is expected to change after addressing ticket https://github.com/linagora/james-project/issues/5075
Then. Tmail will save a draft email, that has to: [{name: null, email: "invalid"}]
And because of this issue, when "Email/get" the draft email, it will appear as:
"to": [
{
"name": "name1",
"email": "invalid1"
},
{
"email": ">"
}
]
Ok
Not a critical blocker, just a very very nice to have.
How about by the time we get this fixed we filter in the JMAP stack the lone >
email? Not clean but it would do as a temporary fix...
james-mime4j pr: https://github.com/apache/james-mime4j/pull/102
When parsing the rawField
To: name1 <invalid1>
by AddressListFieldLenientImpl The AddressList return incorrectActual: size 2 ("invalid", ">")
Expected: size 1 ("invalid")