> --- Michael <[EMAIL PROTECTED]> wrote: >> It is certainly safe to have all users on the system sharing the same >> whitelist & blacklist file. >> >> I would like to have all users on the system share the same >> 'confirmed' >> file ... >> > > What is going to be the difference between your 'confirmed' file and > your 'whitelist' file? If you will create your filter so that confirmed > addresses are allowed through (using CONFIRM_APPEND) then you are > essentially creating another whitelist.
Correct ... I just created two files ... 'whitelist' is manually maintained and 'confirmed' uses CONFIRM_APPEND > Do you want all your users to be able to receive mail from any address > that any other user accepted and confirmed? Yes > I mean, if Joe gets an > e-mail from someone and that person confirms... does that mean that the > same person should automatically be allowed to send mail to Bob as > well? I can see why you would want to do this in a business > environment... Yes, that is what I want to do. > The tricky thing is this... IF you had a user send a message to 20 > people... who would the confirmation message come from? It would have > to come from all of them. Thus the pending list would exist in 20 > places, and just because the sender responds to one of the confirmation > requests, doesn't mean he will respond to all of them. I'm not thinking of someone mailing to 20 at a time. someone sends a message to [EMAIL PROTECTED] today ... and confirms. I want it to be CONFIRM_APPENDed to a globally-shared 'confirmed' file. tomorrow they send a message to [EMAIL PROTECTED] ... no confirmation is necessary because they are now whitelisted in the shared 'confirmed' file. But the problem is that I am concerned about multiple processes writing to the shared 'confirmed' file .... Michael _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
