Tim Rice <[EMAIL PROTECTED]> writes: > 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.
Er, only MMDF you mean. As I explained in my last reply, there is a workaround for every other MTA. > 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. This seems like a whole lot of work for something that only affects one TMDA user (you). In my last reply, I asked the following, and I'd still like to know if you've pursused this: Is there no way to configure MMDF's SMTP interface to just accept the transmission regardless, to get it into the mailq where it will be retried as necessary? With qmail, this is the default behavior. With Postfix, you can toggle it on. Not sure about Exim but I imagine it's configurable. With Sendmail, you can get this behavior by using the /usr/sbin/sendmail interface instead of SMTP. In other words, there should be some kind of similar solution for MMDF. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
