Jim Ramsay <[EMAIL PROTECTED]> writes: > As for the option itself, I think I'll do it like: > > PENDING_WHITELIST_RELEASE = None | Current > > with "Current" as the default instead of making it just a True/False > option, as eventually (maybe) we can add the "All" option which will > release all matching sender message (option C).
Probably best to use integers (0, 1, and perhaps 2 in the future) to match current code (e.g, AUTORESPONSE_INCLUDE_SENDER_COPY). As far as the option C, this has been discussed in the past in the context of a sender based pending queue, where messages are stored according to sender. This way, all matching sender messages are released upon confirmation as well as by tmda-pending/cgi release. This has been requested enough that I think it's worth implementing. My thought was to design a queue abstraction where we support a few different types of pending queues (current simple format, a sender based, and a Maildir++ compatible) but where sites with special pending queue needs can drop in their own module. When I will get the time to do this I'm not sure, but it's something I definitely want to do in TMDA 1.1.x. Any design thoughts anyone has on the matter are welcome. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
