On Oct 7, 2004, at 2:20 PM, Nate Sanders wrote:
Obviously I am seriously confused by this whole system. I guess I fail to understand the whole process at this point. I'll just have to keep playing with it to try and figure it out.
At this point, I used tmda-cgi to setup one user (though I had to copy the .procmail info from TMDAs guide because tmda-cgi defaults to qmail), and the process is some what working. People are asked to reply with a blank message, but after they are added to the confirmed list, no email from them ever gets received. I also added a domain to the whitelist, and they too cannot send email. No errors in any maillog files.
The problem was that tmda-cgi didn't set the DELIVERY variable in my users config file. Problem solved.
On a side note, is a global config file required? Or do you just need the ~/user/.tmda/config ?
Still would like an answer on whats the real difference between a global config or user config. Which is better for a tmda-cgi setup?
On Oct 7, 2004, at 1:57 PM, Stephen Warren wrote:
Nate Sanders wrote:Hello everyone, this is my first post.
I'm working over the install right now and came to the question of wether or not I can configure TMDA to be global (instead of ~user/.tmda/). I believe the answer to my question is /etc/tmdarc.
You can put pretty much any configuration option you want either in the global config file, or the per-user file.
But, I was wondering if this would have a negative effect on my mailing lists, aliases, or other such addresses? Am I better off just setting it up per-user? It would obviously save a lot of time just going global (like /etc/procmailrc).
Well, it depends how you setup what. Filters aren't part of the config file (although the config file can determine their location) so you can have a unified global config file, with per-user filters for mailing lists etc.
Also, is it possible to store a system-wide global whitelist? It would be easiest if anyone who contacted a person within my company could then contact any other employee as well. There's no reason to have a whitelist per-employee.
It's easy to have either global or per-user filters, lists etc. The config file tells TMDA where the filters are - it can be either a single global path, or per-user. Equally, the filters determine where your lists are placed, so they can reference one, or both, of global lists and per-user lists.
-- Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO [EMAIL PROTECTED] http://www.wwwdotorg.org/pgp.html
------ Nate Sanders Customer Support Manager Sonic Studio, LLC (763) 577-1535 ext. 2
RMA Requests - [EMAIL PROTECTED] Keyfile Requests - [EMAIL PROTECTED] Support Requests - [EMAIL PROTECTED]
Email sent to the incorrect locations will not be handled with the same accuracy and speed as proper email submissions.
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
------ Nate Sanders Customer Support Manager Sonic Studio, LLC (763) 577-1535 ext. 2
RMA Requests - [EMAIL PROTECTED] Keyfile Requests - [EMAIL PROTECTED] Support Requests - [EMAIL PROTECTED]
Email sent to the incorrect locations will not be handled with the same accuracy and speed as proper email submissions.
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
