Hello, I've been testing out tmda here for some weeks and have a problem that I "resolved" by using a shared crypt_key across all accounts, but I see read that is frowned upon, so I guess there is a better solution.
The setup I need tmda to work in is as following: - the mailalias "alias" expands to userA, userB, etc. It also first calls tmda. - userA, userB use tmda "personally". - when senderA sends mail to alias, the first line in the alias calls tmda and senderA has to confirm the message. When senderA confirm the message some global files get updated, so senderA can send mail to all users in alias. The message is then delivered to userA, userB, etc, all fine. However, the confirmationmessage is also delivered to userA, userB, etc. and their crypt_key is different from alias's crypt_key, so they are asked to confirm their message to userA, userB, etc. If userA, userB, etc.'s crypt_key is identical however, the confirmation is accepted by userA and userB too. Is there a better way to do this? Also, what is the problem with sharing crypt_key? (Please Cc me on replies, I'm not subscribed.) -- _ // \X/ -- Michael Shuldman <[EMAIL PROTECTED]> _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
