RE: [vchkpw] can login on LDAP / can NOT login on pop3
The netstat -lnp | grep 110 had the following result: tcp0 0 0.0.0.0:110 0.0.0.0:* LISTEN 1373/couriertcpd --- --- --- And as far as I know I am running Courier-IMAP for IMAP and qmail-popup for POP ... nope sorry... looks like your running courier as your pop client or atleast that's the one that currently has the port... I would configure courier to not listen to the pop port and confirm that qmail is configured with /service for qmail-pop3d running I'd then stop courier restart qmail confirm that it is qmail-pop3d that has control of port 110 and then restart courier. kenneth gf brown
Re: [vchkpw] quotawarn....
shadowplay.net schrieb: has neone else had this issue? once again the issue is no removal of quotawarn messages I have the same 'problem' Werner
Re: [vchkpw] can login on LDAP / can NOT login on pop3
On Aug 21, 2004, at 6:44 PM, [EMAIL PROTECTED] wrote: in the file /etc/pop3d it reads: AUTHMODULES=authshadow POP3AUTH=LOGIN CRAM-MD5 CRAM-SHA1 POP3AUTH_TLS=LOGIN PLAIN POP3DSTART=YES If you change the first line to say authvchkpw instead of authshadow, that should do the trick. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] quotawarn....
shadowplay.net wrote: has neone else had this issue? once again the issue is no removal of quotawarn messages Yes I have had this issue, and stopped quotawarn messages as a solution. The bigger issue for us was getting the maildirsize file to properly update sometimes. Currently we just go through and delete them all and rerun vuserinfo which replaces the file. Everything has been fine once this was done. I've never brought it to the list becasue I thought is was becasue we moved maildirs from a machine with maildirs and installed them on amchine with maildir++ after we installed courier. DAve
