similar to: dovecot lmtp and drop privileges to specific user

Hello, After I upgrade dovecot 2.2.35 to 2.3.1 and pigeonhole 0.4.23 to 0.5.1 when I use sieve to forward a message to other address using "redirect :copy" I get this: (host server1.myserver.com <http://server1.myserver.com/>[private/dovecot-lmtp] said: 451 4.2.0 <chris at mydomain.com <mailto:chris at mydomain.com>> Execution of Sieve filters was aborted due to

I use dovecot-lmtp and postfix. When I send e-mail to 2 recipients (or more) at the same time and if one of them is over quota (or under quota and the message I send is bigger than his free space) mailq shows: -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 20B03336F22 26099 Thu Apr 19 18:02:47 support at example.com (lost connection with

Thank you for your reply. I use FreeBSD so no changes on the OS before and after the dovecot/pigeonhole updates. > On 4 Apr 2018, at 08:54, B. Reino <reinob at bbmk.org> wrote: > > Hello, > > The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. > > (if you need help with that ask again..

Hi, I have another problem with dovecot 2.3.1 on FreeBSD (smtpd is postfix 3.3.0). When one mail is sent with different recipients and the quota limit of one user is exceeded, the message will be delivered repeatedly to all users. The queue from postfix says: (lost connection with mailserver.foo.bar[private/lmtp-dovecot] while sending end of data -- message may be sent more than once) The

Here are some logs: Apr 3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: program `/usr/sbin/sendmail' terminated with non-zero exit code 75 Apr 3 23:25:35 server1 dovecot: lmtp(chris at coderz.gr)<47735><AUI6Aj/jw1p3ugAAPz4RRA>: Error: sieve: msgid=<DE90EB45-9B58-4679-9BCE-E2698773519E at cretaforce.gr>: failed to redirect

Hi all I'm facing an issue while running dovecot inside a singularity (https://sylabs.io/singularity/) container dovecot version is 2.3.4.1 (configuration below) running on debian buster, inside a container made with singularity version 3.4.2 unfortunately, when I try to start dovecot, it gives: Singularity test.sif:~> cat /var/log/mail.log Dec 30 17:23:38 testnode dovecot: master:

Hello, The new systemd service file has NoNewPrivileges set to true. You need to override that to false and then it should work again. (if you need help with that ask again.. I'm on the train now so I can't write much comfortably..) Cheers. On April 3, 2018 10:25:22 PM GMT+02:00, Christos Chatzaras <chris at cretaforce.gr> wrote: >Hello, > >After I upgrade dovecot 2.2.35

I use a helpdesk system that connects to dovecot using POP3 with SSL enabled to fetch the e-mails. After I upgrade to v2.3.7 the helpdesk randomly (some times it works, some times not) doesn't fetch the e-mails. If I configure the e-mail accounts with SSL/TLS disabled then it works. Any idea about this?

Hello, we're setting up a weird platform where every incoming email is passed from the MTA directly to a tool that then uses dovecot LMTP to deliver the message into the user mailbox. We are legally *not* allowed to run antispam on all the incoming messages, but only on some of them, as they are recognized by the aforementioned tool; but given that tool directly uses LMTP to delivers the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 2 Aug 2016, Michael Fox wrote: > Update: > > I was able to eliminate the /var/log/mail.err error messages (shown below) > by creating a userdb.quota-status and userdb.lmtp passwd-file. However, > since userdb.pop3 and userdb.imap will have different extra-fields values > for namespace (different namespace/xxx/inbox=yes

The service specific passwd-file userdb is causing quota-status and lmtp to fail. Using: userdb { args = ... /etc/dovecot/auth.d/%d/userdb.%s } I'm getting the following in /var/log/mail.err when I try to send/receive mail: Aug 1 15:46:57 n6mef-gw dovecot: auth: Error: passwd-file(mefpop at email.n6mef.org): stat(/etc/dovecot/auth.d/email.n6mef.org/userdb.quota-status) failed: Address

Hello, I am getting crash on lmtp for specific message on dovecot 2.3.2 See below the backtrace: Jul 02 22:54:20 Panic: lmtp(xxx)<172769><yL/kH0zXOlvhogIAF3haWw:3>: Buffer write out of range (23153 + 18446744073709551614) Jul 02 22:54:20 Error: lmtp(xxx)<172769><yL/kH0zXOlvhogIAF3haWw:3>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xcdfe4) [0x7f1fc8df9fe4] ->

Hi, I upgraded (in place upgrade, preserving my dovecot configs) to a newer release of ubuntu in order to gain access to slightly newer Dovecot release and be able to use Dsync for migration from Cyrus, here is my doveconf -n output: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-44-generic x86_64 Ubuntu 12.10 auth_debug = yes auth_default_realm = whatever.com auth_master_user_separator

Have you tried setting linux capabilities, like NET_BIND_SERVICE,CHOWN,SYS_CHROOT,SETGID? Have you checked the permissions of paths? I had to relocate the run dir with things like these && mkdir /var/dovecot \ && mkdir /var/lib/dovecot \ && (umask 027 ; mkdir /var/dovecot/login) \ && (umask 022 ; mkdir /var/dovecot/empty) \ && (umask

Hello list, we are using dovecot-lmtp for delivery to virtual users, and vmm[1] to manage them. 1. http://vmm.localdomain.org/ One nice feature of vmm is that every virtual user has their own UID/GID on the UNIX filesystem. There is no passwd entry, so no shell login, but each user effectively has a home directory and can run commands in isolation and with lowered privileges. This requires

Hello all, Is there a way to use LMTP (or LDA) so that maildir index and dovecot-uidlist are not updated? My setup is such that mail delivery sees user's maildir as write only. This setup works well when using postfix for mail delivery, but when I try to switch to dovecot LMTP the lmtp process wants to read the dovecot-uidlist and fails on insufficient privileges. Is there a way around this

Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

Hi, I'm using Dovecot 2.0.1, and I log to a custom syslog facility (local0) in the main configuration (I want a separate log file, but I want to make use of rsyslogd's capabilities). I overwrite the syslog facility for LDA (mail) to have all delivery related stuff in /var/log/mail.log, and that works fine. I tried to do the same for LMTP with protocol lmtp { syslog_facility = mail }

Hello, I tried to activate SSL on LMTP service, to secure connections between Postfix and Dovecot on my LAN, but Dovecot is not negociating a TLS session with Postfix. If I enforce TLS for LMTP at Postfix's side, communication between Postfix and Dovecot is not working. I put ssl = yes ssl_cert = </dovecot/ssl/ssl-LMTP.pem ssl_key = </dovecot/ssl/ssl-LMTP.key in section protocol