Re: confirm looping. How to stop it?

On Wed, 2006-09-20 at 11:30 -0600, Stephen Warren wrote:
> Rich Duzenbury wrote:
> > I'm trying to work through a problem with a new installation of tmda and
> > could use your advice.
> 
> > In this configuration, email from an unknown source is sent a
> > confirmation message.  Rather than accepting the confirmation, and
> > allowing the message in, another confirmation for the reply is
> > generated.  This continues over and over again.  Confirmations are never
> > recognized as confirmations.  They are instead seen as new requests, and
> > erroneously treated as such.
> 
> > The main interesting bit in the maillog is that tmda-filter is exiting
> > with code 99, even on a response to a confirm request.  
> 
> That's normal given how TMDA is acting (challenging mails). Whenever a
> message is challenged, TMDA "consumes" the message (places it into the
> holding "queue") and exits 99 to tell qmail not to attempt further
> processing of the email. Typically, when the confirmation comes in, TMDA
> will "pick up" the processing and deliver the email.
> 
> Do you have TMDA debug logging turned on - typically, look in the files
> ~/.tmda/logs - see also:
> 
> http://wiki.tmda.net/ConfigurationVariables#LOGFILE_DEBUG
> 
> One of these logfiles should/might tell you what's going on.
> 
> It sounds to me like TMDA isn't seeing the "EXTENSION" variable, which
> differentiates between mail to user@domain v.s.
> user-something-extra@domain. Perhaps you can check this.
> 
> 
http://theduz.com/tmda/dot-mailfilter

I think you are correct.  Now, what to do about it?

What I did was write a small perl script to dump the environment out to
a text file, just prior to calling tmda-filter
(http://theduz.com/tmda/tmdadebug)


You can see how I the MTA calls tmda-filter via:
http://theduz.com/tmda/dot-mailfilter
You might recall that this is courier-maildrop being called by courier.

Then, I sent an email from an unknown account, and attempted to confirm
it.

The environment trace is located at http://theduz.com/tmda/tmdadebug.log

If you review it, you might see that there isn't an EXTENSION variable
defined.  What is it supposed to be?  I suppose Courier doesn't provide
it, since it doesn't seem to be defined, so -- now what?

Thank you!

Regards,
Rich