Steve Keith <[EMAIL PROTECTED]> writes: > However, I have made some progress. I had missed the example tmdarc file > in sample.config. My tmdarc is now: > > MAIL_TRANSFER_AGENT = "sendmail" > > RECIPIENT_DELIMITER = "+" > > DELIVERY = "|/usr/bin/procmail ~/.procmailrc-tmda" > > FILTER_INCOMING="/etc/tmda/incoming" > CRYPT_KEY_FILE="/etc/tmda/crypt_key" > LOGFILE_INCOMING="/var/log/tmda.in" > LOGFILE_OUTGOING="/var/log/tmda.out" > LOGFILE_DEBUG="/var/log/tmda.debug" > > This has changed the problem... > > Now, everything seems to work, though not quite right... > > Confirmation messages are sent out from "root" with the users e-mail > (e.g., [EMAIL PROTECTED]).
Can you clarify this, perhaps by posting the header of a confirmation message (received by an outside sender)? It seems to me that if the >From field is the user's email, then it's not being sent from root...? > Confirmation replies are accepted and acknowledged; however, the > message intended for steve goes to root, TMDA expects to run as the user receiving the mail. From what you say below, that does appear to be true (pending messages are stored in /home/steve/.tmda/pending). When a message is confirmed, TMDA re-sends that message to the address it found in the RECIPIENT environment variable when it received the message for the first time. RECIPIENT, in Sendmail's case, is set by the .procmailrc script. You might want to check if that is being set correctly. An easy way to do that is to look at the message in the pending directory and find out what the X-TMDA-Recipient field says. > and the whitelist does not appear to be updated since subsequent > e-mails from the outside address require another confirmation. You need to set the CONFIRM_APPEND variable to the path of the whitelist file in order to have TMDA "auto-whitelist" an address. Take a look at http://tmda.net/config-vars.html for a list of all the configuration variables you might want to set. Many of the defaults work fine, but some, like CONFIRM_APPEND, you almost always want to change. > Furthermore in /home/steve/.tmda/pending the messages delivered to root > are still pending. Please ignore the contents of pending. Messages remain in pending even after they have been confirmed and delivered. For more details, you can search the archives. > An important detail may be that ~/.procmailrc-tmda files do not exist. > Per the man page: "If no rcfile is found, or processing of the rcfile > falls off the end, procmail will store the mail in the default system > mail�box." I assumed one is not necessary for each user, but that > assumption may be incorrect. Well, the DELIVERY example setting isn't a magic incantation! It says to run procmail and use the ~/.procmailrc-tmda file. If that file doesn't exist, you'll certainly run into problems; the messages won't be delivered how you want, at the very least. The example says to find the .procmailrc-tmda file in each user's home directory (that's what the '~' means). If you don't want per-user dot-procmailrc files, then change the path to point to the one you want to use. Obviously, that file will have to deliver multiple users' mail to the correct location, but that's a procmail issue. > Again, I'm trying to use this as a global system rather than user-specifc. > I may have munged something up in the process. TMDA is designed to be per-user. You can certainly set it up globally, but you'll definitely have to do some configuration in order to make it work that way. Particularly, as you've discovered, the means by which you deliver the message has to make sense for multiple users. Since TMDA runs as the user, the dot-procmailrc file will be run as that user, also, which means there are probably environment variables or procmail variables that can help you (MAILDIR comes to mind). Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
