On May 10, 2010, at 2:10 AM, Robin Bowes wrote:
On 10/05/10 06:55, Robert Spier wrote:
Robin Bowes wrote:
Hi,
I committed my auth_vpopmaild plugin to my github fork [1].
I've also attached the patch against Ask's upstream master to this
msg.
It looks like both you and Matt are working on vpopmail related
plugins.
Is there overlap between the two plugins? Do we need both in core?
Robert,
The two plugins do the same thing (authenticate users against a
vpopmail
installation) but in different ways.
auth_vpopmaild:
- no additional perl modules required
- connects over a tcp socket to a vpopmaild daemon
- requires vpopmaild daemon service
- vpopmail not required on same machine as qpsmtpd
auth_vpopmail
- requires vpopmail perl module (hooks directly into the static
libvpopmail.a library)
- vpopmail must be on same machine as qpsmtpd
As to whether both, or either, are "needed" in core - that's not for
me
to say. I don't see why both can't be included.
R.
I believe all three should be included. In addition to the comments
Robin made about auth_vpopmail, it also requires custom hacking to the
p5-vpopmail .xs file, which adds support for CRAM-MD5 authentication
to work properly. I have contributed a patch to the p5-vpopmail
author but have no idea how long it'll take before it makes it's way
into a release, and that makes it's way into distributions.
For people running the vpopmaild daemon, I suspect that its a better
solution than either auth_vpopmail or auth_vpopmail_sql.
Matt
