Re: Messages to multiple receivers with aliases
[email protected] Sat, 19 Apr 2008 08:44:04 +0200
| Newsgroups | gmane.mail.spam.tmda.user |
|---|---|
| Message-ID | <[email protected]> |
Hello David, thank you for your response! As I use a global whitelist for all accounts, I tried your suggestion too some days ago. But when [email protected] gets the message forwarded after confirmation from info@... , he sends out another confirmation request. And this is done by all users. Message: Bad confirmation cookie. So I did the following: Create a new pop account info@... , protect it by TMDA. Forward confirmed/whitelisted messages to a new list which has a cryptic address. On this new list, all the users are listed, but not with user1@mydomain, but with user1-cryptedstring@mydomain. Than for each user I created a .qmail-username-cryptedstring file which delivers messages directly to their inbox. I know that spam to username-cryptedstring@mydomain will pass through, but I'll give the system a shot :-) Regards, Tom David Grimberg schrieb: > 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 >> >> >> >> _____________________________________________ >> tmda-users mailing list ([email protected]) >> http://tmda.net/lists/listinfo/tmda-users