SEO

Hi

After upgrading courier-imap I can no longer log in to the mailserver.
Any attempt will fail and put th following in the log:

Feb 9 15:49:11 [imapd] authdaemon: s_connect() failed: No such file or
directory
Feb 9 15:49:11 [imapd] LOGIN FAILED, user=username,
ip=[::ffff:111.222.333.444]
Feb 9 15:49:11 [imapd] authentication error: No such file or directory
Feb 9 15:49:37 [imapd] authdaemon: s_connect() failed: No such file or
directory
Feb 9 15:49:37 [imapd] LOGIN FAILED, user=username,
ip=[::ffff:111.222.333.444]
Feb 9 15:49:37 [imapd] authentication error: No such file or directory
Feb 9 15:50:37 [imapd] authdaemon: s_connect() failed: No such file or
directory
Feb 9 15:50:37 [imapd] LOGIN FAILED, user=username,
ip=[::ffff:111.222.333.444]
Feb 9 15:50:37 [imapd] authentication error: No such file or directory

I reckon that i have be a bit quick with etc-update and now I am, not
able to find the correct parameter to get some kind of authentication
running again.

Any ideas would be appreciated.


--
/raymond

PERL - Linux' Swiss Army Chainsaw

Hello Raymond,


> After upgrading courier-imap I can no longer log in to the mailserver.


I experienced the same. Check that courier-authlib (not authdaemond as
it was before!) is running and verify it with authtest (as root).


HTH,
-hannes

Hannes Erven wrote:
> Hello Raymond,
>
>
>> After upgrading courier-imap I can no longer log in to the mailserver.
>
>
>
> I experienced the same. Check that courier-authlib (not authdaemond as
> it was before!) is running and verify it with authtest (as root).

That solved the problem, but it does not seem to want to run correctly
at startup. Any ideas why? I have to restart it manually (not start, but
restart) to make it work. Something I forgot perhaps?

--
/ray

> That solved the problem, but it does not seem to want to run correctly
> at startup. Any ideas why? I have to restart it manually (not start, but
> restart) to make it work. Something I forgot perhaps?

Umm... <guessing>: ensure that you only start authdaemond OR
courier-authlib . (I guess I unmerged authdaemond so I forgot to tell
you.. sorry!)</guessing>

Is there something in the logs? What does ps axu | grep auth tell you?
Is courier-authlib zap ; courier-authlib start fine?


lg,
-hannes

Hannes Erven wrote:
>> That solved the problem, but it does not seem to want to run correctly
>> at startup. Any ideas why? I have to restart it manually (not start,
>> but restart) to make it work. Something I forgot perhaps?
>
>
> Umm... <guessing>: ensure that you only start authdaemond OR
> courier-authlib . (I guess I unmerged authdaemond so I forgot to tell
> you.. sorry!)</guessing>
>
> Is there something in the logs? What does ps axu | grep auth tell you?
> Is courier-authlib zap ; courier-authlib start fine?

Hmmm.... for some reason it seemed to work now, but I still get a:

root 1675 0.0 0.0 1356 424 ? S 20:51 0:00
/usr/sbin/courierlogger -pid=/var/run/authdaemon.pid -start
/usr/lib/courier/courier-authlib/authdaemond

in the process list.

Checked and found:

morgul root # rc-update -s default

authdaemond |
clamd | default
clock |
consolefont |
courier-authlib | default
courier-imapd | default
courier-imapd-ssl | default
courier-pop3d | default
courier-pop3d-ssl | default

in the runlevel, so authdaemond is not supposed to start, bit it still
seems to for some reason. Anything I need to cahnge in
/etc/courier-imap/something maybe?

--
/ray