Hi again, There is https://github.com/perkeep/perkeep/issues/465 <https://github.com/perkeep/perkeep/issues/465> but seems to have gone stale/died.
Ok, I will wait for Brad to pitch in if he had any more thoughts or if he still thinks it would be good to have someone/me to write up a suggestion/doc (as mentioned in the issue). /Viktor > On 8 May 2018, at 15:41, Mathieu Lonjaret <[email protected]> wrote: > > Hi all, > > an e-mail (gmail in particular) importer has of course been in our > minds for a while, so if enough people are interested that might help > moving it closer to the top of the TODO list. But I think Brad had > specific ideas about it so it's probably better to coordinate with him > to get it started. Do we have an open issue about it? > > > On 7 May 2018 at 14:40, Viktor Ogeman <[email protected]> wrote: >> James, Bob, >> >> Thanks for those links, look interesting both of them - and I will go >> through them more in detail - if there is support for trying to get >> something included into “core” perkeep. >> >> >> >> On 7 May 2018, at 22:16, James Hillyerd <[email protected]> wrote: >> >> 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. >> >> >> -- >> 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. -- 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.
