"Richard Smith" <[EMAIL PROTECTED]> writes: > What's happening is that when I send TMDA a message, it responds with a > confirmation request since the address I'm using is not in any lists. When I > reply to the confirmation (using both the MUA reply, and creating a blank > email to the address generated, TMDA keeps sending requests...
The address that you reply to, supplied by TMDA in the confirmation request, should look something like this: [EMAIL PROTECTED] where XXXXXXXXX is a timestamp, NNNNN is a PID and nnnnnn is a cryptographic magic number. You should also see, in your incoming log, the confirmation message come through *to* that address. But all that is in the log is a confirm to [EMAIL PROTECTED] This means that, somewhere along the line, this address is getting screwed up. Did you carefully follow the Exim configuration described at: http://www.tmda.net/config-pre.html At a guess, you haven't got Exim configured to understand and preserve extension addresses. It doesn't by default. > <---- SNIPPET FROM LOG FILE ----> > Date: Sat Jan 18 23:05:49 GMT 2003 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subj: confirm > Actn: CONFIRM action_incoming > (1982) > > Date: Sat Jan 18 23:05:49 GMT 2003 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subj: confirm > Actn: CONFIRM pending 1042931149.1568.msg > (1982) These are both for the original message. > Date: Sat Jan 18 23:07:33 GMT 2003 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subj: Re: Please confirm your message > Actn: CONFIRM action_incoming > (5383) Here you replied to the confirmation request, but the To address is wrong, so TMDA doesn't recognize it as a an actual confirmation. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
