Tim Legant <[EMAIL PROTECTED]> writes: >> If they aren't using this, I could imagine cases where someone >> would send 10 messages expecting to get back 10 confirmation >> requests. > > Without responding to any of them?
Why does it matter whether they have responded to any of them? > I'm curious why you want to do it this way. I don't see the point, > right off, of counting acceptance notices. Do we gain something > versus counting just confirmation requests? Failure notices (e.g, the notice returned when the sender is blacklisted) need to be counted, because a loop may develop there. For uniformity and ease of coding, confirmation acceptance notices are thrown into the mix as well. Technically though, you are right in that they probably don't need to be counted. > If this requires the sender-based queue, I withdraw the suggestion. > I wasn't thinking of that full implementation, though. I see very little distinction between the two. > Scanning all messages in pending/ would also work, but might be > prohibitively expensive... hmmm. That was my thought as well. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
