similar to: LDA null logging patch

Hello, seems that LDA ignores deliver_log_format (still log with format: "msgid=%m: %$") # 1.2.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.31 x86_64 Debian squeeze/sid xfs log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: none listen: none disable_plaintext_auth: no login_dir: /var/run/dovecot/login

Hi, I've been trying to build a password forwarding proxy to Gmail without success... The SSL connection to Dovecot is happening no problem (as far as I can tell), but for some reason the conversation between Dovecot and Gmail is getting timed out. I know this is supposed to be simple... :-( But could somebody please give me some help by pointing what I'm not doing right? No matter

Hey, i have an question about the deliver_log_format. My log looks sometimes like: Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>: msgid=<20201001073801.628713AC05DC at myserver.com>: saved mail to INBOX The deliver_log_format settings are still on default. Are somebody able to explain me this part of the log message?

Hi all, I'm using Postfix + Dovecot with system users (/etc/passwd and NIS) + deliver + cmusieve; Here are some relevant lines in conf files : /etc/postfix/main.cf ... mailbox_command = /usr/lib/dovecot/deliver ... /etc/dovecot/dovecot.conf ... protocol lda { postmaster_address = postmaster at lri.fr mail_plugins = cmusieve deliver_log_format = msig=%m :

Hi to all, i have dovecot 2.2.5 and i have implemented lda rejection through quota full this is my dovecot conf protocol lda { mail_fsync = optimized auth_socket_path = /usr/local/var/run/dovecot/auth-userdb deliver_log_format = msgid=<%f>-<%s>-%m: %$ hostname = mail.cgilfe.it info_log_path = /var/log/dovecot/dovecot-deliver.log log_path =

I have been trying to get the virtual domain and mailboxes working on an newly built Ubuntu 10.04 server and am stuck on this error. System is using a postgres database and PostfixAdmin. Thanks in advance for any help. Dave ==> /var/log/mail.err <== Jan 16 13:21:26 radius dovecot: deliver(dave at mydomain.com): Fatal: postmaster_address setting not given ==> /var/log/mail.log

On 9/17/19 5:35 PM, Richard W.M. Jones wrote: > Test both the TLS enabled and fallback paths. > > nbd-server doesn't appear to support TLS at all, and qemu-nbd is known > not to allow fallback to unencrypted, and therefore it only makes > sense to test nbdkit at the moment. > --- > .gitignore | 4 ++++ > +interop_nbdkit_tls_certs_allow_enabled_SOURCES =

Hi, # 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-45-server x86_64 Ubuntu 10.04.4 LTS deliver_log_format = mailbox: deliver: session=<%{session}> msgid=%m from=%f: %$ produces log messages always containing "session=<session}>", like this one: Feb 24 09:22:09 10.129.3.233 dovecot: lmtp(3484, user at example.org): mbnWK6/NKVGcDQAAiWCYmA: sieve: mailbox: deliver:

Hello everyone. I'm running dovecot (1.2.9) with postfix (2.7.0) on an ubuntu 10.04.1. I'm hosting mail for several domains and using the dovecot local delivery agent. Everything has been working great. However, today I set up a sieve script to send out-of-office replies (vacation) for one of our users. I tested it and got the response just fine. However, when looking at the

Recently configured postfix to use the dovecot lda as I wanted to use sieve. Got that working a few days ago but noticed that I wasn't getting any emails to aliases. Checked the logs and saw messages like: Mar 1 08:19:59 carson postfix/lmtp[16949]: 0DCD22016BE: to=< sales at example.com>, relay=carson.example.com[private/dovecot-lmtp], delay=0.07, delays=0.01/0.01/0/0.04, dsn=5.1.1,

Hi list, just a small issue with deliver_log_format. Although, the parameter is altered in the config and is correctly shown with "dovecot -n", deliver uses only its default log_format. > root at terra:~# dovecot -n | grep -e deliver -e "^#" > # 1.2.rc3: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.26-1-686 i686 Debian 5.0.1 > deliver_log_format: %m:%$:%f:%s

Hello list, I'm really hoping someone can point me in the right direction on this. I set up a server using Postfix with LDAP lookups to Active Directory. Postfix delivers to maildir. Dovecot IMAP and POP are working correctly using PAM Kerberos to authenticate via Active Directory. I want to add spam filtering, so I'm trying to set up Postfix to use dspam which is then supposed to use

I was a little surprised to find that LIBNBD_TLS_ALLOW worked out of the box, so I had to examine the logs whereupon I saw the magic message ... libnbd: debug: nbd1: nbd_connect_command: server refused TLS (policy), continuing with unencrypted connection I don't believe this path has ever been tested before. It's possible the tests could be improved if they actually checked for this

Hi list, I am configuring a samba server as a PDC (called DSERVER). I have follow some good docs to build my smb.conf file (see below). However, my server does not works correctly: when I execute smbclient, I don't find my workgroup (SOCINFO) alghouth I activated the wins support. [adel@grid007 ~]$ smbclient -L localhost -U root Password: Domain=[DSERVER] OS=[Unix] Server=[Samba

Oh wait, you crossposted to the postfix list. Please keep the discussion there going, you have a postfix issue, not a dovecot one ;) Tom On 02-03-17 09:40, Tom Hendrikx wrote: > Hi, > > Typically, postfix should resolve the aliases into user accounts that > dovecot knows before you even start delivering to dovecot. You probably > messed something up in the postfix config that

Test both the TLS enabled and fallback paths. nbd-server doesn't appear to support TLS at all, and qemu-nbd is known not to allow fallback to unencrypted, and therefore it only makes sense to test nbdkit at the moment. --- .gitignore | 4 ++++ TODO | 3 --- interop/Makefile.am | 54 +++++++++++++++++++++++++++++++++++++++++++++ interop/interop.c | 30

A summary of answers I got to the questiosn I posed. > Is there a reason I should prefer LMTP over LDA for local delivery? Thanks for the responses I received. The benefits reported were more/better information logging, and service isolation. Also, one significant advantage not mentioned for LMTP was that one delivery failure to multiple recipients can be disambiguated; LDA can only return

I use a lot of plus-style addresses (me+stuff at example.com), except I use underscore as the separator rather than plus (me_stuff at example.com). My mail logs are full of messages where dovecot looks for a mailbox named "stuff", fails, then delivers to my inbox. Is there a way to turn that off so that dovecot automatically delivers to my inbox? Thanks! Here are the details: >

Please ... any info on how to proceed??? After I made sure it had the correct sha256sum, and after I burned it to DVD, and and dd'd the DVD back to a temp file and again checked the sha256sum of the temp file, all was OK. Same sha256sum. So, I rebooted the machine and it booted up from the DVD. I got a message that it was not using VNC, Then after that immediately an error came out saying

We uograded our dovecot from version 2.1.10 -> 2.10.12, but within the first hour of use, dovecot-lda would segfault during delivery. This left a lock file lying around causing the user's mail readers to hang; much hilarity ensues. All further deliveries to the same user will result in a crash. The only thing that fixes this condition is to blow away the user's INBOX cache index.