-------- Original-Nachricht -------- > Datum: Mon, 18 Jan 2010 17:17:43 -0500 > Von: "Mark Nernberg (gmail account)" <marknernb...@gmail.com> > An: Steve <steeeeev...@gmx.net> > CC: "postfix-users@postfix.org" <postfix-users@postfix.org> > Betreff: Re: The method behind the madness
> > > On Jan 18, 2010, at 17:05, "Steve" <steeeeev...@gmx.net> wrote: > > > > > -------- Original-Nachricht -------- > >> Datum: Mon, 18 Jan 2010 11:30:49 -0800 > >> Von: "Daniel L. Miller" <dmil...@amfes.com> > >> An: Postfix users <postfix-users@postfix.org> > >> Betreff: Re: The method behind the madness > > > >> Stan Hoeppner wrote: > >>> Daniel L. Miller put forth on 1/18/2010 12:51 PM: > >>> > >>> > >>>> A point - and a good one for initialization of the whitelist. > >>>> However, > >>>> this does not address the need to add new addresses to the list > >>>> automatically. Example - our company changes insurance brokers, > >>>> and > >>>> needs to receive forms from the new broker. Such communications > >>>> should > >>>> not be reliant on the IT department "unlocking" the mail server - > >>>> just > >>>> the act of the office manager's sending an e-mail to the broker > >>>> should > >>>> be sufficient. > >>>> > >>> > >>> Daniel, it seems you're looking for feature perfection in rev. > >>> 0.1.1 of > >> an as > >>> yet created home brew software solution. Do you think you might be > >> setting your > >>> sights a bit high? > >> And what's wrong with setting your sights high? Or wanting to plan > >> things out before diving in? > >>> Is this because you already have a solution that does all > >>> these things perfectly, and you're _expecting_ your new home brew > >> solution to do > >>> the same right from the start? > >>> > >> Yes - ASSP. But I'd like to implement it as a "pure" Postfix > >> solution > >> instead of a proxy server. > >>> If you _need_ a home brew solution _now_, start small and inelegant, > >> getting > >>> most of the functionality you want/need. This can be done with > >>> simple > >> scripts > >>> and cron. After it's working relatively well, _then_ spend time > >> creating the > >>> "elegant" solution. JMHO. > >>> > >> > >> But the main thing is having OP-maintained lists is exactly what I'm > >> trying to avoid and completely misses the point of having an > >> auto-whitelist. > >> > > It's not hard to write a small Perl script doing that automatically. > > I have done that and my current implementation is 132 LOC. It's > > ultra easy and stores the AWL data in MySQL. One does not need to be > > a rocket science to code that in Perl. Just a small Postfix policy > > service that returns every time a DUNNO but uses the data from the > > Postfix policy delegation to feed the AWL. > > > > > > I have achieved this with a slightly hacked TMDA (www.tmda.net). if > you want my modifications, contact me off-list. > Asking Google for help about a solution that does already AWL for Postfix lead me to this page: http://www.terena.org/~visser/awl.php The script there (http://www.terena.org/~visser/whitelist_sasl.pl) could be used as a base for doing a AWL service in a Postfix policy. No need to go on and use TMDA. The Perl script above is sure not perfect (what ever perfect might be) but it's small and easy to extend. It is mentioning SA but at the end you could change it to fill up any database you like and you can tweak the SQL till it fits your needs. I find that much easier then using such a big think as TMDA. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser
