similar to: (Dis)advantage of using lmtp?

The correct way has to be one or the other: http://wiki.dovecot.org/LDA/Exim are mutually exclusive with http://wiki.dovecot.org/HowTo/DebianStable It appears that exim can either call dovecot's LDA or make the delivery itself. There may be good reasons to do it one way or the other. ---------------------------------------------------------------- Karl Schmidt

Dear all, I'm running a linuxbox with ' Dovecot<->Exim<->horde/IMP<-> Mysql ', this is a very good combination and works excellent for the system users. Now I want to change the configuration and authenticate against the mysql database from horde. That way it is much easy for me to create (virtual) mail users. I also want to use the mail alias of the horde users

Hello Timo, On 30.12.2015 14:24, Timo Sirainen wrote: >> On 30 Dec 2015, at 03:45, Christian Schmidt <christian.schmidt at chemie.uni-hamburg.de> wrote: >> >> Hello Timo, >> >> On 29.12.2015 19:25, Timo Sirainen wrote: >>> So looking up a header causes a crash. Can you send me one such mail >>> that causes this crash? >> I'll ask one

I have a problem with some messages passed from exim to dovecot lmtp service: From exim debug: using socket /var/run/dovecot/lmtp LMTP<< 220 mbox8 ready

On 23.03.2018 10:04, Arkadiusz Mi?kiewicz wrote: > On Thursday 22 of March 2018, Arkadiusz Mi?kiewicz wrote: >> I have a problem with some messages passed from exim to dovecot lmtp >> service: >> >> From exim debug: >> >> using socket /var/run/dovecot/lmtp >> LMTP<< 220 mbox8 ready >> LMTP>> LHLO mbox8... >> LMTP<<

Hi We tried to update our Dovecot Director-Ring to 2.3 (latest version) and had one problem/bug. When we try to deliver an email from Exim to a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process stays open forever and never closes. So after a few hours, we hit the LMPT-Process limit.? The problem only exists if the receiving Dovecot reports "Quota exceeded (mailbox for user

Dovecot now support lmtp, i'm try to tell exim transport to use lmtp driver = lmtp command = /usr/libexec/dovecot/lmtp batch_max = 20 user = 1000 group = 1000 But get error: May 12 13:00:43 selfip exim[13863]: [13863] 1OC7nF-00036i-Ue == vase at selfip.ru R=usr_aliases T=usr_aliases defer (-19): Malformed LMTP response after initial connection: Debug: none: root=, index=, control=, inbox=

Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24. Besides the update, nothing has changed in the config files.? The configuration has been working

Hi, I have a mailsystem where i have some local users with shell access and full home dirs which receive mail and also several SQL virtual users only for mail. With the virtual users, everything works fine. Mail is delivered via LMTP and also sieve works :) The SQL Lookup knows what to do with username at domain.com The problem is the system user. If exim delivers the mail to the lmtp

Just had a minor suggestion, with no clue how hard/easy it would be to implement: The %f flag in deliver_log_format seems to pick up the From: header, instead of the "MAIL FROM:<...>" arg. It'd be handy to have a %F that shows the "MAIL FROM" arg instead. I'm looking at tracking emails through logs from Exim to Dovecot easily. I know Message-ID can be used for

Hello All, I want to remove Dovecot (LMTP) information from Email Header, Please help me. I am using Dovecot 2.0.9 with Exim. Received: from XX.XXblue.co.uk by XX.XXblue.co.uk*(Dovecot) with LMTP id* XIuTJkJFxVLKTwAAG2fxGQ for <anant.saraswat at techblue.co.uk>; Thu, 02 Jan 2014 10:59:28 +0000 Received: from [210.7.64.2] (helo=[192.168.100.71]) by solo.techblue.co.uk with esmtp (Exim

Op 06/01/2019 om 11:50 schreef Stephan Bosch: > > Op 31/12/2018 om 23:59 schreef Steven Craig: >> Hello there, >> >> Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but >> after updating to version 2.2.36, our director servers are not able >> to proxy LMTP. >> >> We are sending mail from exim to the local Dovecot LMTP socket, which

I tried to use dovcots lmtp instead of dovecot-lda. postfix has in master.cf ... dovecot-lda -f ... -d ${user} to separate the user part from user at hostname.domain. So lookup of "user" succeeds in userdb (LDAP) done by dovecot-lda. I have always local addresses like to=<user at hostname.domain> postfix/lmtp[6579]: [ID 197553 mail.info] B3CDA66A16: to=<h0094slk at

Hi, what are the following messages supposed to tell me and does this indicate a problem? # systemctl status cyrus-imapd [...] master[3766]: unable to setsocketopt(IP_TOS): Operation not supported master[3766]: unable to setsocketopt(IP_TOS): Operation not supported [...] Exim says it can not connect to the lmtp socket even when selinux doesn?t get in the way. The configuration looks like

Hi all, This is the first time I use the dovecot mail list so I?m sorry if I forget something. My problem is that for some reason I can get public mailboxes to work. I have setup the directory Public, the folders and the cur,tmp and new folder in them: Public | |- .office3 | |- cur |- tmp |- new |- dovecot-acl Here is my dovecot conf: # 2.2.13: /etc/dovecot/dovecot.conf # OS:

Sorry for offtopic, don't know where to ask it after updating from `ubuntu` 18 to 20 started getting this on running golang binary from sieve rules file ``` Sep 17 08:54:00 lonjemail spamd[3231]: spamd: connection from ::1 [::1]:57844 to port 783, fd 5 Sep 17 08:54:00 lonjemail spamd[3231]: spamd: setuid to Debian-exim succeeded Sep 17 08:54:00 lonjemail spamd[3231]: spamd: processing message

Hi, I'm not sure if this is a deliberate design decision or a technical limitation that I've missed. Please briefly explain if so :). Or a bug or feature request? When LMTP receives a mail with a single recipient it adds a Delivered-To header. However if the message is delivered in a batch that header isn't added. At first I thought maybe the LMTP was doing something with hardlinks

Hello there, Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after updating to version 2.2.36, our director servers are not able to proxy LMTP. We are sending mail from exim to the local Dovecot LMTP socket, which then used to send it to our internal mail servers on port 24. Besides the update, nothing has changed in the config files. The configuration has been working great

Hello. I am migrating my servers to Ubuntu and have been having an issue with Dovecot authenticator service. Exim is set up to use dovecot-auth, anticipating the question whether exim binary was compiled with support of Dovecot authenticator, it was: --- # exim -bV Exim version 4.86_2 #1 built 05-Apr-2016 12:21:41 Copyright (c) University of Cambridge, 1995 - 2015 (c) The Exim Maintainers and

Hi I tried to get some logs: https://pastebin.com/Z8xVzpzW As you can see the process isn't shutdown and still in transaction as long dovecot is running. It destroyed the transaction when I stopped Dovecot. And this behavior only happens when the mailbox of user is full... Any Ideas how to debug this correctly? > So far, I haven't been able to reproduce anything weird at this end.