Steve Charmer writes:

from the terminal, do I call the bash script?
   /usr/sbin/authdaemond stopor just
   authdaemond stop
(bcuz it's in my path, both should work)

Correct, it does the same thing.


 authdaemond: Authenticated: sysusername=<null>, sysuserid=8, sysgroupid=8, homedir=/var/vmail/<URL:http://domain.com/acct>domain.com/acct, address=<URL:mailto:[email protected]>[email protected], fullname=<null>, maildir=/var/vmail/<URL:http://domain.com/acct>domain.com/acct, quota=<null>, options=<null>  authdaemond: Authenticated: clearpasswd=MYPASSWORD, passwd=$1$EGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGR.ZbFFFFFFFFFFFFFFFFFFF/  imapd: LOGIN, user=<URL:mailto:[email protected]>[email protected], ip=[::ffff:xxx.xxx.xxx.xxx], port=[56789], protocol=IMAP
 imapd: Connection, ip=[::ffff:xxx.xxx.xxx.xxx]





so it appears to be working.


Is it shown twice (the first clearpasswd is null) because the DEBUG level is set to 2, and it needs to do debug level 1 first, (the login attempt), then level 2 (the clearpasswd) ?


or do I have 2 instances running in memory?

No, different parts of the daemon were doing their own logging.

does authdaemond run as a service? or is it just called on demand by courier- imapd-ssl ?
I tried systemctl list-units -a to view all the services
but I did not find a service named   authdaemond

authdaemond runs as a permanent service. Check for services that have "authlib" in their name.

for the purposes of customizing rsyslog, does authdaemond have a facility name, or is it captured under mail.* ?


I noticed it worked for me under   <URL:http://mail.info>mail.info and mail.debug 

LOGGEROPTS in the authdaemonrc configuration file sets options for courierlogger. You can specify a -facility option to use a different subsystem.

Attachment: pgpot2N80nHxC.pgp
Description: PGP signature

_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to