Re: [vchkpw] courier-imap roaming-users problem
Newer version of courier-imap will no longer be able to write the IPs into the relay table. This is because all authentication has now been moved out of courier (and sqwebmail) and into the courier-authlib package. As has always been the case, authdaemon doesn't support POP before SMTP. That's why I chose never to use authdaemon. Now that courier no longer supports POP before SMTP via the authvchkpw module, it's just one more good reason not to use courier-imap for POP3 services. Use qmails pop3d instead. That way POP users still get roaming access. IMAP users are users newer email clients that support SMTP AUTH and should be directed to use that instead. I have overcome this via the relay-ctrl package. My roaming users don't roam very often, but -do- (and are required to) use DDNS. Via their DDNS record, I can easily access their machine if need be...but I digress. I have written a -simple- perl cron that reverse queries their name/ip mapping, and updates the relay-ctrl directory of the allowed ip's that can relay. This way, I'm still using courier. (not that qmail-pop is bad, I've used it too...just have courier in this case) Just my approach. -Chris
[vchkpw] courier-imap roaming-users problem
Hi there. I'm using qmail, vpopmail (mysql) with roaming-users, and courier-imap on my FreeBSD Box. The problem is that, although I compiled courier with authvchkpw-auth it seems not to call this program. I think so because I see (with ktrace and truss) that courier authenticate my users reading the mysql database and it adds also the info data to the relay table on MySQL directly (I mean, not using vchkpw as it should do). So, the user is authenticated and can read his e-mail but he isn't added to the tcp.smtp.cdb file (tcpserver). We compile authlib and courier-imap in this way: courier-authlib $ ./configure --without-authpam --without-authldap --without-authpwd --without-authmysql --without-authpgsql --without-authshadow --without-authuserdb --without-authcustom --without-authcram --without-authdaemon --with-authvchkpw courier-imap export CFLAGS=-DHAVE_OPEN_SMTP_RELAY -DHAVE_VLOGAUTH /configure --prefix=/usr/local/courier-imap --disable-root-check --with-trashquota --enable-unicode --enable-roaming-users=y Any suggestion or idea? Thanks in advance Jesús Arnáiz
Re: [vchkpw] courier-imap roaming-users problem
On Feb 4, 2005, at 6:11 AM, Jesús Arnáiz wrote: The problem is that, although I compiled courier with authvchkpw-auth it seems not to call this program. I think so because I see (with ktrace and truss) that courier authenticate my users reading the mysql database and it adds also the info data to the relay table on MySQL directly (I mean, not using vchkpw as it should do). So, the user is authenticated and can read his e-mail but he isn't added to the tcp.smtp.cdb file (tcpserver). Actually authvchkpw is a version of vchkpw that's integrated with courier-imap. It never calls vchkpw directly, so it's behaving as expected. Unfortunately, I don't know about using roaming users (pop before smtp) with courier. I've always used SMTP AUTH as the sole relaying mechanism on our servers. -- 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] courier-imap roaming-users problem
On Feb 4, 2005, at 10:25 AM, Tom Collins wrote: On Feb 4, 2005, at 6:11 AM, Jesús Arnáiz wrote: The problem is that, although I compiled courier with authvchkpw-auth it seems not to call this program. I think so because I see (with ktrace and truss) that courier authenticate my users reading the mysql database and it adds also the info data to the relay table on MySQL directly (I mean, not using vchkpw as it should do). So, the user is authenticated and can read his e-mail but he isn't added to the tcp.smtp.cdb file (tcpserver). Actually authvchkpw is a version of vchkpw that's integrated with courier-imap. It never calls vchkpw directly, so it's behaving as expected. Well, at least as documented. Unfortunately, I don't know about using roaming users (pop before smtp) with courier. I've always used SMTP AUTH as the sole relaying mechanism on our servers. Newer version of courier-imap will no longer be able to write the IPs into the relay table. This is because all authentication has now been moved out of courier (and sqwebmail) and into the courier-authlib package. As has always been the case, authdaemon doesn't support POP before SMTP. That's why I chose never to use authdaemon. Now that courier no longer supports POP before SMTP via the authvchkpw module, it's just one more good reason not to use courier-imap for POP3 services. Use qmails pop3d instead. That way POP users still get roaming access. IMAP users are users newer email clients that support SMTP AUTH and should be directed to use that instead. Matt `` Matt Simersonhttp://matt.simerson.net The Network People Inc. http://www.tnpi.biz The chief danger in life is that you may take too many precautions. - Alfred Adler ``
