-
Notifications
You must be signed in to change notification settings - Fork 86
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
Error: invalid bare carriage return or newline. #129
Comments
That's an error you are stilling getting for new incoming deliveries? Or is that coming from mox parsing the message from disk? It is still possible that mox rejects messages, but I'm thinking we should accept such messages if they are incoming for final delivery, and only keep rejecting them for messages that still need to be delivered (over submission). The bug was that the smtpserver was adding an extra \r to the message file. Reparse only reads the message as stored on disk, it doesn't fix it. Could you try removing that \r from the on-disk file yourself and running reparse again? If that works, we may need some subcommand or instructions to fix up these issues... |
Got this two days ago, after upgrading mox to v0.0.10-0.20240209102133-ee1db2dde705:
Had a quick go at it but it seams I am unable to locate it, will need to figure out the proper tooling, I welcome any suggestions. What about this error:
Thank you! |
Ok, I was able to fix the mails with Now Will be watching for new deliveries returning |
we weren't properly tracking the cr's and lf's when being strict about message lines when sending data. we are reading buffered data from a Reader. if that chunk happens to start with a newline, we weren't looking at the previously written data, which could be a cr. instead, in that case, we would always claim the cr/lf wasn't correct. the new test case triggered the behaviour before having the fix. should solve issue #129 by x8x, thanks for the report!
I think I found the bug that was causing error message Still good to keep this issue open for the reparse and "\r\r\n" issue. |
v0.0.10 is coming soon. It has instructions for fixing the "\r\r\n" issue. Closing this issue, but feel free to reopen if needed. |
After upgrading to 0.9 I got a few mail delivery errors like this:
Thinking this commit was a related fix, I upgraded to version
v0.0.10-0.20240209102133-ee1db2dde705
, but am still getting such delivery errors../mox reparse
returns these errors:How to fix stored messages reported by
reparse
and are there still known issues related to the smtp error above?Thank you!
The text was updated successfully, but these errors were encountered: