Tim Legant <[EMAIL PROTECTED]> writes: > Tom Allison <[EMAIL PROTECTED]> writes: > > > I get errors about not having a ~.tmdarc file, which I don't want to > > have and don't see in the docs that it's required. I am trying to > > get this configured as a system level filter and not per user. > > Either a ~/.tmdarc or a ~/.tmda/config is required. However, you > bring up an interesting point. If you've created an /etc/tmdarc for > your system, why should a user-specific file be required? This is > especially true for systems that have only "virtual" users, but even > for systems with shell users it should work.
Jason, does it make sense to you not to require a ~/.tmdarc or ~/.tmda/config if we have successfully loaded an /etc/tmdarc? If there's no /etc/tmdarc and no local .tmda/config, then in every case except qmail's, the code for checking if DELIVERY is set will raise a ConfigError, which sounds right. You need to configure DELIVERY somewhere. This might be a useful step toward easing configuration for mailhub and ISP type situations. If /etc/tmdarc sets DELIVERY to deliver through procmail, for instance, then all a user needs to do to begin using TMDA would be to run tmda-keygen and create a single-line .forward file. Without a .procmailrc, procmail delivers to /var/mail or /var/spool/mail. If default delivery is to a maildir or mbox in $HOME, that's also trivial and then you don't need procmail. New users can learn about customizing TMDA and procmail filters as they have time. Seems useful to me and I can't think of any reason why it wouldn't work, given the config/crypt_key split. Anyone have any thoughts on this, one way or the other? Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
