Re: Vexim Digest, Vol 68, Issue 4

> ---------- Forwarded message ----------
> From:=A0Avleen Vig <[email protected]>
> To:[email protected]
> Date:=A0Tue, 28 Dec 2010 21:37:42 -0800
> Subject:=A0[vexim] Ready.. Set.. Code!
> https://github.com/avleen/vexim
>
> Finally, after *years* of waiting, promises made and broken (by me,
> I'm sorry!), I'm finally in a position where I can focus heavily on
> vexim. I actually have *time* to do this now :-)
>
> The new version is being coded as we speak. I'm committing heavily to
> git as fast and often as I can.
> I'm hoping to get it the basic features done in the next 2 days.
>
> Some features which *probably* will get dropped for now:
> 1. Header-based blocking. We'll get it back if there is any interest
> (even just one person saying "I want that!").
> 2. The half-hearted support I coded in for non-spamassassin spam
> filtering. It didn't work. We'll stick with SA support for now, and
> later separate it such that we can write plugins for others
> 3. The non-English language support will not be there in the very
> first stable new version I think. But I'll be working closely with
> people to get translations in place.
>
> What are the goals of the new version?
> A complete re-write, to enable easier future development. Currently
> making even small changed to Vexim is a huge pain in the backside.
> To enable others to contribute changes more easily.
> To take the changes that others have make over the last 7 years and
> make sure they are all integrated.
>
>
> I think that's it. The other stuff is pretty basic functionality.
> If you join #vexim on Freenode, I'm in there too. If anyone wants to
> make suggestions, throw code in,
>
> --
> Avleen Vig
> Systems Administrator
> Personal: www.silverwraith.com
>


All I can say is it is great news and if it no longer needs php for
the front end then that is one less hassle set up wise to worry about
Terry