Milter-greylist

> > > You may worry about compatibility with existing versions. My answer is
> > > simple: we must get rid of all existing versions. They are vulnerable.
> > > They dumbly records given mail addresses and fails to parse
> > > greylist.db. All efforts to keep compatibilitiy cannot change things
> > > better. We only need to make sure that the new milter-greylist can
> > > load existing greylist.db.
> > 
> > When I wrote it initially, my idea was that I didn't care about
> > unparsable addresses that could get into the database, because I could
> > just ignore them when reloading. 
> > 
> > So in my opinion, the problem is just that we bug on reloading bogus
> > addresses from the database, where we should just ignore them and skip
> > the line.
> > 
> > Do you see any problem with that approach?
> 
> Sounds reasonable. In this approach we only need to take care about
> lex/yacc caveats and non-ASCII characters breaking ctype(3).

Is this patch sufficient? I'm new to lex/yacc...

http://www.j10n.org/files/milter-greylist-3.0rc6-dosfix2.patch