Re: pop access

-----BEGIN PGP SIGNED MESSAGE----- "Andy" == Andy Piper <andyp(a)parallax.co.uk&gt; writes: Andy> I notice that gnus distributes pop3.el but doesn't appear to Andy> use it. Not by default; it uses the same movemail program that Rmail uses. nnmail-movemail-program controls this behaviour. [...] Andy> What does vm-pop do that pop3 doesn't? Does anyone use Andy> pop3.el with gnus? Are there any other pop access packages? I do; but then, I wrote it. :) Some things to consider: VM's copyright is quite specifically *NOT* owned by the FSF. RMS will not allow any code into the FSF Emacs distribution for which the FSF does not hold the copyright. Which means that any 'unified pop' based on vm-pop will not be distributed by the FSF, which means a 'unified pop' based on vm-pop will not be particularly unified. I have signed the rights to pop3.el to the FSF, so there is no problem there. There is a lot of VM-specific code in vm-pop, since it is a full-blown POP3 client. Using vm-pop as a code base will require much rewriting, even assuming you can get past the legal issues. pop3.el is a library, not a client (pop3-movemail is a reference implementation). A unified POP client could be easilly written using pop3.el as the foundation. That is why I wrote it. -- Rat <ratinox(a)peorth.gweep.net&gt; \ Do not taunt Happy Fun Ball. PGP Key: at a key server near you! \ \