Hi Arun,
>> - proper handling of attachments in multipart messages. If a multipart >> message contains an attachment, mumi tries to display it like any >> other multipart type. > > Is this about allowing attached patches to be downloaded? Is it > currently possible to download patches using mumi? It would be nice to > use mumi for my entire workflow, and not have to fallback to the old > debbugs web interface. This is now possible. I currently only decode attachments that are in base64 and quoted printable formats; all others are sent as is. > Also, is there any value in having a pure guile email parser instead of > using bindings to mailutils? I attempted a similar project, and for some > reason, I ended up writing an email parser from scratch using (ice-9 > peg). But, now that I see how you have used mailutils bindings, I am > unsure if writing an email parser from scratch was wise. However, if you > think it is worthwhile, I can contribute that code to mumi. I’m not using a lot of mailutils. I use the following procedures: - mu-address-get-email - mu-address-get-personal (problem: swallows non-ASCII characters) - mu-header-decode - mu-decoder-port Of all these only “mu-decoder-port” would be non-trivial to implement. It’s used to decode strings that are encoded as “quoted-printable”. It wouldn’t be too difficult to implement in pure Guile – I just wanted to save time. I’d be happy if your work on email parsers could end up in mumi and replace some of my own poor quality code :) -- Ricardo
