search for: realsystem

Displaying 7 results from an estimated 7 matches for "realsystem".

2017 Sep 05
2
pam authentication
...N service=imap secured session=JK0Bfm9YuqfAqAFk lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== (previous base64 data may contain sensitive data) Sep 05 13:26:02 auth-worker(30088): Debug: pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup service=username_format=user00 Sep 05 13:26:02 auth-worker(30088): Debug: pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 style=1 msg=Password: ==> /var/log/dovecot.info <== Sep 05 13:26:04 auth-worker(30088): I...
2017 Sep 05
2
pam authentication
...secured session=JK0Bfm9YuqfAqAFk > lip=192.168.1.100 rip=192.168.1.100 lport=143 > rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== > (previous base64 data may contain sensitive data) > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup > service=username_format=user00 > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 > style=1 msg=Password: > ==> /var/log/dovecot.info <== > Sep 05 13:...
2017 Sep 05
3
pam authentication
...vice=imap secured session=JK0Bfm9YuqfAqAFk > lip=192.168.1.100 rip=192.168.1.100 lport=143 > rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== > (previous base64 data may contain sensitive data) > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup > service=username_format=user00 > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 > style=1 msg=Password: > ==> /var/log/dovecot.info <== > Sep 05 13:...
2017 Sep 05
0
pam authentication
...secured session=JK0Bfm9YuqfAqAFk > lip=192.168.1.100 rip=192.168.1.100 lport=143 > rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== > (previous base64 data may contain sensitive data) > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup > service=username_format=user00 > Sep 05 13:26:02 auth-worker(30088): Debug: > pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 > style=1 msg=Password: > ==> /var/log/dovecot.info <== > Sep 05 13:...
2017 Sep 05
0
pam authentication
...fm9YuqfAqAFk >> lip=192.168.1.100 rip=192.168.1.100 lport=143 >> rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== >> (previous base64 data may contain sensitive data) >> Sep 05 13:26:02 auth-worker(30088): Debug: >> pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup >> service=username_format=user00 >> Sep 05 13:26:02 auth-worker(30088): Debug: >> pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 >> style=1 msg=Password: >> ==> /var/log/dovecot.info &l...
2017 Sep 05
2
pam authentication
thanks Aki, but with all your advices I've same problem: in the logs always I see the authentication with user and domain name, so dovecot doesn't accept it any idea? thanks! Pol On 2017-09-05 10:58, Aki Tuomi wrote: > Oh right, you need to do it like this... > > after the passwd-file drivers add > > passdb { > driver = static > args = username=%n
2017 Sep 05
0
pam authentication
...session=JK0Bfm9YuqfAqAFk >> lip=192.168.1.100 rip=192.168.1.100 lport=143 >> rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== >> (previous base64 data may contain sensitive data) >> Sep 05 13:26:02 auth-worker(30088): Debug: >> pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): lookup >> service=username_format=user00 >> Sep 05 13:26:02 auth-worker(30088): Debug: >> pam(user00 at realsystem.org,192.168.1.100,<JK0Bfm9YuqfAqAFk>): #1/1 >> style=1 msg=Password: >> ==> /var/log/dovecot.info &l...