Milter-greylist

Am Die den 20. Februar 2007 um 22:59 Uhr schrieb manu@...:
> Oliver Haufe <oliver.haufe@...> wrote:
> 
> > Easy - now it also accepts "WHITE"  from access.db.  But as i am running an
> > older Version "milter-greylist-3.0rc7" so if someone would like to patch
> > his version he schould check the place inside milter-greylist.c
> 
> Any volunteer to test that against CVS and provide a patch?

Hm. I think this is probably not really what i want.

My modified pop3-Server writes the IP-Address of the client directly
into the Berkley DB file "access.db", not into its cleartext dependant
"access". If it did so, it had to call a makemap after each
modification, which would not be very elegant. So if we modify
milter-greylist to look into the access-db, we should use the Berkley
DB API to do so. I could provide the code, i have a little bit
experience with this, because i modified the pop3 server too.


But i think there must be a way to pass the value from the RHS of the
access.db via some sendmail rules to the milter. With:

O Milter.macros.envrcpt={greylist}

you just tell sendmail to pass the macro {greylist} to the milter, but how
must i define this macro, so that it contains a value from a db-file?
This is not described in any playce, at least i havent found it.
I found in the list archives that Ivan F Martinez provided the code
for this, is he still on the list and can explain this any further?


Another way would be to make the pop3 server modify milter-greylists
configfile. Is it correct, that MG rereads its configfile automatically
every time it has been modified?

Bye,
Georg