-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReceivedHeader: incorrectly parse #183
Comments
Aah, it's because there's a section called 'id' so it starts a sub-consumer at that point. Should be an easy enough fix to the regex here:
In most cases the spaces before/after aren't optional except for 'from' which I think is required and always comes at the start but would have to refresh my memory on it. So it might make more sense to have a 'FromReceivedConsumer' that uses \s*(from)\s+ and the rest have \s+(token)\s+. Lastly some better testing needs to be added. Thanks for reporting, @mariuszkrzaczkowski |
some solution ?? it blocks my job |
Feel free to submit a PR with a fix. |
I have no idea how to fix it and where |
if I knew it, I would have created PR a long time ago |
I tried what you wrote but it didn't work |
Fixed in 2.2.0. |
I found a strange bug, the problem is probably in the word 'id'
My code:
Example 1 (working properly)
Code:
Response:
Example 1 (bug)
Code:
Response:
difference:
mail.uiii.ac.idd
VSmail.uiii.ac.id
The text was updated successfully, but these errors were encountered: