similar to: Dovecot logging

Hi, I am trying to integrate sieve with qmail-ldap. I can't get it to work, and deliver isn't logging anything to the log files (or syslog, if selected). Hence I have got no way to diagnose the problem. Any help appreciated. *root at debtwo:~# dovecot --version* 1.2.13 *root at debtwo:~# dovecot -n* # 1.2.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-3-686 i686 Debian squeeze/sid

Hi everyone, I'm using Postfix and Dovecot with dovecot-lda used for local delivery. I've successfully migrated from 1.2.13 to 2.0.0 however I have a little problem with dovecot-lda logging. With version 1.2.13, I use to log dovecot-lda to /var/log/dovecot-lda.log with world-writable mode. With version 2.0.0, postfix complains: "Can't open log file /var/log/dovecot.log:

Hi, i have this in /var/log/messages May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Timed out May 7 09:29:59 blade25 dovecot-auth: pam_ldap: ldap_result Can't contact LDAP server but i defined log_path and info_log_path in dovecot.conf "dovecot -n not show different values for "protocol lda"? Regards # dovecot -n # 1.0.10: /etc/dovecot.conf log_path:

Hello list, Testing lmtp deliver I can't constrain it to log all activity to separate file, like dovecot-lda does. Here is config: protocol lmtp { info_log_path = /var/log/dovecot/dovecot-deliver.log log_path = /var/log/dovecot/dovecot-deliver.log mail_plugins = acl quota trash virtual zlib expire sieve } protocol lda { info_log_path = /var/log/dovecot/dovecot-deliver.log log_path

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of

Hello, tl;dr: Is there a way to get dovecot's auth to log failed smtp authentications without having to switch on "auth_verbose"? postfix version 2.11.0 and dovecot version 2.2.12 I'm currently migrating my postfix+courier to postfix+dovecot and so far it's working as expected. Except for logging smtp login failures. Despite Postfix logging successful authentications (see

>From the wiki: log_path = Use this logfile instead of syslog(). /dev/stderr can be used if you want to use stderr for logging (ONLY /dev/stderr - otherwise it is closed). (I dont understand the above references to the use of stderr) info_log_path = For informational messages, use this logfile instead of the default (What exactly is an informational message, and what is the

Hi! On Thu, 31 May 2018 00:44:58 +0900, A. Schulze wrote: > When running multiple instances of dovecot on the same host (or running multiple docker container), > it is hard to distinguish logs from different processes: the syslog entries are all prefixed with the same identifier "dovecot" > It is hardcoded here: >

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

Hello everyone. I have dovecot version 1.2.8 installed from source. This morning I installed the sieve plugin to sort emails, and though the install reported no errors, the plugin doesn't seem to function, and no mention of it is made in the logs when I turn on verbose logging. dovecot --version 1.2.8 dovecot -n # 1.2.8: /usr/local/etc/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64

Hi gentlemen! After running for six month Dovecot 0.99.14 I decided to upgrade to 1.0rc15. Actually Dovecot is running under Slackware Linux 10.2 and I got the package from http://www.linuxpackages.net. Problems? Yes, one! When I try to startup Dovecot program hung: Fatal: Can't resolve address no: Name or service not known I'm not a Dovecot or IMAP guru and I can't imagine what

Hi, I'm testing dovecot 1.1.beta14 on two debian etch with drbd+ocfs2[active/active], I use qmail+vpopmail(userdb) and three front-end with openbsd 4.2 with dovecot 1.1.beta14 as proxy with passdb sql through vpopmail database. Is posible to add logs into vpopmail.vlog from proxys?, like "update vlog blah blah..." or in other sql database? I tried with post login scripting but I

Hi to all i'm running two Dovecot servers version 2.2.15 both Server A and Server B Server A is in production instead Server B is ready to start as a replacement My goal is replicate through doveadm backup command mails from Server A to Server B but when i execute following command in Server B error happens doveadm -vvv -D backup -R -u davide.marchi at mail.cgilfe.it imapc:

Hi, Not sure if this is relevant but having been running dovecot 1.1.4 for a long time (without any problem) I recently upgraded to 1.1.7 when I switched to SuSE 11.1 This is just running on my home server and it's a fairly standard fetchmail-procmail-dovecot setup. However I recently had an incident which I cannot quite explain. I suspect it could be a possible disk problem but I did

Hi, I can see those values correctly with the doveconf -nc command. Here is the part of output: bash-4.2# doveconf -nc /etc/dovecot/director.conf # 2.2.36 (1f10bfa63): /etc/dovecot/director.conf # OS: Linux 4.1.12-112.14.11.el7uek.x86_64 x86_64 Red Hat Enterprise Linux Server release 7.7 (Maipo) # Hostname: 69b492645b56 auth_debug = yes auth_default_realm = xxxxxxxxxxxxxxxx auth_verbose = yes

Hello! Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program. Do you think this is a good concept? For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the

Hi Marc, I can see the processes are running as a root in container environment. Do you think that still have issues ? Here is the processes running inside container: bash-4.2# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c

If you are running your container as root. You will not have the issues I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?) when needed, this is fine. PS. I would not recommend using internal logging, use something like this to log to the host or remote syslog. docker run -v /dev/log:/dev/log -it dovecot-proxy -----Original Message----- Subject: Re: Issue

It's working from the linux box and not the xp then it's not Yes I try making corrections and this probably accounts for the confusion and broken samba communication. I just never seem to be able to come up with a working working configuration. Exception: smbclient; I can mount the XP share in a directory on my Linux box or at least the last time I checked. I have to turn off the

Hello I use LDA Dovecot 2 with SIEVE as Postfix delivery agent and I occasionally get such message in syslog. info.log:Apr 13 12:39:40 lda(xxxxxxxx): Info: msgid=<4DA484FF.5060903 at gmail.com>: save failed to INBOX: Timeout while waiting for lock See below the doveconf -n trace Thanks for any info > # 2.0.11: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 8.2-RELEASE amd64