On version 1.4.3. Some emails I'm able to parse and import, but others give the below error.

This might be similar to #30, although the error is a bit different.

Add an option for how many mails will be fetch in each command action.
This can be used in tweaking setup.

I have already finished this, just need some more testing and will initiate a pull request.

• Added a setting for Fetch Interval
• Created a timer to poll/fetch on that interval.

Hello,

Thanks for this plugin, I just installed it and it works great !

I have a question about the attachments, is there a possibility to link them in the template in order to find the attachment of the email directly from the note?

Use Case

Writing email in Markdown causes a problem as Turndown does not convert well.

Proposal

Make the Turndown call a Settings option so Emails could be written in pure markdown and then just incorporated into Obsidan.

Example

Here is the rendering in Obsidian of a simple markdown file sent as email.

This is the original email source. If pure markdown is used in the email, Turndown doesn't seem to recognize it.

Love it. Seems to be working fine in my vault. Complicated emails with lots of images aren't always handled perfectly, but that's not unexpected. The one thing I haven't found how to do is to change how the file is named. Currently it is using ${Subject} as the name, and I'd like it to use ${Date} - ${Subject} instead. Is there a way for me to do that?

The plugin fetches emails, it works.

But tags or body are not correct.

Here is what I put in my template:

${Body|raw} 

${Body} 

${Body|htmlmd} 

${Body|text} 

${Labels}

${Labels|tag}

${Labels|link}

And here is the result:

${Body|raw} 

 

${Body|htmlmd} 


${Body|text} 

[[obsidian]], [[INBOX]]

${Labels|tag}

${Labels|link}

What did I miss?

What I did

I sent an email with a PDF attachment.

What did I expect

• The attachment file to placed in the vault "somewhere"....perhaps based on the vault settings for Attachment locations. That would be better than another separate attachment settings specific to the google-mail plugin.
• A link placed in the newly created Note to the Attachment.

What happened

• Attachmed PDF file did not seem to be transferred. I searched the vault, and also did a find on the vault hierarchy, and the file was not found.

Workaround

• No known workaround

• amount setting
• not to change label option

I installed this maybe a month or two ago, and tested it successfully. I noticed recently I'm getting the following error when starting up Obsidian:

BRAT: thingnotok/obsidian-google-mail/
The release is not complete and cannot be download. main.js is missing from the Release

I have followed all the instructions, after I click the prompts in the OAuth screen I get a notification that I've been authenticated, and Obsidian displays a notification that I've been "logined" (should be *logged in). But nothing happens after that. This is on version 1.4.2. I haven't tested it on the latest stable version.

What I Did

Forward an email, and put some text at the front of it.

What I expect

Text of entire email, my content and the forwarded portion should be included in the resulting note.

Actual Results

The pre-pended text is not visible anywhere. I have tested this with and without a template.

Here is the screenshot of the email:

and here is the resulting screenshot in Obsidian after fetching the mail (No Google-Mail Templates used).

Sometimes I have to logout and log back in due to a token error.

When I log out, the Labels I have set are not saved, and rather than just logging back in. Other settings are saved (e.g. Mail Folder).

(using file)

• Benefits
  • much more simpler compared to paste three fields from credential
• Drawback
  • Need to access file outside vault
    • additional access permission
    • need fs module

Maybe let users directly paste json content is a better idea? open file and copy content is much easier than key in the path of file.

Use a template frame works for all notes should be useful to organize the emails.
Email fields can be in ${Email:Field} format

Possible format for the mail:

title:: ${Email:Subject} %% This line will be the filename.
tag::  ${Email:Labels|link} #captured. %% link or tag
from:: ${Email:From}
date:: ${Email:Date}

---

${Email:Body|format} %% plaintext or HTML2MD

Just realized that the fetch timer should be torn down on logout and not created if not logged in to Gmail.

I will fix this over the weekend.

After some trial and error, everything worked fine through setup. I have some labels applied, I have a template and my folders set up. I can do the plugin setup in Obsidian and it recognizes the labels. But when I go to actually fetch the mail, nothing is retrieved. No idea what my error might be.
Error log in the developer console attached.

Hello,

I try to install your plugin but I can't. I already use https://github.com/YukiGasai/obsidian-google-calendar from @YukiGasai and it works fine. I created all the stuff in Google API part.

With your plugin , when I click on the "Continue" button (after checking permissions), the page can't go further. The JSON field is ok.

How can I give you more details to help me?

This is awesome!! Thank you!

At the risk of being greedy, there are a couple other features that would be really cool as this matures. I know these are mostly outside the scope (e.g. require file munging and parsing) but could be some cool features.

• Post processing hook. Even if this was just a script. So for example, you could allow users to pipe PDF attachments through an OCR engine / indexer
• Delete on fetch (this is destructive, I know, but I am using a dummy Gmail account which I will most likely never log into interactively)
• Allow for user defined labels, not just the fixed set
• Auto-filing in the vault. for example, maybe specify a Vault folder in the subject line like Evernote does with @Notebook
• Auto tagging using tags in the subject line

I'm unable to get ${X-Received} to render. I was trying to use it to get the date and time from so I could use that to rename the file (I want to start the filename with 'yyyymmdd_hhMMss'). If you're diving into the code anyway, would it be possible to make available a ${DateTime} variable that provides the date/time in a common format (something predictable like 'YYYY-MM-DDTHH:mm:ssZ' or an option for multiple common formats)?