"Thomas Cameron" <[EMAIL PROTECTED]> writes: > Here is the log once the message is replied to:
[snip what we saw before...] > Date: Mon Jan 27 23:35:51 CST 2003 > From: "Thomas Cameron" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: Re: Sorry for the inconvenience, please confirm your message > Actn: CONFIRM accept 1043732141.31576.msg > (1665) Here TMDA logs that the crypto stuff checked out and that it accepts the confirmation reply. > Date: Mon Jan 27 23:35:51 CST 2003 > From: "Thomas Cameron" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: Re: Sorry for the inconvenience, please confirm your message > Actn: CONFIRM_APPEND /home/spam/.tmda/lists/confirmed > (1665) Here TMDA notes that it added [EMAIL PROTECTED] to your CONFIRM_APPEND file, /home/spam/.tmda/lists/confirmed. Also at this point, it resends the original mail to spam@... with an added header to indicate that the confirmation has come through. > Date: Mon Jan 27 23:35:52 CST 2003 > From: "Thomas Cameron" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subj: test3 > Actn: OK good_confirm_done_cookie > (952) Here, TMDA gets the original mail the second time with the special 'confirm-done' header and delivers it. > But when I send another e-mail from [EMAIL PROTECTED], I get > another confirmation request: [...] > Let me know what you think... I think you might not have a /home/spam/.tmda/filters/incoming file. If you don't have an incoming filter file, then you won't have added your CONFIRM_APPEND file to it. At a minimum, your incoming filter should say: from-file ~/.tmda/lists/confirmed accept If you don't have a rule mentioning your 'confirmed' file, TMDA won't look at it. It uses the CONFIRM_APPEND configuration variable only as the location to store successfully confirmed addresses. It doesn't automatically look up incoming addresses there. This may not be intuitively obvious. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
