This is a discussion on Re: restriction_classes lookup. within the mailing.postfix.users forums, part of the Mail Servers and Related category; suneel cumar wrote: > Hi all, > > i have setup virtual domains. > > 1. i need to create ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
suneel cumar wrote:
> Hi all, > > i have setup virtual domains. > > 1. i need to create a all@domain.com for every domain. > so any user sending a mail to all@domain.com should > forward to all users in that domain. > > All my virtual domains are looked up from database. > the trivial answer is to create a (virtual) alias that contains all users. Now, decompoe your company/network into groups, such as sales/mktg/eng/farniente/... and when you add a user, add him to one of the groups, then put the groups into the "all" alias. If you don't want this, choose an LDA (maildrop, procmail) and let it run a script that forwards the message to all users stored in some db. > > 2. i need to Whitelist sender address based on > recipients . > > Is it possible to whitelist a sender to a particular > domain or username. without user restriction_classes > parameter. > > I was able to do it through > recipient_restriction_classess. but i don't what to > edit the main.cf each every time to create a new class > for new group of whitelisting. > postfix access control is stateles, you can't say: F(client, sender, rcpt) = reject|permit|.... you have to do checks one at a time. Now, if you can define a limited number of recipient groups, then use restriction classes. You can for instance define N groups, and let users choose their own, which results in selecting the right restriction class. If you can't, use a policy service and make it to do what you want. > > 3. i want to restrict certain domains and users to > outside mails. and restriction them with thier > respective domains. > > > Desperately looking for a solution. Any ideas will > greatly appreciated. > Unless you can cast your requirements to fit postfix, you'll need a policy service to match your requirements. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|