> > ------------------- > > The idea > > ------------------- > > If we could check the 'sender-status' before requesting a confirmation > > we could, if it fails, give the message a new status in the pending queue > > and later (at random times like purge) attempt to deliver confirmation > > requests IF the 'sender-status' ever is good > > > > You may want to limit the number of messages it attempts at a time. > > thoughts? > > > > 0) Most of the messages with smtp connection failures are spam (well, > most of _everything_ is spam, these days). So it might be a > waste of effort.
I almost totally agree ;) If we can detect Connection Refused vs Time out or DNS error then I would agree... > 1) It is probably not worth the effort of keeping track of the sender status > if what you want to do is make one more effort to confirm (or > send a final bounce message) before purging. In fact, I think > the messages where confirmations don't bounce are more likely to > be actual messages from humans (as opposed to spammers :-). No I want to take more effort before sending a message that is likely to fail... Failures end up sending Two messages... We could generate a (local) database of servers that do not accept SMTP connections (from us) and test it as a domain blacklist We could even skip the sender check on future messages... tom _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
