search for: auth_request_finish

...ts there was on the server, and optional a way to filter on the auth attempt status (successful or failed). My server uses a simple auth (with LDAP backend) and supports only "auth_mechanisms = plain login" I tried using the following metrics: -------------------------------- metric auth_request_finished { event_name = auth_request_finished } metric auth_passdb_request_finished { event_name = auth_passdb_request_finished } metric auth_userdb_request_finished { event_name = auth_userdb_request_finished } metric auth_client_request_started { event_name = auth_client_request_started...

Hi, I'm playing with the new events, and encounter some issues: First the 'auth_request_finished' event is documented as having a 'successful' field, but in the code, the field is defined as 'success' (e->add_str("success", "yes")). But more important, in the function "auth_request_success_continue()" (auth/auth-request.c:288), "auth...

...e for success, one for all) and diff the 2 to get the count of failed attempts. > Le 12 juil. 2019 ? 15:31, Jean-Daniel Dupas via dovecot <dovecot at dovecot.org> a ?crit : > > Hi, > > I'm playing with the new events, and encounter some issues: > > First the 'auth_request_finished' event is documented as having a 'successful' field, but in the code, the field is defined as 'success' (e->add_str("success", "yes")). > > But more important, in the function "auth_request_success_continue()" (auth/auth-request.c:288),...

...> </div> <div> Hi, </div> <div> <br> </div> <div> I'm playing with the new events, and encounter some issues: </div> <div> <br> </div> <div> First the 'auth_request_finished' event is documented as having a 'successful' field, but in the code, the field is defined as 'success' (e->add_str("success", "yes")). </div> <div> <br> </div> <div> But more important, in the func...

> I'm trying to get some IMAP auth stats on a Dovecot 2.3.6 instance, but whatever I declare in metric, it always show 0. None of these auth_* requests exist in 2.3.6. > I tried using the following metrics: > > > -------------------------------- > metric auth_request_finished { > event_name = auth_request_finished > } > > metric auth_passdb_request_finished { > event_name = auth_passdb_request_finished > } > > metric auth_userdb_request_finished { > event_name = auth_userdb_request_finished > } > > metric auth_client_...

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once. This is confirmed by monitoring queries made...

...??? event_name = imap_command_finished ??? #source_location = example.c:123 ??? #categories = ??? fields = name args running_usecs bytes_in bytes_out ??? #filter { ??? #??? field_key = wildcard ??? #} } metric sql { ??? event_name = sql_query_finished } metric auth { ??? event_name = auth_request_finished ??? fields = user transport error successful } and get the following [root at stargate dovecot]# doveadm stats dump metric_name??? field??? count??? sum??? min??? max??? avg median??? stddev??? %95 imap??? duration??? 370??? 2007904499??? 130??? 62955249 5426768.92??? 2068??? 16436817.37???...

> On 15/03/2023 13:12 EET Dejan <me at dejanstrbac.com> wrote: > > > > lmtp_save_to_detail_mailbox = yes > > Plus-delivery conflicts with existing, reserved files such as > "subscriptions": > > Message for kim+subscriptions@ results in: > > lmtp(kim@***.com)<14493><SK7sEvaHEWSdOAAAvAYmHA>: Error: >

...c:123 > > #categories = > > fields = name args running_usecs bytes_in bytes_out > > #filter { > # field_key = wildcard > #} > } > > metric sql { > event_name = sql_query_finished > } > > metric auth { > event_name = auth_request_finished > fields = user transport error successful > } > > and get the following > > > [root at stargate dovecot]# doveadm stats dump > metric_name field count sum min max avg median stddev %95 > imap duration 370 2007904499 130 629...

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once. This is confirmed by monitoring queries made...

...secret ? comparisons: OAUTH2 JWT-token HMAC, imap-urlauth token, crypt() result. - auth: Several auth-mechanisms allowed input to be truncated by NUL ? which can potentially lead to unintentional issues or even successful ? logins which should have failed. - auth: When auth policy returned a delay, auth_request_finished event ? had policy_result=ok field instead of policy_result=delayed. - auth: auth process crash when auth_policy_server_url is set to an ? invalid URL. - auth: Lua passdb/userdb leaks stack elements per call, eventually ? causing the stack to become too deep and crashing the auth or ? auth-worker...

...secret ? comparisons: OAUTH2 JWT-token HMAC, imap-urlauth token, crypt() result. - auth: Several auth-mechanisms allowed input to be truncated by NUL ? which can potentially lead to unintentional issues or even successful ? logins which should have failed. - auth: When auth policy returned a delay, auth_request_finished event ? had policy_result=ok field instead of policy_result=delayed. - auth: auth process crash when auth_policy_server_url is set to an ? invalid URL. - auth: Lua passdb/userdb leaks stack elements per call, eventually ? causing the stack to become too deep and crashing the auth or ? auth-worker...

...d potentially log some user's password ? in the error message. - dict-sql: SQL prepared statements were not shared between sessions. ? This resulted in creating a lot of prepared statements, which was ? especially inefficient when using Cassandra backend with a lot of ? Cassandra nodes. - auth: auth_request_finished event didn't have success=yes parameter ? set for successful authentications. - auth: userdb dict - Trying to list users crashed. - submission: Service could be configured to allow anonymous ? authentication mechanism and anonymous user access. - LAYOUT=index: Corrupted dovecot.list.index cau...

...d potentially log some user's password ? in the error message. - dict-sql: SQL prepared statements were not shared between sessions. ? This resulted in creating a lot of prepared statements, which was ? especially inefficient when using Cassandra backend with a lot of ? Cassandra nodes. - auth: auth_request_finished event didn't have success=yes parameter ? set for successful authentications. - auth: userdb dict - Trying to list users crashed. - submission: Service could be configured to allow anonymous ? authentication mechanism and anonymous user access. - LAYOUT=index: Corrupted dovecot.list.index cau...