While we're on the topic of pending, something I'm not happy with is that only tmda-pending can distinguish between "still pending" messages and those which have been already delivered (either by confirmation or manual release).
This is the source of the FAQ about why the message is still in pending even though it's already been delivered. And I don't blame them, the current behavior isn't very intuitive. In http://mla.libertine.org/tmda-workers/200204/msg00009.html, Drew suggested adopting the Maildir info flag approach. At the time I was considering storing additional message metadata, so I rejected it. Now, I don't think that's a relevant concern, as I'd store the metadata in a separate file anyway if I did this. I think I'd like to get rid of .delivered_cache, and instead append a status flag to the file once it's delivered. This shouldn't change tmda-pending behavior, but would allow homegrown tools to grok delivery status. Something like: 1036836637.29343.msg 1036836637.29343.msg:C 1036836637.29343.msg:R For still pending, delivered by sender confirmation, and delivered by manual release, respectively. Or is ``R;' confusing because it looks too much like Maildir's ``2,R'' and might give the impression of meaning "replied"? Any comments? _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
