Shameless plug warning! If you do end up implementing an IMAP importer, and want to parse MIME encoded mail (plain text vs HTML, attachments, etc), please take a look at my library: https://github.com/jhillyerd/enmime
MIME message quality varies significantly in the wild, and you will find that Go's built in decoding is aimed at HTTP multipart forms, which tend to be very consistent. On Mon, May 7, 2018 at 12:52 PM Viktor <[email protected]> wrote: > Hi, > > I now have a pk server up and running (thanks for the help the other day) > and working - importing many of my artefacts. In this process I realise > that much of the stuff I care about is stored in different mailboxes (gmail > chief among them). > > As I have a lot of experience in golang, and the perkeep homepage suggests > importers as a good place to start for new contributors I thought I could > give this a try. > > Would there be interest in this if I spend time to flesh out a more > detailed proposal that I could subsequenctly implement? > > My initial thought would be not to make something golang specific but > using IMAP such that it could be re-used for other providers as well. There > are some additional challenges related to what to do with some metadata, > attached files etc. - but again, if there is interest I would as I said > suggest to write up a more detailed proposal to be discussed before coding > to much. > > /Viktor > > -- > You received this message because you are subscribed to the Google Groups > "Perkeep" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
