similar to: LMTP Logging

I'm having difficulty with the doveadm who command on a multi-instance setup of dovecot. When I run the who command on the non-standard instance with the -m flag (to see their mail location), this happens: [root at wardentest3 dovecot]# doveadm -i mailtest user -m warden doveadm(root): Error: user warden: Initialization failed: Namespace 'INBOX.': Ambiguous mail location setting,

I'm seeing lots of: Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN)

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 are experiencing similar sporadic data timeout issues with dovecot 2.0.20 as in http://dovecot.org/pipermail/dovecot/2011-June/059807.html at least once a week. Some mails get temporarily deferred in the postfix queue since dovecot director lmtp refuses them and the mails are delivered at a later time. The problem applies to mails delivered to single users as well as distribution lists

I don't really need logging of successful local deliveries since the MTA provides enough data. I can't get rid of LDA delivery logs by setting deliver_log_format = All this does is produce an empty log message e.g. Apr 16 01:22:05 dserver dovecot: lda(user): Timo, would you consider inclusion of this patch which will skip logging deliveries if deliver_log_format is empty: ---

Updated (current) doveconf -n attached.... On Mon, Dec 25, 2017 at 04:33:16PM -0600, Larry Rosenman wrote: > FTR, this is being delivered via LMTP from Exim using the recommended transport / director. > > headers from one of my tests: > Return-Path: <ler at lerctr.org> > Delivered-To: ler at lerctr.org > Received: from thebighonker.lerctr.org > by

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

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

Hi all, are there any (dis)advantages in "connecting" dovecot and an MTA (in our case: exim) using LMTP over using other methods (e.g. the exim transports definitions that can be found in the wiki)? Thank you very much! Gruss/Regards, Christian Schmidt

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

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

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

On Thu, Feb 23, 2017 at 3:45 PM, Zhang Huangbin <zhb at iredmail.org> wrote: > > > On Feb 24, 2017, at 6:08 AM, Mark Moseley <moseleymark at gmail.com> wrote: > > > > * Do you use the perl poolmon script or something else? The perl script > was > > being weird for me, so I rewrote it in python but it basically does the > > exact same things. >

Per my earlier post about system and virtual users, I have everything working, but I'm seeing the following message, and wondering: 1) does it matter? 2) is there a way to suppress it? I have an Exim /etc/aliases entry that sends root to me. Jul 13 14:38:47 thebighonker dovecot: auth-worker(13055): Error: passwd-file /etc/passwd: User root has invalid UID '0' doveconf -n: # 2.2.31

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.