Joe,
--- On Wed, 2/3/10, Joe Knall <joe.kn...@gmx.net> wrote: > From: Joe Knall <joe.kn...@gmx.net> > Subject: Plugin for recipient specific black-white-list? > To: qpsmtpd@perl.org > Date: Wednesday, February 3, 2010, 1:25 PM > Hello, > > is there a plugin that already does the following and where > do I find it: > > 1. take envelope sender and recipient of incoming mail > 2. if recipient does not have a personal config (in > database...) -> deliver > > 3.a if recipient has a personal blacklist > if sender is blacklisted > -> deliver to /dev/null or recipients spam account, end > of processing > -> else deliver, end of processing > > 3.b if recipient has a personal whitelist > if sender is whitelisted > -> deliver, end of processing > -> else deliver to /dev/null or recipients spam account, > end of processing > > If there is no such plugin - is qpsmtpd the right thing to > use for this? > Are there better ways to achieve this? > > Background: > - whitelist for my child with grandma, friends... on, > everything else should > go to bigpapa for supervision > - separate black or white list for wife, delivery to > regular or personal spam > account > ... I wrote a plugin just like this using the LDAP domain check plugin as the template. What I don't have is the forwarding to big Papa feature. IMHO, that might be better as another plugin after passing spam checks. But I'm not the expert. > - maybe global blacklist (for all recipients) Global blacklists is done. Look at the check_spamhelo and check_badmailfrom > - in the end easy to configure with a web frontend The web front end is totally separate from qpsmtpd. My grand scheme was to use Drupal+LDAP modules to do the web frontend. I've worked with Drupal enough to do this, just never taken the time to do it. Maybe someone else has other suggestions for a web frontend? > (personal config in the > database) I'm nothing special as a coder, so I'm certain you can do it. LDAP isn't as popular a database to connect to as PostgreSQL/whatever, but works for me. Michael > > Thanks, Joe >