Tom,
TMDA as it stands now is not able to forward to multiple accounts, but
you could have the [EMAIL PROTECTED] account TMDA protected, then have
it deliver the mail to an intermediate dissemination account after it
gets past the initial info account.
e.g. mail sent to info gets challenged
mail that successfully gets past the challenge gets delivered to a non
tmda protected account which then redirects the mail to multiple recipients.
Then for any of the multiple recipients that are also TMDA protected
they should have an incoming rule that uses the whitelist generated by
the info account as it's source (be sure to make it readable by everyone
in the redirect). There might be more direct ways to do this, but I'm
not in a vpopmail environment, and am no longer in a qmail environment
either. Anyway the path would look as follows:
[EMAIL PROTECTED]>tmda->[EMAIL PROTECTED]> (multiple addresses
e.g. [EMAIL PROTECTED], [EMAIL PROTECTED], ...)
and each of the final recipients would need a line similar to the
following in their incoming filter:
from-file -autodbm -optional
/path/to/vpopmail/user/info's/.tmda/lists/WhiteList ok
ensuring that /path/to/vpopmail/user/info's/.tmda/lists/WhiteList is
readable by all the final recipients.
[EMAIL PROTECTED] wrote:
Hello together,
I successfully set up TMDA on my domain, but one issue is still bothering me
(even after hours of reading the mailing list archive and the FAQ).
My setup: qmail, vpopmail, latest tmda and tmda-cgi
We have several internal redirect adresses.
For example [EMAIL PROTECTED] gets redirected to [EMAIL PROTECTED], [EMAIL
PROTECTED], [EMAIL PROTECTED] ...
So the sender of a message to [EMAIL PROTECTED] will receive a confirmation
message from each user and has to confirm each of these (he gets whitelisted
after the first confirmation, but the messages remein in the pending queue of
course).
Can anybody give a hint of how to resolve this issue?
I already tried to realize [EMAIL PROTECTED] via an ezmlm mailing list and than
protect this mailing list with tmda. This would work fine for users who are not
TMDA protected, but not for those who are :-(
Any suggestions are really appreciated.
Kind regards,
Tom
begin:vcard
fn:David Grimberg
n:Grimberg;David
email;internet:[EMAIL PROTECTED]
x-mozilla-html:TRUE
version:2.1
end:vcard
_____________________________________________
tmda-users mailing list ([email protected])
http://tmda.net/lists/listinfo/tmda-users
