Displaying 7 results from an estimated 7 matches for "jk0bfm9yuqfaqafk".
2017 Sep 05
2
pam authentication
Sure :) thanks
cat /var/log/dovecot/[...]
Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
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>...
2017 Sep 05
2
pam authentication
...enticated
> }
>
> On 05.09.2017 14:29, Pol Hallen wrote: Sure :) thanks
>
> cat /var/log/dovecot/[...]
>
> Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
> Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
> 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,<...
2017 Sep 05
3
pam authentication
...thenticated
> }
>
> On 05.09.2017 14:29, Pol Hallen wrote: Sure :) thanks
>
> cat /var/log/dovecot/[...]
>
> Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
> Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
> 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,<JK0Bfm9YuqfA...
2017 Sep 05
0
pam authentication
...skip = authenticated
}
On 05.09.2017 14:29, Pol Hallen wrote:
> Sure :) thanks
>
> cat /var/log/dovecot/[...]
>
> Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
> Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
> 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,<...
2017 Sep 05
0
pam authentication
...;> On 05.09.2017 14:29, Pol Hallen wrote: Sure :) thanks
>>
>> cat /var/log/dovecot/[...]
>>
>> Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
>> Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
>> 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.o...
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
...gt;> On 05.09.2017 14:29, Pol Hallen wrote: Sure :) thanks
>>
>> cat /var/log/dovecot/[...]
>>
>> Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131)
>> Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN
>> 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....