Milter-greylist

> > It is on my bug. In addition, sm_macro feature is not 
> working at all.
> > Please try this:
> > http://www.j10n.org/files/milter-greylist-3.0a5-misc.patch
> >
> > The 3.0a5 is sensitive to another bug in libmilter. You may need the
> > following patch to get final dump correctly. Otherwise, I recommend
> > dumpfreq 0.
> > http://www.j10n.org/files/libmilter-8.13.8-signal.patch
> 
> I must confess I'm not sure I took the right decision about 
> integrating
> the thread race condition fixes before the 3.0 release 
> instead of doing
> it afterwards.
> 
> Your work is very valuable, and I really appreciate your 
> contribution, 
> but it is a huge change set. I fear it needs a lot of testing before 
> being ready for a release. Moreover, it fixes problems that never 
> appeared at mine, so that raise the question whether this 
> huge fix was 
> critical enough to be merged at alpha stage. 
> 
> If I made the wrong decision, it's still time to roll back. 
> I'd like input
> from people that have tested previous 3.0 alpha releases: do 
> we need the
> thread race condition fixes in the 3.0 release, or shall we 
> back it out
> from the current sources and integrate it in the next 
> developement release?
> 
> If the answer to this question is the second alternative, then I'll 
> immediatly make two releases available:
> 1) 3.0a6, which will be 3.0a4 plus Attila's fixes (MX sync 
> and Tru64 build)
> 2) 3.1.1, which will be 3.0a5 plus your new patches.
> 

Hello,

This release does not look very stable, the daemon frequently dies without
any notice. Maybe the patches can be cut into smaller chunks and apply them
release by release? 

Bests,
Attila