Skip to content

Conversation

@mrbrdo
Copy link

@mrbrdo mrbrdo commented Oct 30, 2025

I added the option to specify a local file path instead of uploading a file for mbox/eml/pst ingestion. I only added the capability to the API and not on the frontend, but that could be easily added.

Seems to be working, I am still waiting after several hours to finish on my 13GB google takeout mbox file. (it seems the process is so intensive that I am basically unable to access the server even by SSH, but I can see in the hypervisor it is doing something, especially disk i/o).

Please note the code was mostly generated by AI (Claude/opencode), I also checked it roughly, although I am no typescript expert.

Here is an example API call by curl to use it (find Bearer token from some request in the browser):

curl -X POST http://localhost:3000/api/v1/ingestion-sources \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_JWT_TOKEN" \
  -d '{
    "name": "My Mbox Import",
    "provider": "mbox_import",
    "providerConfig": {
      "type": "mbox_import",
      "localFilePath": "/path/to/emails.mbox"
    }
  }'

Here is a precompiled version of MboxConnector.js that one could overwrite in the docker container (+restart), if someone wanted to quickly test it (v0.4.0): https://gist.github.com/mrbrdo/a5061ddbe3502820da206e6180b95f33

Related to #120

@github-actions
Copy link

github-actions bot commented Oct 30, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@mrbrdo
Copy link
Author

mrbrdo commented Oct 30, 2025

I have read the CLA Document and I hereby sign the CLA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant