This is a discussion on Re: Postfix User Level Gateway? within the mailing.postfix.users forums, part of the Mail Servers and Related category; On Monday, May 10, 2004 at 21:50 CEST, Henrik Hudson <lists@rhavenn.net> wrote: [...] > I've ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Monday, May 10, 2004 at 21:50 CEST,
Henrik Hudson <lists@rhavenn.net> wrote: [...] > I've found the various HOW-TO's / FAQs about gateway'ing on a domain > level via the transport table, but is there anyway to do this on a > user level? I cannot parse this paragraph. It seems like you see a problem where there isn't one. > Ideal Functionality on Gateway: > -User level control of white/blacklists via a webinterface > -DSPAM or SpamAssassin for SPAM blocking > -All or most config info in LDAP; ie the whitelists, etc... >=20 > This might be a better query for the DSPAM/SA lists, but thought I > would start here. I just can't think how Postfix would do the scan at > a user level (since it would have to know about the users) and then > deliver to the primary server, since it would now be trying to drop > mail into a user's box? No problems here. Configure Postfix to use a content filter to run the spamfilter (amavisd-new is popular among Postfix users), and use a transport map to redirect the mail to the internal server after reinjection. Per-user whitelists etc is a feature of the spamfilter, and I think SpamAssassin supports it both with and without amavisd-new. Extract the valid recipient addresses and use them with relay_recipient_maps to avoid being a victim of dictionary attacks. Different methods of using SpamAssassin as a content filter is currently being discussed in the thread "SpamAssassin: spamd vs amavis-new". [...] --=20 Magnus B=E4ck magnus@dsek.lth.se |