GeoSync / News: Recent posts

I have just uploaded the RFC into the Docs section

Since my uni project is now complete and handed in, it's time to tag a proper release of Geosync (which is considered to be libdpop3 and the gnu-pop3d patch).
I am not aware of any bugs in this release, but there may well be some, besides, even if you install this, there are no client mail programs that can support the protocol yet, so it wouldn't be much use. I'm going to start talking to mail client authors soon and see if I can rustle up some support.

The second release candidate for my university project has now been tagged in CVS.
This includes fixes for all known bugs and adds the following features:
o Debug/Warning/Critical libdpop3 logs are now redirected to /tmp/libdpop3.log instead of stderr
o UIDL is now implemented and returns the same md5 unique id that RETR does. This is considered the canonical id for that mail as far as the server is concerned (which means it will propogate to clients)

There is a fairly serious bug in the UNI-RC1 release of libdpop3 that stores timestamp information incorrectly.
UNI-RC2 should be tagged tomorrow and that will contain a fix.

The project now (roughly) meets the requirments for my university project. All in just under a month of hacking!
This does not mean GeoSync is now suitable for production use, however. More work is needed to harden the error handling and there are some implementation subtleties that need clearing up.

I have just started moving code into GeoSync (or libdpop3 as it is more often known) into the CVS repository.
I'm tidying it up from my local code, so there will be some bugs as I change namespaces, rework bits, etc.
The gnu-pop3d module in CVS contains the latest release at the time of writing with modifications for dpop3 support on a seperate branch.
The libdpop3 module is GeoSync, ie it is the dpop3 library that servers should link against.