Mechiel Lukkien 37de8de1c5
fix incorrect error about bare cr/lf when sending a message over smtp
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!
2024-02-16 20:20:58 +01:00
..
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00
2024-02-10 17:55:56 +01:00
2023-01-30 14:27:06 +01:00
2023-01-30 14:27:06 +01:00