You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can scan for the header boundary as we receive the emails in the DATA command state, saving the position of the header boundary for later processing, and/or parse as we go along. At present, the data is re-scanned at the end of the transaction.
Additionally, once we have the header, we could could have a MIME aware reader, that can read in chunks and is aware about content boundaries, getting us closer to addressing issue #84
The text was updated successfully, but these errors were encountered:
Hi, I have some problem with headers. Should I start new Issue?
DEBU[0001] Client sent: DATA
DEBU[0001] Writing response to client: 54 Enter message, ending with '.' on a line by itself
ERRO[0001] parse headers error error=EOF
On Fri., 8 Mar. 2019, 02:48 Serhii Chaplia, ***@***.***> wrote:
DEBU[0001] Client sent: DATA DEBU[0001] Writing response to client: 54
Enter message, ending with '.' on a line by itself ERRO[0001] parse headers
error error=EOF
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#130 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAnmP4T1kQsduZ2Oz4jwvbuB6YS-3-Qqks5vUTTMgaJpZM4ZyS78>
.
We can scan for the header boundary as we receive the emails in the DATA command state, saving the position of the header boundary for later processing, and/or parse as we go along. At present, the data is re-scanned at the end of the transaction.
Additionally, once we have the header, we could could have a MIME aware reader, that can read in chunks and is aware about content boundaries, getting us closer to addressing issue #84
The text was updated successfully, but these errors were encountered: