amavisd-new 2.7.2 vs 2.8.0:?

[Patrick Ben Koetter]

* Steve <steeeeeveee at gmx.net>:
> 
> -------- Original-Nachricht --------
> > Datum: Sat, 07 Jul 2012 12:44:54 +0200
> > Von: Mark Martinec <Mark.Martinec+amavis at ijs.si>
> > An: amavis-users at amavis.org
> > Betreff: Re: amavisd-new 2.7.2 vs 2.8.0:?
> 
> > Quanah,
> > 
> >  > I'm kind of curious as to whether or not 0MQ is dead.
> >  > I've filed multiple bug reports with them with zero feedback.
> >  > <https://github.com/lestrrat/p5-ZMQ/issues?state=open>
> > 
> > Don't know, I hope it's not dead, there have been releases
> > since the fork.
> > 
> > But since the fork of a 0MQ project into a Crossroads I/O,
> > with two main developers actively continuing their work there,
> > seems to me the other one has a better prospect. Time will tell.
> > 
> > 
> > On 2012-07-07 10:53, Steve wrote:
> > > You don't know Quanah! When he wants something then he wants it to be
> > done/ready yesterday.
> > 
> > :)
> > 
> > Quanah has been very patient with me dragging my feet regarding
> > improving LDAP support. Appreciated.
> > 
> Well... I see him often nagging/(requesting) on the dspam mailing list for ipv6 support. Last time he even sent a bunch of links for how to implement ipv6 into c code. Funny. When I read it I asked my self: he took the time to find documentation what needs to be added/changed in c code for ipv6 code (in addition to ipv4 code) and this is not the first time he is asking for that on the list. And so far no one of the community has made anything. And this guy works for EMC/VMware where a gazillion of coders are working and he can not provide a small patch adding that ipv6 support that he is claiming to be easy to add? Is the community not supposed to work that way, that everyone is contributing as much as they can?

You do it yourself, you pay someone else or you wait until someone does it
when that persons thinks the time is right.

p at rick

-- 
All technical questions asked privately will be automatically answered on the
list and archived for public access unless privacy is explicitely required and
justified.

saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>