Hi, Curtis (and the group), I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. I don't have any more time to mess with it this morning, but I will make it a point to try 'shadow' when I get in this evening. It's possible that NetBSD wants to work that way. Thanks for your help. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If Salvador Dali had owned a computer, would it have been equipped with surreal ports?"
On Mon, 2006-07-10 at 06:55 -0700, Bruce Lane wrote:> Hi, Curtis (and the group), > > I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. > > I don't have any more time to mess with it this morning, but I will make it a point to try 'shadow' when I get in this evening. It's possible that NetBSD wants to work that way.Or possibly "bsdauth". I don't know if it works with NetBSD though. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20060710/bf6fcd9f/attachment.bin>
Bruce Lane wrote:> I tried setting up Dovecot's auth default section as you described, > with both authdb and userdb set to 'passwd.' It let the authenticated > session start on the POP side, but I got consistent authentication > failures on the client side that the passwords didn't match. > > I don't have any more time to mess with it this morning, but I will > make it a point to try 'shadow' when I get in this evening. It's > possible that NetBSD wants to work that way.*********************************************** $ uname -rs NetBSD 3.0 *********************************************** $ egrep -A 1 -B 2 'passwd \{' dovecot.conf.ssl # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. passdb passwd { } -- # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } *********************************************** Without problems. Kind regards, Petar