Hi,
As per my discussion with cmouse on irc, I'm currently just using dovecot for its auth mechanism, etc capabilities (alas, Exim does not support argon directly). Tis a fun little side project. :)
I have the config pared down as far as I think is reasonable (see below) and all is working well except that dovecot is very silent.
Errors hit the logs but I would appreciate seeing successful auths happen for the additional piece of mind. Cmouse and I couldn't find a way to do it on irc and it appears that the capability is missing. Successul /logins/ can be logged but auths, by themselves, cannot.
I would appreciate if the ability was added.
Dovecot 2.3.7.1 is in use.
Thanks
Pigeonhole version 0.5.7.1 (db5c74be)
OS: Linux 5.2.4 x86_64 Debian 10.0
Hostname: bob
auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1:16 log_timestamp = "%Y-%m-%d %H:%M:%S %z " mail_log_prefix = "%{pid}<%{session}> %{service}(%{user}): " passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } service anvil { unix_listener anvil-auth-penalty { mode = 00 } } service auth-worker { user = $default_internal_user } service auth { unix_listener auth-client { group = Debian-exim mode = 0660 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }
AP
On August 2, 2019 9:35 PM AP via dovecot <dovecot@dovecot.org> wrote:
As per my discussion with cmouse on irc, I'm currently just using dovecot for its auth mechanism, etc capabilities (alas, Exim does not support argon directly). Tis a fun little side project. :)
I have the config pared down as far as I think is reasonable (see below) and all is working well except that dovecot is very silent.
Errors hit the logs but I would appreciate seeing successful auths happen for the additional piece of mind. Cmouse and I couldn't find a way to do it on irc and it appears that the capability is missing. Successul /logins/ can be logged but auths, by themselves, cannot.
I would appreciate if the ability was added.
Dovecot 2.3.7.1 is in use.
Events (using event exporter) is probably what you want, new in 2.3.7.
https://doc.dovecot.org/admin_manual/list_of_events/
michael
On Sat, Aug 03, 2019 at 11:27:24AM -0600, Michael Slusarz wrote:
Errors hit the logs but I would appreciate seeing successful auths happen for the additional piece of mind. Cmouse and I couldn't find a way to do it on irc and it appears that the capability is missing. Successul /logins/ can be logged but auths, by themselves, cannot.
I would appreciate if the ability was added.
Dovecot 2.3.7.1 is in use.
Events (using event exporter) is probably what you want, new in 2.3.7.
Hi,
I've tried using this in various ways but I could never get any real success.
I came close but the logging was always far too verbose. The info I wanted WAS there but so was a ton of other data I didn't want. I'd share the configs I tried but they came and went as I was experimenting.
Would love to know how to configure the events logging such that I only get a successful auth line logged as that would, indeed, solve my issue. It's quite likely I didn't hit the right config as the docs are somewhat sparse.
AP
On 4 Aug 2019, at 6.23, AP via dovecot <dovecot@dovecot.org> wrote:
On Sat, Aug 03, 2019 at 11:27:24AM -0600, Michael Slusarz wrote:
Errors hit the logs but I would appreciate seeing successful auths happen for the additional piece of mind. Cmouse and I couldn't find a way to do it on irc and it appears that the capability is missing. Successul /logins/ can be logged but auths, by themselves, cannot.
I would appreciate if the ability was added.
Dovecot 2.3.7.1 is in use.
Events (using event exporter) is probably what you want, new in 2.3.7.
Hi,
I've tried using this in various ways but I could never get any real success.
I came close but the logging was always far too verbose. The info I wanted WAS there but so was a ton of other data I didn't want. I'd share the configs I tried but they came and went as I was experimenting.
Would love to know how to configure the events logging such that I only get a successful auth line logged as that would, indeed, solve my issue. It's quite likely I didn't hit the right config as the docs are somewhat sparse.
There probably isn't yet a name for the event that you want. A kludgy approach would be to filter the event based on the source code filename and line number. But that likely needs to be modified every time you upgrade Dovecot..
participants (3)
-
AP
-
Michael Slusarz
-
Timo Sirainen