-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: .eml email file #1363
Comments
### What problem does this PR solve? add support for eml file parser #1363 ### Type of change - [x] New Feature (non-breaking change which adds functionality) --------- Co-authored-by: Zhedong Cen <cenzhedong2@126.com> Co-authored-by: Kevin Hu <kevinhu.sh@gmail.com>
fixed. |
Thanks for your reply ! |
The API and server share the same data source. |
Thanks for your reply ! Even if it's not the same conversation id, one on ragflow and one newly created conversation id through the API call interface . I'll follow up on that one. I'm looking forward to feeding my voice to ragflow, I wonder when it will be available . I also hope that chat module can support translation into multiple languages for retrieval. Is there any plan to launch it . Thank you very much! |
### What problem does this PR solve? #1363 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Demo is upgraded. |
### What problem does this PR solve? add support for eml file parser infiniflow#1363 ### Type of change - [x] New Feature (non-breaking change which adds functionality) --------- Co-authored-by: Zhedong Cen <cenzhedong2@126.com> Co-authored-by: Kevin Hu <kevinhu.sh@gmail.com>
### What problem does this PR solve? infiniflow#1363 ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue)
Is there an existing issue for the same feature request?
Is your feature request related to a problem?
No response
Describe the feature you'd like
can you add the support for .eml files
Describe implementation you've considered
a parser for email files
Documentation, adoption, use case
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: