guile-email discussion
 help / color / Atom feed
From: Arun Isaac <>
To: Ricardo Wurmus <>
Subject: Re: [guile-email] parse-email-headers returns just “fields”
Date: Thu, 23 Apr 2020 17:01:50 +0530
Message-ID: <> (raw)
Message-ID: <20200423113150.jC9tZDOO_z8_DWiDAPbItN1fDW_41ue4UV5yz6mttcU@z> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 837 bytes --]

> Hmm, I still get this error when the first line of an email to be
> parsed is something like
>     From Wed Apr 22 11:26:37 2020

Did the parse-email snippet I sent in my previous mail work on the
attached mbox you sent earlier? Could you send me any other mboxes you
are having trouble with? I'm unable to reproduce your problem, and
having a copy of the problematic mboxes would help very much.

>   (parse-email
>    (and=> (call-with-input-string contents mbox->emails) first))

Also, it isn't a good idea to handle emails or mboxes as strings (the
`contents' variable). They should be handled as bytevectors. Perhaps it
doesn't matter here, but just saying.

And, just out of curiosity, if there's no sensitive information in it,
could you share a copy of a debbugs log file?

Thank you!

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[-- Attachment #2: Type: text/plain, Size: 110 bytes --]

guile-email mailing list

  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
2020-04-23 11:31     ` Arun Isaac [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 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/ \
	public-inbox-index guile-email

Example config snippet for mirrors

AGPL code for this site: git clone