Adam McKenna <[EMAIL PROTECTED]> writes: > I know I've said this before, but..
And I know I've answered it before, but why not revisit it as TMDA has changed lots since the last few times you've asked about this. > Why not just make pending a Maildir? Then one could operate on it > with any number of free mail readers. Initially I was opposed to this because I didn't want to be constrained by the Maildir spec. Since Maildir is designed for MUAs and TMDA isn't an MUA, I wasn't sure what conflicts would arise down the road. As it turns out, it probably would have sufficed. One thing I'm still concerned about is the interoperability with MUAs. For example, after a message is delivered, TMDA notes whether the message was 'confirmed' or 'released' with an entry in .delivered_cache. If we shifted to a Maildir, we'd need to retain this info in some manner. The obvious way would be to append a Maildir "info" flag to the filename once it was confirmed or released. e.g, 1037904930.368624.acl:2,X djb defines several flags, all for use by MUAs (see ``What can I put in info?'' under http://cr.yp.to/proto/maildir.html). The question becomes, what flags would we use to indicate 'confirmed' and 'released'? How would MUAs react to those flags? Down the road, what happens if these flags conflict with new ones that djb defines? So, I don't think the "info" flag approach would work. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
