Okay, here's my configure for vpopmail:
./configure --enable-roaming-users=y --enable-logging=y \
--enable-clear-passwd=y --enable-mysql=y \
--enable-mysql-replication=y --enable-valias=y \
--enable-mysql-logging=y --enable-mysql-limits=y
And here's my configure for qmailadmin:
./configure --enable-cgibindir=/var/www/cgi-bin/ --enable-htmldir=/var/www/html \
--with-htmllibdir=/var/www/html
And here's my configure for courier-imap:
./configure --disable-root-check --without-authdaemon --with-authvchkpw \
--enable-workarounds-for-imap-client-bugs
And here's the output from the telnet session:
[root]# telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. See COPYING for
distribution information.
01 LOGIN [EMAIL PROTECTED] password
01 NO Login failed.
01 LOGOUT
* BYE Courier-IMAP server shutting down
01 OK LOGOUT completed
Connection closed by foreign host.
I am using Qmail POP3 and SMTP. Courier is only there for IMAP. I would think this
would only be a courier configuration issue (since courier does support mysql
authentication), however, qmailadmin doesn't authenticate either, so I don't know if
it's related somehow or 2 seperate issues.
Thanks for the help.
-Todd Brill
====================================
OSC Hosting Inc.
Affordable Dedicated eMail, eCommerce, and Web servers.
!!! 30-day CASH BACK Guarantee !!!
!!! Unbeatable Price Guarantee !!!
http://www.1osc.com
> I noticed when you log in w/ pop3, its using plain text as far as the pw
> goes, are you sure your imap client isnt trying to use some sort of
> encryption? Try logging in via telnet over port 143, and test it
> something like this:
>
> [EMAIL PROTECTED]:~$ telnet 66.113.xx.xx 143
> Trying 66.113.xx.xx...
> Connected to 66.113.xx.xx.
> Escape character is '^]'.
> * OK Courier-IMAP ready. Copyright 1998-2002 Double Precision, Inc. See
> COPYING for distribution information.
> 01 LOGIN [EMAIL PROTECTED] mypassword
> 01 OK LOGIN Ok.
> 01 LOGOUT
> * BYE Courier-IMAP server shutting down
> 01 OK LOGOUT completed
> Connection closed by foreign host.
>
> I'm also curious are you using qmail pop3 or courier pop3? also what was
> the configure line you used to configure courier and qmailadmin? did you
> make any changes to any other source files before you compiled?
>
>
> On Sun, 2003-06-29 at 11:11, OSC Hosting SysAdmin wrote:
>> Actually, vpopmail is installed in /home/vpopmail so no need for symlinks. Here
>> is
>> some output for you to look at:
>>
>> [root]# /home/vpopmail/bin/vuserinfo [EMAIL PROTECTED]
>> name: test
>> passwd: $1$rSZWX$2IciZZWwyO2Yp1/5vAp3T.
>> clear passwd: password
>> uid: 0
>> gid: 0
>> all services available
>> dir: /home/vpopmail/domains/test1.com/test
>> quota: NOQUOTA
>> usage: NOQUOTA
>> last auth: Sun Jun 29 11:01:20 2003
>> last auth ip: a.b.c.d
>>
>> From /var/log/maillog after a successful pull using POP:
>>
>> Jun 29 11:03:51 1osc vpopmail[16769]: vchkpw-pop3: (PLAIN) login success
>> [EMAIL PROTECTED]:192.197.109.109
>>
>> From /var/log/maillog after unsuccessful login attempt using webmail (IMAP):
>>
>> Jun 29 11:07:15 1osc imapd: LOGIN, [EMAIL PROTECTED], ip=[::ffff:127.0.0.1]
>> Jun 29 11:07:15 1osc imapd: LOGOUT, [EMAIL PROTECTED], ip=[::ffff:127.0.0.1],
>> headers=0, body=0
>> Jun 29 11:07:31 1osc imapd: Connection, ip=[::ffff:127.0.0.1]
>> Jun 29 11:07:36 1osc imapd: LOGIN FAILED, ip=[::ffff:127.0.0.1]
>>
>> One thing that strikes me from this log is that with a user that works, the LOGIN
>> is
>> followed by the username where the LOGIN FAILED is not. I don't know if this has
>> any relevance to the problem or not.
>>
>> Thanks for all the troubleshooting guys.
>>
>> -Todd Brill
>> ====================================
>> OSC Hosting Inc.
>> Affordable Dedicated eMail, eCommerce, and Web servers.
>> !!! 30-day CASH BACK Guarantee !!!
>> !!! Unbeatable Price Guarantee !!!
>> http://www.1osc.com
>>
>> > You know this problem actually sounds familiar, vpopmail installs to
>> /home/vpopmail now (i think it used to be /var/vpopmail before), anyways courier
>> and
>> qmailadmin expect vpopmail to be in /home/vpopmail and if that isnt true, you have
>> to edit some configure scripts. Or you can just create a symlink from
>> /home/vpopmail to wherever it exists now. But other than that I cant think of what
>> could be causing it. Maybe some error logs would help?
>> >
>> > On Sat, 2003-06-28 at 21:11, OSC Hosting SysAdmin wrote:
>> >> Thanks for the tips, Eric, however, I had a working implementation before this
>> using
>> >> precisely the methods you outline below.
>> >> I can also use the new MySQL method for creating new users/domains and vpopmail
>> updates the db fine, so it's not a permissions issue.
>> >> When I use vpopmail to create or view info about users/domains from the command
>> line, I have no problem whatever.
>> >> As I mentioned, there is also no problem accessing these new users/domains
>> (that
>> exist in MySQL) using POP, but I can't authenticate using Qmailadmin or IMAP.
>> -Todd
>> Brill
>> >> ====================================
>> >> OSC Hosting Inc.
>> >> Affordable Dedicated eMail, eCommerce, and Web servers.
>> >> !!! 30-day CASH BACK Guarantee !!!
>> >> !!! Unbeatable Price Guarantee !!!
>> >> http://www.1osc.com
>> >> > When you configure courier, you need to make sure it links with vpopmail
>> authentication and not mysql. so when you configure courier be sure to pass the
>> option --without-authmysql and also --with-authvchkpw. I ran configure on my
>> qmail
>> server with vpopmail/courier/mysql with the following arguments:
>> >> >
>> >> > # ./configure --disable-root-check --without-authdaemon
>> >> > --without-authmysql --with-authvchkpw
>> >> > --enable-workarounds-for-imap-client-bugs
>> >> >
>> >> > then once built, you need to make the following changes.
>> >> > Edit /usr/lib/courier-imap/etc/imapd
>> >> > Change 'AUTHMODULES="..."' to 'AUTHMODULES="authvchkpw"'
>> >> > Change 'IMAPDSTART=NO' to 'IMAPDSTART=YES'
>> >> >
>> >> > As far as getting qmailadmin to work with mysql, there shouldnt be any
>> problems
>> there, so if qmailadmin can't authenticate, theres something wrong with your
>> vpopmail. When compiling vpopmail make sure you edit the mysql.h file to use the
>> correct mysql host/user/pass, and also make sure you give the
>> --enable-mysql=y when configuring vpopmail.
>> >> >
>> >> > If it still fails, the only other thing i can think of is that the mysql user
>> which vpopmail uses, doesnt have the required rights it needs to edit the vpopmail
>> db.
>> >> >
>> >> >
>> >> >
>> >> > On Fri, 2003-06-27 at 23:17, Michael Bowe wrote:
>> >> >> > That's interesting, Tom. I created a new domain called 'test1.com' and a
>> >> >> new user
>> >> >> > called 'test' and all the records in the database work and POP mail works
>> >> >> fine,
>> >> >> > however, Qmailadmin and IMAP won't authenticate.
>> >> >> >
>> >> >> > I double-checked the info for that domain/user on the command line and
>> >> >> vuserinfo
>> >> >> > reports back the correct information.
>> >> >>
>> >> >> Not sure if this is your problem, but it is something that trips a lot of
>> people up... :
>> >> >>
>> >> >> Every time you recompile vpopmail, you then need to go and recompile any of
>> the other apps that make use of the vpopmail authentication libraries (eg
>> qmailadmin, courier-imap)
>> >> >>
>> >> >> Michael.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >
>> >
>> >
>> >
>>
>>
>>
>>
>>
>>
>
>
>
