Comments (5)
Email threading is not easy, but needs to be dealt with
http://www.jwz.org/doc/threading.html
from api.
I strongly recommend not using the algorithm as described in your link.
In step 5, Jamie Zawinski groups emails without reference headers by subject, which would again cause lavab/web#552 and #129.
He complains that Netscape 4.0 removed this step, which was exactly the right thing to do.
An alternative suggestion:
If you use the algorithm, remove step 5.
Use a disjoint-set data structure to group together everything which references each other, then sort by references order, by date or by incoming server time stamp.
The time stamp for sorting the threads in the inbox could be the latest time an email in it was sent.
Clients which have their time messed up and send emails on 1.1.1970 would have their emails sorted to the end of the inbox, where they are likely never seen by the user. One could protect against this by using the incoming server time stamp instead.
from api.
I implemented my personal adaptation of that algorithm, I only need to tune it a little bit, as I accidentally introduced some bugs back then.
from api.
You mean the one in https://github.com/lavab/mailer/blob/master/handler/handler.go?
from api.
Fixed in b0bcf39
@mlooz I think that for now it's good enough - mailer doesn't use the "Date" field anyways, which might cause issues. We'll bring it up later, when we'll be less loaded.
from api.
Related Issues (20)
- API doesn't seem to support q-encoding for subjects
- Remodel the responses
- Need endpoint that will simply mirror requested headers HOT 3
- Sent email is absent in inbox when getting reply from Lavaboom HOT 4
- SMTP library crash HOT 3
- Apply Jorge's example query to other select-intensive RethinkDB queries
- Port images to a more lightweight base
- NSQ is just queueing tons of messages HOT 1
- Replace db package with something more reasonable HOT 1
- Optimize API startup time HOT 1
- Reimplement onboarding emails using webhooks
- keys.list doesn't support styled names with dots
- Threads.list dies with "Internal error (code TH/LI/01)" HOT 1
- /GET files with filtering by tags returns `Internal error (code FI/LI/03)` HOT 2
- /GET threads and /GET threads/[id] randomly returns empty meta and body
- Determine third parameter of the utils.NewError by the error code
- pgp/mime thread.name='Encrypted thread' while first email.name contains actual email subject in plain/text
- Light mailer and api refactoring
- The whole codebase's license should be changed to Affero GPL HOT 2
- Invite Email
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from api.