check mail encoding and format if charset is not specified #21575
+25
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please add a test case |
|
Test added for case handled in fix |
trasher
reviewed
Oct 22, 2025
AdrienClairembault
approved these changes
Oct 23, 2025
|
(Lint and tests are failing) |
trasher
reviewed
Oct 24, 2025
trasher
approved these changes
Oct 28, 2025
AdrienClairembault
approved these changes
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a new check in case charset is not specified as in the .eml file shared in GLPI 11.0.1 : Collector mail error charset #21540 also add a new test .eml file with same configuration.