similar to: LMTP proxying strategy with multiple recipient delivery

On 2012-04-05 4:18 AM, Thomas Leuxner <tlx at leuxner.net> wrote: > Also with 2.x you may want to use LMTP rather than the LDA Piping. > > http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP I am preparing to convert my main client's postfix_courier-imap setup to dovecot 2.1, which currently just uses the postfix virtual delivery agent... Does anyone know if the use of LMTP

On 2014-01-08 14:32, Charles Marcus wrote: > On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>> a single RCPT TO. You can force a single RCPT TO from Postfix side by >>>> setting

* Reindl Harald <dovecot at dovecot.org>: > lmtp_destination_concurrency_limit on postfix side It's not a postfix issue. postfix is merely reporting what Dovecot said. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer

I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 <recipient at backup.invalid> Too many concurrent deliveries for user (in

Am 06.03.2015 um 14:44 schrieb Ralf Hildebrandt: > I updated dovecot today and all over a sudden I'm getting: > > Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=<recipient at backup.invalid>, relay=127.0.0.1[private/dovecot-lmtp], > delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 >

Hi all, I have a Dovecot setup (2.1, I will switch to 2.2 soon) with one Director and 2 backend servers. When my MX server (Postfix) tries to deliver mail to Dovecot via LMTP, it often gets an error "451 4.4.0 Remote server not answering (timeout while waiting for reply to DATA reply)" from the Director. Service LMTP is configured with "client_limit = 1" on Director en

Hi, I've upgraded a mailstore from Debian Jessie (aka oldstable) with Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1 today. It worked pretty well, except that we're seeing error messages very similar to this old thread https://dovecot.org/pipermail/dovecot/2015-July/101396.html It appears to be happening when a mail with multiple recipients on this message store is

On 4/28/2015 1:40 PM, Tobias Franz?n <lists.zxinn at otaking.se> wrote: > On 2014-01-08 14:32, Charles Marcus wrote: >> On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >>> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>>> a single RCPT TO. You

Hi, I have a problem with my postfix/dovecot configuration, I can't receive mail from outside, i can send a mail from my mail to myself and others, but i can only receive one i send from myself, but when it comes from outside my domains, it dosn't work. Thaks for your help ! Here is my conf : ----------------------------------------------------------------- DOVECOT

I'm resurrecting this again because I'm getting pretty close to possibly being ready to install a brand new dovecot server (finally), but I still need for dovecots LMTP to add the x-original-to header. So... was this completed quietly, or is support for it still not there? Thanks, Charles On Tue Apr 28 2015 15:27:07 GMT-0400 (Eastern Standard Time), Charles Marcus <CMarcus at

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username at domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly.

How to send a test message directly to lmtp, to test proxying?

Hi All, is there any way to enable logging of users' IP address in dovecot director host? It actually logs only: Sep 14 07:32:29 mailgw-lb dovecot: lmtp(17615): Connect from xx.xx.xx.xx Sep 14 07:32:29 mailgw-lb dovecot: lmtp(17615): Disconnect from xx.xx.xx.xx: Client quit Thanks Luca

Hi all, we are experencing some, may be strange, slowness in our dovecot/postfix mail system. We have three dovecot 2.0.1 server with LMTP, POP3 and IMAP enabled. Three shared OCFS2 filesystem are used for mail storage. We have too a load balancer based on dovecot director in front of these three server. Our SMTP cluster receives mail and send by LMTP to load balancer. Everything work flowless,

Hello! I'm having crashes with LMTP delivery when user is over quota on the latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. I see the issue has been fixed on January 17, but it doesn't seem to have made it into 2.3.0.1 (I compared with the source from https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz).

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, just setting up mail hub with Postfix & Dovecot I have found BUG in LMTP implementation. * assumptions - latest stable Postix & Dovecot, - Postfix delivers via Dovecot LMTP (virtual_transport = lmtp:127.0.0.1:24), - Dovecot userdb & passwd lookups are made via custom checkpassword interface, - each user (email account) has different UID/GID * description LMTP process must

I found this[1] thread that describes the same problem with dovecot-LDA, but the solution (add X-Original-To: header) has no effect with LMTP. My sendmail LMTP configuration: FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp') Sendmail's address test indicates that sendmail is providing user+detail to LMTP (see below). Except for this problem, dovecot, LMTP, and sieve

Hi Timo, hi all, after upgrading my server (both backends and load balancer) to 2.1.2 (from 2.0.17), I'm getting a log of login processes crashed in load balancer. Log lines are like: Mar 20 10:05:45 mailgw-lb dovecot: pop3-login: Fatal: master: service(pop3-login): child 27764 killed with signal 11 (core dumps disabled) Mar 20 10:06:17 mailgw-lb dovecot: imap-login: Fatal: master:

Hi all, I''ve just spent some time going through trying to get mongrel & apache 2.0 working with mod_proxy. I thought I''d share what I''ve found in case someone is going through the same exercise. Of late, I''ve been using mongrel (lovely, btw) to run my rails apps. Since I have a couple of different rails apps running on the machine, I thought it be nice to