Re: confirm looping. How to stop it?
Stephen Warren <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.user |
|---|---|
| Message-ID | <[email protected]> |
Rich Duzenbury wrote: > On Wed, 2006-09-20 at 11:30 -0600, Stephen Warren wrote: >> 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. > > 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? Well, one of the variables that gets set is: [email protected] from this, the "extension" part of that address is: confirm-1158794185.6596.21dee4 This value is then usually placed into a variable named EXTENSION by your MTA. see section "General Prerequisites" on this page: http://wiki.tmda.net/PreConfiguration This actually implies that no configuration is required for Courier to set EXTENSION correctly, so I guess something in your chain of filter/delivery commands is stripping EXTENSION from the environment? My advice is to apply your tmdadebug wrapper script technique to other programs/scripts/... in your filter/deliver command chain and verify (a) that EXTENSION is being set at all, and (b) find out what's stripping it out of the environment, and configure it not to. Alternatively, enhance your tmdadebug script to calculate EXTENSION from RECIPIENT - that should work (be wary of when there is no extension).
signature.asc
(application/pgp-signature, 250 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFEeWZhk3bo0lNTrURAhWMAKCd9VO0YLXqMAaaXX8OBwZmi6BdwwCgkoSz +wwRuHrgjRFrM+aPYO8GqxE= =YwqA -----END PGP SIGNATURE-----