authdaemond shenanigans

[hazza]

Hello,

I've been running a test mail server happily enough for the past month until I came to update vpopmail and courier-imap (now on versions 5.4.6-r1 and 3.0.5 respectively). Vpopmail is behaving itself (after updating the format of /etc/vpopmail.conf), however authdaemond appears to have broken quite impressively.

Restarting the server gives

Code: Select all

10653 ?        S      0:00 /usr/lib/courier-imap/courierlogger -pid=/var/lib/courier-imap/authdaemon/pid -start /usr/lib/courier-imap/authlib/authdaemond.plain
10654 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain
10655 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain
10656 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain
10673 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain
10674 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain
10675 ?        S      0:00 /usr/lib/courier-imap/authlib/authdaemond.plain

Lovely - the server is running happily enough. Logs report similar joy:

Code: Select all

Aug 25 10:30:18 mordor authdaemond.plain: restarting authdaemond children
Aug 25 10:30:18 mordor authdaemond.plain: modules="authvchkpw", daemons=5
Aug 25 10:30:19 mordor authdaemond.plain: modules="authvchkpw", daemons=5

All well and good.
However, if you try and either log in via pop3 or run a /usr/lib/courier-imap/authlib/authtest with appropriate user info, you get a failed login with the following in the logs:

Code: Select all

Aug 25 10:32:33 mordor authdaemond.plain: could not connect to mysql update server Access denied for user: 'root@localhost' (Using password: YES) with database
Aug 25 10:32:33 mordor authdaemond.plain: could not connect to mysql update server Access denied for user: 'root@localhost' (Using password: YES)

Now to my untrained eye, this looks as if authdaemond is trying to talk to the MySQL server natively rather than using vchkpw, even though the config files say otherwise:
/etc/courier-imap/authdaemond.conf:

Code: Select all

AUTHDAEMOND="authdaemond.plain"

/etc/courier-imap/authdaemonrc:

Code: Select all

authmodulelist="authvchkpw"
authmodulelistorig="authcustom authcram authuserdb authvchkpw authmysql authpam"
daemons=5
version=""
authdaemonvar=/var/lib/courier-imap/authdaemon

So, I'm confused... Anyone got any ideas? I'm sure it's probably a perfectly simple problem, so if anyone could point out my idiocy I'd be much obliged

Cheers,
--Harry

[hazza]

I can't explain this one, but never mind: Just re-emerged (no changes to config, USE flags or anything else) and everything is working swimmingly agin... Strange, but true...

TTFN,
--Harry

[ferdog]

I'm having the exact same problem and would like to know what exactly did you re-emerge? I've tried re-emerging courier-imap, but that did not help at all.

[hazza]

what exactly did you re-emerge? I've tried re-emerging courier-imap, but that did not help at all.

I issued the following command:

Code: Select all

mordor root # emerge vpopmail courier-imap

That's it - no changes to use flags or any other faffing around. Oh, and I rebooted - that's the lot. Restarting the services didn't seem to carry sufficient clout, so shutting the damn thing down for a moment wielded a far greater mental (if not machinish) impact. Well strange

I guess the only likely reason for this is that the damn thing had a stale library loaded (or something - being highly technical here!) and the reboot flushed it and loaded the new freshly compiled one.

As I say, mad.

TTFN,
--Harry

[Guybrush]

Hi,

had the same problem. Reemerging vpopmail and courier-imap solved this,
Quite strange though...

But I think it was because my last

Code: Select all

emerge -u world 

first emerged courier-imap before vpopmail.

This might be the solution.