pilichoumao opened a new issue, #6921: URL: https://github.com/apache/rocketmq-dashboard/issues/6921
### Search before asking Searched existing issues/PRs for `parseRecipients` and recipient comments, including #6663 and its merged implementation. This is a remaining comment-syntax case, rather than the quoted-display-name case fixed there. ### Environment `rocketmq-studio` at c34535db0819d02f68e50a856cb3d2614f0dc5dd; Linux ECS, JDK 21, Jakarta Mail. ### Reproduction Configure email recipients as: ```text [email protected] (Ops, on call), [email protected] ``` Dispatch an EMAIL alert. The splitter in `NotificationOutboxService.parseRecipients` splits the comma inside the comment, producing an invalid fragment; delivery enters `RETRY_WAIT` and the mail sender is not called. The same happens for `Ops (East; on call) <[email protected]>; [email protected]` and nested comments containing a comma. Expected: send to `[email protected]` and `[email protected]`, preserving the existing strict address validation and legacy semicolon separators. RFC 5322 ยง3.2.2 permits nested comments and quoted pairs: https://www.rfc-editor.org/rfc/rfc5322#section-3.2.2. ### Investigation A temporary production-dispatch probe on the above SHA reproduced three failures; four normal/invalid-input controls passed. An isolated prototype that splits only outside quoted strings and comments passed all seven cases and the existing 46 notification tests. Repositories, mapper and mail sender were mocked; no real SMTP or database was contacted. Full Maven/build checks remain for the formal patch. Proposed scope: comment-aware splitting plus dispatch regressions, preserving #6663's quoted names, escapes and semicolon compatibility. AI assistance was used for investigation and verification. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
