On Thu, 7 Aug 2003, Jason R. Mastaler wrote: > > What if we keep a MD5 hash index of the incoming messages that are > > in the pending queue and check against this in confirm mode. (Am I > > making sense?) > > Not really, can you elaborate?
The MTA pipes the incoming message to TMDA. TMDA checks rules to see if it's white-listed/blackliste , if not goes to confirm mode. TMDA puts the incoming message in pending and tries to send a confirm message to the sender. Some MTAs don't blindly accept the confirm message causing an error if there is a DNS problem or the user/domain is bogus which leaves the incoming message in the queue for retry later. This could easily cause several thousand messages in the pending queue for just one piece of spam. What if we scanned the pending queue for a duplicate message before trying to send a new confirm message. If it is a duplicate, remove the pending message just created and retry the confirm message for the original pending message. Perhaps keep a MD5 sum list of the messages in pending queue to make it easier to find duplicates. -- Tim Rice Multitalents (707) 887-1469 [EMAIL PROTECTED] _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
