Tom Wolfe wrote:
Hi Stephen: Thanks for the personal reply, I appreciate your time and concern.
No problem. I'm cc'ing the TMDA list just in case this reply helps any one out, or is useful in the archives later...
Basically, I send an email to [EMAIL PROTECTED] and get a confirmation request. I then reply to [EMAIL PROTECTED] and get another confirmation request, to be sent to tom-confirm-YYYYY.sawback.com ... etc. See below for two examples generated from a throw-away hotmail account.
Is the second confirmation request's from/reply address [EMAIL PROTECTED], or just [EMAIL PROTECTED]
As I mentioned in my previous email sent to the tmda list, mail to [EMAIL PROTECTED] AND [EMAIL PROTECTED] are all filtered with tmda-filter using procmail. Both of these messages were generated by tmda as a result of being filtered through tmda-filter, but for some reason tmda-filter is not recognizing the tagged address.
OK. I personally don't use procmail. That said, there are some things your MTA needs to do to keep TMDA happy. qmail obviously does these (setting up some environment variables) and I have to assume that procmail maintains these variables and passes them on through to TMDA. But, you may want to check that:
a) Emails, as presented to TMDA, are prefixed with a Return-Path header, indicating the envelope sender. This is typically created by using the preline executable in your .qmail file. I have no idea if procmail does this, or if you still need preline in your .qmail file.
b) Make sure environment variables like EXT are defined - this tells TMDA which part of the recipient address is your main address (tom) and which parts are extensions (-confirm-XXXX) qmail typically does this, and I'm assuming procmail passes it all through. I don't know if this will get confused in your case, since you said the email is being forwarded from the recipient of [EMAIL PROTECTED] into your TMDA installation where your actual address is different...
c) I'm assuming procmail doesn't do any extension addres parsing. If it does, make sure it's configured for you recipient delimiter of -
My confirmed file (in .tmda/lists) is also not appended -- should this happen automatically as part of the confirmation process? If so, it's not happening.
You have to set a configuration variable to get this behaviour - it's not the default. See:
http://www.tmda.net/config-vars.html#CONFIRM_APPEND
The thing that makes me most suspicious right now is the from my procmail log (see below for a complete procmail log entry): (snip) procmail: Match on "^To:(.*\<)?tom@" procmail: Executing "/usr/home/sawback2/tmda/bin/tmda-filter" procmail: [39017] Mon Oct 25 14:08:39 2004 procmail: Program failure (99) of "/usr/home/sawback2/tmda/bin/tmda-filter" (snip)
It sounds like you have TMDA configured for qmail. This may sound fine, but apps configured to run from .qmail exit with various different status values indicating to qmail what to do with the email - such as:
0 - success 99 - success, and stop processing the rest of .qmail others - various forms of errors
So, you'll see 99 any time TMDA receives a message that it challenges - it exits 99 to tell qmail that everything was OK, but that the email should not be delivered to the user. TMDA delivers it later.
Regarding procmail, you may want to see if the link below helps:
http://www.lifewithqmail.org/lwq.html#procmail
Hope this helps get you started!
-- Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO [EMAIL PROTECTED] http://www.wwwdotorg.org/pgp.html
signature.asc
Description: OpenPGP digital signature
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
