similar to: How to setup a dovecot lmtp proxy server ?

Hello, In my current setup, I uses two mailservers to handle the users connections, and my emails are stored on a distant server using NFS (maildir architecture) Dovecot is both my IMAP server and the delivery agent (LMTP via postfix) To avoid indexing issues related to NFS, proxying is enabled both on IMAP and LMTP. But when a mail is sent to users that are shared between the servers, I got the

Hi Timo, I'm writing to alert you that even in version 2.1. we have the error: "Can't handle mixed proxy/non-proxy destinations" when we write to two users: one existent and one not. The error occurs randomly. I configure LDAP query in the file : dovecot-ldap.conf in this way: pass_attrs = mail=user,userPassword=password,=proxy=y,mailHost=host, =proxy_timeout=600

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

Hi all, I have a setup of some nodes running Dovecot 2.0.13 and Postfix 2.5.6 with storage in NFS and authentication happening with PAM. Poking around in the wiki, I tried out different possibilities but now I am stuck -- and are hoping for your (enlightening) comments and tips. My planned setup for IMAP and LMTP is like this: IMAP ==== 1. A loadbalancer directs new sessions to a

FYI, we saw one panic on our director/lmtp-proxy yesterday. It's running dovecot v2.0.13, so it very well might have been fixed already.., but here it is anyway: Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Aug 31 11:33:31 loadbalancer1 dovecot:: lmtp(4119): Error: Raw

Hi, I have a timeout problem only when I have heavy load in my system. I have two director servers directing to 4 backend servers. The problem is when my smtp relays tries to deliver mail to my users via lmtp (proxied with director). In the smtp logs I have: Jun 12 11:41:18 xenon13 postfix/lmtp[4248]: 4433E5D5A0: to=<myuser at um.es>, relay=pop.um.es[155.54.212.106]:24, delay=31,

Hello everyone, I have set up postfix to deliver mails to dovecot (2.0.16) using LMTP. On the other hand, I've successfully configured the IMAP proxy setting in dovecot in order to be able to distribute mailboxes among different servers. I wanted to do the same proxy at LMTP level, but it's not working. If I put lmtp_proxy = no, then everything works ok (assuming the mailbox is local),

Hi, Director -> Backends -> NFS setup. Problem: Broken dovecot-uidlists because of our postfix LMTP delivery using a different address than the IMAP client lookups Error: Mailbox INBOX: Broken file dovecot-uidlist line 169: Invalid data: example: LMTP delivery: lmtp(info#domain.nl at mail.local) IMAP lookup: info at domain.nl doveadm director status info#domain.nl at mail.local

Hey all, I've upgraded from a working Dovecot 2.0.17 Proxy with a master user setup to Dovecot 2.1.3 and I've merged my conf settings from 2.0.17 into 2.1.3. I'm able to start up dovecot proxy and telnet localhost, however it creates the users home director on the proxy server instead of going to the backend dovecot server (which has already been successfully upgraded to 2.1.3 from

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, the lmtp service of our dovecot director installation quits with a segmentation fault if a lot of mails are simultaneously delivered. For example if the postfix mailqueue is filled (for whatever reason) and postqueue -f is run the lmtp service quits with a segmentation fault: Program terminated with signal 11, Segmentation fault. #0? o_stream_cork (stream=0x0)

Hi Aki, I also tried with changing the original ldap source to svr2. Although everywhere svr2 is configured, still mails keep being delivered locally on svr1. Do I need to configure more than 20-lmtp.conf? [@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#' lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins

Op 25-11-2017 om 13:00 schreef Tomislav Perisic: > Does anyone have any idea regarding this? > > On 17 Nov 2017 11:36, "Tomislav Perisic" <tomiperisic at gmail.com> wrote: > > Hi, > > We have 2 servers, server A and server B. > > Server A has: > > Postfix > dovecot-2.2.33.2-1.el6.x86_64 > > Server B has: > >

Hi, We have 2 servers, server A and server B. Server A has: Postfix dovecot-2.2.33.2-1.el6.x86_64 Server B has: dovecot-2.2.33.2-1.el6.x86_64 dovecot-pigeonhole-2.2.33.2-1.el6.x86_64 Server A receives email on postfix, dovecot then takes that email from postfix and proxies it to Server B Dovecot. Dovecot on Server B takes the proxied email and delivers it with lmtp to the user inboxes. The

Hi list, I set up dovecot as IMAP proxy using a master user to login into the backend and it works beautifully. ?? Next I set out to do LMTP proxying and I struggled (initially). I got the log message: Mar 17 11:23:44 mail postfix/lmtp[2665]: 99A3F219C8: to=<johnny at doe.com>, relay=10.15.1.2[10.15.1.2]:24, delay=5.1, delays=4.9/0.05/0.01/0.07, dsn=5.1.1, status=bounced (host

Hello, i am using the lmtp proxy and dovecot 2.0.6 When (in my case caused by an erroneous config in the backend lmtp server), the backend lmtp cannot find the user, the proxy dies with a signal 11. 220 backend Dovecot LMTP ready LHLO proxy MAIL FROM:<user at domain> 250-backend 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING 250 2.1.0 OK RCPT TO:<user> 550 5.1.1 <user>

Hi, I have configured 20-lmtp conf file to use proxy and into the protocol section i added: passdb { driver = static override_fields = proxy=y protocol=smtp port=25 host=x.x.x.x } But is not reading this configuration. I do not understand how is working. BEST regards El 25 jun. 2018 9:46 p. m., "Stephan Bosch" <stephan at rename-it.nl> escribi?: Op 25/06/2018 om 21:42

Excuse me, is a error a use args not override_fields. BEST regards El vie., 3 ago. 2018 15:46, Aki Tuomi <aki.tuomi at dovecot.fi> escribi?: > Hi! > > With static db, you should use args instead override_fields. > > Aki > > > On 03 August 2018 at 16:42 grupo correo <grupodecorreo10 at gmail.com> > wrote: > > > > > > Hi, > > I have

Op 1-12-2017 om 15:30 schreef Tomislav Perisic: > Hi, > > Thanks for replying. > > initially logging was done via syslog, and the custom log file for > mail.* facility was /var/log/maillog. Everything was logged normally > (dovecot login logouts, sieve scripts, extra debugging lines) but > nothing regarding LMTP. I would receive the email in my inbox but I > wouldnt

I'm trying to configure my proxy/director server, which proxies imap/pop/managesieve correctly already, to proxy LMTP to my backend message store server (dovecot+postfix already configured there) This is what I have so far: 10-auth.conf using auth-static.conf.ext instead of auth-ldap.conf.ext (switching to this made proxying imap/pop/managesieve work) 10-director.conf protocol lmtp {