Ah, duplication of effort. :) I guess I should've tried to get mine on CPAN when I wrote it, so it might've saved you some work. Though maybe not, since my module seems quite a bit more basic than yours, as it doesn't support any of the extensions and leaves a lot more up to the user to implement.

I'm curious, though, why you insist that your module is alpha. What necessesary features does it still lack?

And, yes, I went with the new/start model to stay close to Net::Server's style as, I assume, did you.

Though maybe not, since my module seems quite a bit more basic than yours, as it doesn't support any of the extensions and leaves a lot more up to the user to implement.

I'd probably have based my module on yours, if I'd found yours on the CPAN when I was looking. That might have influenced my interface. It might also be that I wouldn't have been inspired then to put mine on the CPAN, if yours was there already. Dunno. I don't think I'll take mine down now, though, since as you point out it implements more.

I'm curious, though, why you insist that your module is alpha. What necessesary features does it still lack?

It's alpha because it's less than three months old, and I'm pretty much the only person working on it (though I did get a one-line fix sent to me from a person using the code once already). It's mostly complete now, and I should probably graduate it to beta status one of these releases. There are features it still lacks. stopserver and restartserver methods are lacking, and when I get those working I'd like to augment the sample proxy with a control script to start and stop it. APOP is not supported yet. I still need to recheck RFC 1939 to make sure I've implemented every MUST. It has been reported that on some perls on some platforms $EOL needs to be changed to "\r\n" to work correctly, but that breaks it on Mandrake Linux (my development platform) and I still need to figure out how to automatically detect which way to go.

There are useful things that can be done without any of these features, of course. Currently my development is focusing mostly on the sample scripts and testing, so I guess with the next release I could mark it beta.

---

;$;=sub{$/};@;=map{my($a,$b)=($_,$;);$;=sub{$a.$b->()}} split//,".rekcah lreP rehtona tsuJ";$\=$;[-1]->();print

John and Nathan, I am maintainer of Mail::POP3 since 2002-ish, which implements a POP3 server. Having come back to it this month, I realise it is badly named and should be something like Net::Server::POP3[::*].

The purpose of it was only ever to implement a POP3 server-side interface to make a "mailbox" interface to a website (specifically jobserve, as it happens), to be able to use my email program to easily "reply" to a job ad.

I know these modules aren't "broke", so there may be no need to "fix" them. However, I see that you chaps last updated your modules in 2004/2005, and I wonder whether it would be a good idea for me to take them over? I want to put them both in one distribution, since they are similar, obviously leaving them with the same API, and include another module that gives the "email" interface to a website, as above.