Hi all:

Well, I seem to have finally solved the problem myself. Several problems in
fact... Here's what I've done so far as far as I can figure it. I'm no unix
pro by any stretch, which might explain why some of the things I'm doing
seem a little unorthodox:

1. I am using procmail to forward my mail to tmda-filter using a non-default
recipe (not .procmailrc). So despite the fact that my MTA is qmail, I still
needed to recreate the variables in my procmail recipe. This is because when
you use both -p and -m flags you lose almost all of your environment
variables (see man procmail) for some reason.

2. I removed # comment from the SHELL=/bin/sh line in the sample procmail
folder. Turns out my default shell is tcsh. Whether this makes a difference
or not I'm not sure, but I figured, why not? 

3. Using the sample procmail file, the EXTENSION variable sets to "+".
Whether this overrides the EXTENSION_DELIMITER variable from the config
file, I don't know... but I changed/left everything as "-" in the config and
procmail recipe files.

4. CONFIRM_ADDRESS is important for me to set since my system address is not
the one that I use and is not easily directed through a filter... 

5. I set the MTA to sendmail. This eliminates the Program Failure (99) issue
for some reason. Any guesses why?

So.... the current state of affairs is as follows:

1. Confirmation requests are sent (as always)
2. A sent confirmation receives a "Confirmation accepted" email (HURRAY!!!!
Finally!!!) *AND* even better, the lists/confirmed file is updated with the
new confirmed sender's address (HURRAY!!!! Finally!)
3. Subsequent emails from the same sender are accepted!
4. However... the initial email is not released from the pending cue to my
mailbox. I seem to remember an FAQ or a mailing list question dealing with
this so I'll press on with my struggle. However, if anyone could be so kind
as to point me to the solution I'd be grateful.

Andreas, hopefully my solutions give you some more ideas to try.

Some kind of a flowchart or explanation of how tmda works and various
potential pitfalls might be a useful piece of documentation... but someone
with more knowledge than I would need to create it!

Regards,
Tom Wolfe

 

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to