[vox-tech] Squirrel Mail Authentication Problems

[ME]

Ryan said:
> I think I have imap set up incorrectly. In the manual it says that if
> authdaemon isn't running, imap won't work correctly. I have never used
> imap before and I can't seem to locate the log file for courier.
>
> In /var/log/messages I see this line:
>
> Mar 22 06:54:33 the45 authdaemon: authdaemon: s_connect() failed: No
> such file or directory

In Debian, courier config files can be found in /etc/courier and there is
more in /var/lib/courier

There are really two ways (maybe more) to set up authorization with
courier. Getting courier setup to work should be your first priority
before trying to get SM to work.

The two methods for auth that I know about include use of /etc/passwd and
the system usernames and password *or* used of "userdb" which permits you
to have a separate DB password file and user list for authentication. (I
used userdb from courier since I did not want to enter my shell
password/username pair when checking SM from public machines.)

Once you get courier properly setup, you should be able to run an IMAP
client to talk to courier. PINE does this, and so does Netscape. If that
works, then move on to SM.

When you try to login to SM, it passes your auth info (username and
password) to the IMAP server. If imap is not properly setup to permit
logins, SM wont work.

As for logs, my copy logs login and logout to syslog as an imaplogin event.

> So it looks like the authdaemon isn't working correctly.
>
> What imapd do you use? I am using courier only because that is what SM
> recommends.

courier-imap: it works well for me.

> I forgot to mention this, but I had run that configure script. I set the
> imap server to courier but I dont see any option to set the auth_type to
> userdb.

Yep, that is a courier imap config option.

> I'll tweak around SM after I get the imap configured properly. Do you
> know how to access the courier log?

Nope, the info in syslog seemed to permit me to properly configure it.

I used the docs that come with courier to install and configure it to work.

> On Sat, 2003-03-22 at 10:54, ME wrote:
>> Ryan said:
>> > 	"ERRORUnknown user or password incorrect."
>> >
>> > I am using version 1.2.10 along with courier-0.42.0 and php4.3. I have
>> > started the imapd and authdaemond but I still can't login. I have no
>> > idea how to even start trying to figure what is wrong.
>>
>> First, php 4.3 had some security holes and bugs, and upgrades from 4.3
>> to
>> 4.3.1 was suggested.
>>
>> Next, there has been discussion on the SM lists that SM is not fully
>> compatable with the 4.3.x series of PHP, and use of the latest 4.2.x was
>> better for stability.
>>
>> Next, SM 1.2.11 was released t fix security issues in 1.2.10, so you may
>> want to upgrade that too.
>>
>> (more)
>>
>> > 	Before messing with imap and squirrel mail I have been using exim and
>> > qpopper.
>>
>> qpopper also has had posted security issues.
>>
>> (See http://www.securityfocus.com/ and the BUGTRAQ link to search
>> archives.)
>>
>> > These are currently running and have not been restarted or
>> > touched. The only thing I have tried is compiling and make install-ing
>> > imap, and then doing an 'imapd start' and 'authdaemond start'.
>>
>> Have you ever run SM before? If Not, you will also need to run the SM
>> config program.
>>
>> cd to the web publishes SM dir, and from there, cd into its "config"
>> dir.
>> >From there run config.pl:
>> ./config.pl
>>
>> COnfigure SM to match your system with the same IMAP client and auth
>> method. I chose to setup my courrier-imap to use the userdb based auth
>> so
>> the passwords used for imap need not be the same as those in
>> /etc/passwd.
>>
>> Next note:
>> When I upgraded from 1.2.10 to 1.4.0RC1,RC2,RC2a, I had to rebuild my
>> config.php from scratch using the entries from the other in 1.2.10. It
>> seems
>> a copy of the config file over to the new one was not enough.
>>
>> You can check your logs too, to see what error isbeing reported. SM
>> auths
>> against imap so the courrier log entries should giuve you feedback on
>> the
>> problems encountered during auth.
>>
>> HTH
>> -ME