search for: featherweb

...unable to get the mail client I'm experimenting with (Pegasus) to complete a pop3s connection, in that I still get an indication of a failed password. However, at least I'm a little closer to understanding the failure itself. Please note what came up in /var/log/maillog. Jul 13 22:41:25 featherweb dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=192.168.42.130 rip=192.168.42.40 resp=AGt5cnJpbgBocDIxZHZlbTc= Jul 13 22:41:25 featherweb dovecot: auth(default): cache(kyrrin at bluefeathertech.com,192.168.42.40): User unknown Jul 13 22:41:26 feat...

...o just use basic POP3 without worrying about authentication. QUESTIONS: (1) Does the dovecot master daemon have to be running in order to call pop3- login from inetd, in response to POP connection attempts? If so, it could be a problem. I'm getting this error when I try to start the thing. featherweb: {339} /usr/local/sbin/dovecot Fatal: listen(110) failed: Address already in use featherweb: {340} (2) For apop authentication, how do I go about generating the shared secret file locally, for each user? Is there a script that came with dovecot or...? (3) Is there a trick, similar to postfix'...

...ve -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at bluefeathertech.com,192.168.42.40): pam_start() failed: system error Jul 9 21:14:17 featherweb dovecot: pop3-login: Aborted login: user=<kyrrin at bluefeathertech.com>, method=PLAIN, rip=192.168.42.40, lip=192.168.42.130, TLS THE PLATFORM: NetBSD 3.0,...

...or a WINS Client, but NOT both wins server = 192.168.42.90 # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names # via DNS nslookups. The default is NO. dns proxy = no #============================ Share Definitions ============================== [webstuff] comment = Featherweb doc directories path = /usr/local/www/htdocs browseable = yes writable = yes valid users = kyrrin jlanfri kathy write list = @www @wheel create mask = 0755 [logging] comment = Featherweb logging path = /var/log browseable = yes writable = no valid users = kyrrin j...

...'s five processes for imap-login. What gives? On to your second question: Are /etc/pwd.db and /etc/spwd.db available? Yes, both are listed in the directory of /etc as follows. -rw-r--r-- 1 root wheel 40960 Jul 9 09:56 /etc/pwd.db -rw------- 1 root wheel 40960 Jul 9 09:56 /etc/spwd.db featherweb: {41} How "available" this makes them (I don't know what context you were asking in), I'm not sure. Just for giggles, I tried chaning the permissions on spwd.db so that it was world-readable. Doing so had no effect. I still get password failure errors when I try to authenticate...