search for: login_log_format_elements

Hi, login_log_format_elements does not seem to change the login logs. I have it set to the below setting and the word "home" does not even appear. Is there something I have to do to for this? Also I use ldap for authentication. [user at MB1 logs]$ doveconf -n | grep -i log debug_log_path = /home/user/apps/logs/...

When I ran /usr/local/sbin/dovecot, the variable login_log_format_elements from dovecot.conf was honored. Now when I run /usr/local/libexec/dovecot/imap-login from /etc/inetd.conf, it isn't. How do I get imap-login to write log lines that use login_log_format_elements for the format? This is dovecot-1.2.alpha3 soon to be alpha4. Thanks, Jonathan -------------- n...

Hi login_log_format_elements = user=<%u> method=%m rip=%r %k is it possible to get rid of the "proxy(test at testserver.rhsoft.net): started proxying to 127.0.0.1:143: " part because on a proxy-only server i know that and it is explicitly not listed in "login_log_format_elements" as well as for the...

Hi, could it be possible to log the TLS cipher suite as Postfix does? This is a typical TLS Dovecot log line: imap-login: Login: user=<user at acme.com>, method=DIGEST-MD5, rip=1.2.3.4, lip=4.3.2.1, mpid=19671, TLS, session=<Jsvr46wt2c1ScQfY> This is the Postfix equivalent postfix/smtp[59723]: Anonymous TLS connection established to mail.acmne.com[1.2.3.4]:25: TLSv1.2 with cipher

...the imap proxy. Is there an xsession standard that is different between the two, or just an oversight in the code? Both send the remote address/port, but only imap proxy sends the local address/port. This patch declares long variable %{real_rip} so that a backend server can declare a different login_log_format_elements login_log_format_elements = user=<%u> method=%m rip=%r lip=%l pip=%{real_rip} mpid=%e %c This is primarily useful for backend servers to log both the rip, lip, and in case of xsession, the real rip. I haven't done extensive testing yet, but as long as nothing does anything weird elsew...

Hi. I'm using nologin with own reason [1]. That works fine. For example pop3 client gets nice message like "-ERR [AUTH] Account is locked. Please contact support." Unfortunately maillog lacks information details about why user was not allowed to log in. pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<testuser>, method=LOGIN, rip=1.1.1.1, lip=2.2.2.2,

...server with no problems so far. The reason I wanted to try 2.2.19.rc1 was to get access to the %{listener} variable in the auth phase so I can modify the SQL password_query according to which unix_listener is being queried. According to the docs, "These variables work only in Dovecot-auth and login_log_format_elements setting". I can confirm that %{listener} works in login_log_format_elements but it does not work if I use it in my SQL auth query. My logic is as follows: I create multiple listeners for different SASL authentications in 10 -master.conf service auth { unix_listener auth-userdb { mod...

...9;vmail' user and authentication is via checkpassword using user%domain (ie email, just with % instead of @). So dovecot is recording _all_ logins as: imap-login: Login: user=<vmail>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured I have the following log format specified: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c I have also tried: login_log_format_elements = user=<%n@%d> method=%m rip=%r lip=%l %c However, this results in a log file entry of: imap-login: Login: user=<vmail@>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured How do I c...

...ation. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15: /etc/dovecot/dovecot.conf # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 base_dir = /var/run/dovecot/ disable_plaintext_auth = no lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mbox_lock_timeout = 15 mins mmap_disable = yes passdb { ? driver = pam } protocols = imap pop3 service anvil...

...y trusts whoever invoked it (imap-login), it doesn't authenticate the user either. Timo didn't want any crypto or authentication code, or to link against any such libraries in the imap process itself. Your imap-login process does show TLS and this can be logged in the log file as well, see login_log_format_elements and the variables %c and %k -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180713/b61023f0/attachment-0001.html>

for nomal operations * login_log_format_elements = %r %m %k * login_log_format = %$: %s would be perfect because "proxy(h.reindl at thelounge.net)" contains the username *but* in case of auth errors "Disconnected (auth failed, 1 attempts in 2 secs)" does not show the username - hence currently there exists no way to...

...t; >> /usr/sbin/dovecot -n >> # 2.1.15: /etc/dovecot/dovecot.conf >> # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 >> base_dir = /var/run/dovecot/ >> disable_plaintext_auth = no >> lock_method = dotlock >> login_greeting = SpamZapper Email ready. >> login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c >> mail_debug = yes >> mail_fsync = always >> mail_location = maildir:~/Maildir >> mail_nfs_index = yes >> mail_nfs_storage = yes >> mail_privileged_group = mail >> mbox_lock_timeout = 15 mins >> mmap_disab...

...tion = yes # Number of login processes to keep for listening new connections. login_processes_count = 3 # Maximum number of login processes to create. login_max_processes_count = 8 # Greeting message for clients. login_greeting = Dovecot ready. # Space-separated list of elements we want to log. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. login_log_format = %$: %s ## ## Mailbox locations and namespaces ## # Location for users' mailboxes. mail_location = mbox:/home/mail/%u:INBOX...

...o far. The reason I wanted to try 2.2.19.rc1 was to get access to the > %{listener} variable in the auth phase so I can modify the SQL > password_query according to which unix_listener is being queried. > > According to the docs, "These variables work only in Dovecot-auth and > login_log_format_elements setting". I can confirm that %{listener} > works in login_log_format_elements but it does not work if I use it in > my SQL auth query. The docs were wrong - fixed now. Although I suppose auth could also have that.. > Now I want to use %{listener} in my SQL password_query in a case &...

We have multiple logins assigned to single mailboxes, so we can give one login to different devices. Does this cause a problem with mailbox guids in solr or is the ID stored within the indexes and not related to username.

...uth failed, 1 attempts in 2 secs): user=<testuser>, > method=LOGIN, rip=1.1.1.1, lip=2.2.2.2, session=<yIsRftBBmsrB7y2h> > > Is it possible to log "reason" there, too? (whether it is default/internal > dovecot reason or my custom one). Does it work if you add: login_log_format_elements = $login_log_format_elements reason=%{passdb:reason}

Hi. I have an auth plugin where an extra_field is filled. Somewhere, in login process I need to log the authentication command and the extra_field, I was trying to do it in login-common/client-common.c, adding a new variable to login_log_format_elements and trying to get the fileld from environment, but, I could not find any way to do it, the getenv returns null everytime. Anyone can suggest something to do it ? Is there a way that I get the extra_fields from request in login process ? Thanks -- Alexandre *Estanislau* Puhl - PX3D1363 alexandre...

I have my login log format set like so: login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c When I log in using a full email address, though, I only get the username part of the address: Jan 24 13:28:29 node7 dovecot: pop3-login: Login: user=<justin>, method=PLAIN, rip=137.118.2.60, lip=137.118.7.247 Jan 24 13:28:30 node7 dovecot: PO...

Hello. Today one user lost Sent Items folder, seems he deleted it, but I want to be sure. But how? Right now I'm using: login_log_format_elements = %u [%r] %m %c What should I use to see in logs information about created/deleted folders etc? -- Mart

....org> from=postmaster at example.org: stored mail into mailbox 'INBOX/postmaster' http://wiki2.dovecot.org/Variables leads me to the assumption that %{session} works "everywhere" and for deliver_log_format too. Is deliver_log_format variable expansion handled differently from login_log_format_elements and mail_log_prefix? Regards Daniel -- https://plus.google.com/103021802792276734820