From: Ricardo Wurmus <rekado@elephly.net> To: Arun Isaac <arunisaac@systemreboot.net> Cc: guile-email@systemreboot.net Subject: Re: [guile-email] parse-email-headers returns just “fields” Date: Thu, 23 Apr 2020 08:35:03 +0200 Message-ID: <875zdqlnfs.fsf@elephly.net> (raw) In-Reply-To: <cu7lfmnvvp7.fsf@systemreboot.net> Arun Isaac <arunisaac@systemreboot.net> writes: >> In some cases the emails don’t seem to have a >> content-transfer-encoding header, > > This is not a problem. RFC2045 specifies that > "Content-Transfer-Encoding: 7BIT" should be assumed if the > Content-Transfer-Encoding header is not present. guile-email implements > this recommendation. Hmm, I still get this error when the first line of an email to be parsed is something like From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 22 11:26:37 2020 The error message is Body decoding failed. Unknown encoding #f So it fails to parse the headers correctly, ends up not finding the header specifying the encoding, and then aborts body decoding. >> * I sometimes need to discard the first two lines of the raw email to >> get the headers to be fully parsed > > Your attachment is an mbox, not a raw email. Perhaps you are treating it > as a raw email and that's why you have to chop off the first line? And, > I'm guessing your other problems are also related to this. Oh, this may be. However, I still get the same problem when I don’t manually discard the first line if it looks like this: From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 22 11:26:37 2020 I’m splitting the debbugs log file containing the messages and collect all lines between the delimiters. I then do (parse-email (and=> (call-with-input-string contents mbox->emails) first)) But this will only work if I drop the first line from “contents”. -- Ricardo
next prev parent reply index Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-21 12:24 Ricardo Wurmus 2020-04-23 1:26 ` Arun Isaac 2020-04-23 1:26 ` Arun Isaac 2020-04-23 6:35 ` Ricardo Wurmus [this message] 2020-04-23 11:31 ` Arun Isaac 2020-04-23 11:31 ` Arun Isaac 2020-04-23 14:40 ` Ricardo Wurmus 2020-04-23 21:54 ` Arun Isaac 2020-04-23 21:54 ` Arun Isaac
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=875zdqlnfs.fsf@elephly.net \ --to=rekado@elephly.net \ --cc=arunisaac@systemreboot.net \ --cc=guile-email@systemreboot.net \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
guile-email discussion Archives are clonable: git clone --mirror http://lists.systemreboot.net/guile-email/0 guile-email/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 guile-email guile-email/ http://lists.systemreboot.net/guile-email \ guile-email@systemreboot.net public-inbox-index guile-email Example config snippet for mirrors AGPL code for this site: git clone https://public-inbox.org/public-inbox.git