* Wietse Venema [2014-05-27T17:48:03]
> Ricardo Signes:
> > a. one IP, the same username, many different passwords
> > d. one IP, the same username, the same (wrong) password repeatedly
>
> I suppose that one would log a password hhas, just to be sure.
Yes, something like a truncated h
Ricardo Signes:
> a. one IP, the same username, many different passwords
> d. one IP, the same username, the same (wrong) password repeatedly
I suppose that one would log a password hhas, just to be sure.
> I definitely understand the point about not wanting to deal with the SASL
> inte
* Wietse Venema [2014-05-27T17:04:32]
> li...@rhsoft.net:
> > the problem ist that postfix has no idea of the SASL internals and should
> > not need to - in case of dovecot i asked a few days ago to log the username
> > because in case of using dovecot as SASL provider that's the only instance
> >
Am 27.05.2014 23:04, schrieb Wietse Venema:
> li...@rhsoft.net:
>> the problem ist that postfix has no idea of the SASL internals and should
>> not need to - in case of dovecot i asked a few days ago to log the username
>> because in case of using dovecot as SASL provider that's the only instance
li...@rhsoft.net:
> the problem ist that postfix has no idea of the SASL internals and should
> not need to - in case of dovecot i asked a few days ago to log the username
> because in case of using dovecot as SASL provider that's the only instance
> which decodes the input and verify it against th
Am 27.05.2014 22:45, schrieb Ricardo Signes:
> I'm looking for a way to detect and distinguish different kinds of auth
> failures. Right now, I'm feeling a bit stuck by my inability to get all the
> data I'd like in one place at the same time.
>
> Right now, we're using SASL authentication with
