On Saturday 21 May 2005 11:05 am, Matt Simerson wrote:
> On May 18, 2005, at 3:39 PM, Jeremy Kitchen wrote:
> > On Wednesday 18 May 2005 01:26 pm, Payal Rathod wrote:
> >> On Wed, May 18, 2005 at 01:15:22PM -0500, Jeremy Kitchen wrote:
> >>> don't use vpopmail's roaming-users functionality if you want
> >>> pop-before-smtp authentication, use Bruce Guenter's relay-ctrl
> >>> package.
> >>
> >> Any particular reason why?
> >
> > vpopmail's roaming-users support is poorly designed, slow, and
> > prone to
> > failure.
> I'd like to see some evidence to back up this assertion.

the fact that it's based around one file (actually, 3) that can theoretically 
be attempted to be updated many times simultaneously (requiring locking, etc)

the open-smtp file has to be locked, old entries purged, then the cdb file has 
to be locked, and rebuilt.  If you have 10k users and their mail clients 
check every .. 10 minutes.. you're rebuilding this giant tcp.smtp.cdb file 
quite often.

with relay-ctrl, it simply creates a file in a directory for each IP allowed, 
and checks for old ones that should be removed.

This is NFS safe, requires no locking (who cares if two processes try to 
create the same empty file at the same time), and is a lot more 

Plus, since the relay-ctrl software is independent of any other qmail process, 
no other qmail process needs to know the location of the relay-ctrl 
directory, whereas vpopmail's roaming users either requires you to change 
where your cdb file is, or tell it specifically where your cdb file is.

Also.. some people use scripts to generate their tcp.smtp.cdb file, since 
tcprules simply generates a cdb file based on stdin.  vpopmail's roaming 
users breaks this.


Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc.
    [EMAIL PROTECTED] ++ inter7.com ++ 866.528.3530 ++ 815.776.9465 int'l
      kitchen @ #qmail #gentoo on EFnet IRC ++ scriptkitchen.com/qmail
         GnuPG Key ID: 481BF7E2 ++ jabber:[EMAIL PROTECTED]

Attachment: pgpJrYPfjsAjd.pgp
Description: PGP signature

Reply via email to