similar to: protocol specific AuthDatabase Queries

hi- i have a configuration in which i'm using different passdb/userdb settings for each of imap, lmtp and smtp [without getting too far off on a tangent, this is so ldap group membership can be used to independently control authorization for receiving [lmtp], retrieving [imap], and sending [smtp/postfix] of email. each passdb/userdb uses a different search filter.] when i use this as my

Hello, when trying to set up a migration scenario from my old mailbox-servers to my new dovecot-cluster, I get a coredump from dovecot/lmtp when proxying mail-delivery to more than one recipient on the old mailbox-server. My setup: 3 director-hosts (Debian stretch) are proxying to a pair of replicator-hosts and during migration also to the old mailbox-server. For migration the not-migrated

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Here is my setup: dovecot - 2.2.11 pigeonhole - 0.4.2 qmail I was trying to create a vacation message, but after the sive script has been created and I was checking the logs I saw some strange errors: DOVECOT LOG Jun 18 16:52:24 lda(portase.florin at medianetork.ro): Error: lmtp client: connect(medianetork.ro, 25) failed: Connection

Hello, I've just installed Dovecot from the http://xi.rename-it.nl/debian/ repository. But I have a problem with the mdbox Format. When the home folder is empty Dovecot should create the folder structure if the first mail arrived or the user logs in the first time. But I get following error: Sep 16 12:30:41 smtp dovecot: lmtp(31244): Connect from local Sep 16 12:30:41 smtp dovecot:

https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz.sig Some random notes: - This release is signed with a new PGP key 0x18A348AEED409DA1 (which is signed by the old key). - This fixes several compiling issues reported for the 2.3 release candidate. Also a few other fixes mainly for submission server and doveadm server. - We're still

https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.0.tar.gz.sig Some random notes: - This release is signed with a new PGP key 0x18A348AEED409DA1 (which is signed by the old key). - This fixes several compiling issues reported for the 2.3 release candidate. Also a few other fixes mainly for submission server and doveadm server. - We're still

Hi @all, on Saturday I upgraded two dovecot servers from squeeze to wheezy and dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade everything worked fine at first. On Sunday Morning I recognized these errors (they occured after a reload for logging purpose on midnight) on one server: director: Error: Ring SYNC appears to have got lost, resending After reloading/restarting

Hi to all, I have tryed a few days to configure postfix/dovecot to run into a VPS machine (CentOs) -->The machine has 2 domains (but more in the future) -->i want info at mail.domain1.com and info at mail.domain2.com to be seperated mailboxes -->i want to use lmtp protocol to connect dovecot with postfix -->It will be perfect if i can use the system users for authentication

I'm using dovecot in a multi server setup. Two directors forward pop3, imap and smtp to backend dovecots with their central storage on NFS. Yesterday I stumbled upon these log lines: 2019-11-18 20:17:51 lmtp(17274): Info: Connect from 172.22.1.6 2019-11-18 20:17:51 lmtp(17274): Panic: file smtp-client-connection.c: line 1142 (smtp_client_connection_established): assertion failed:

Hi, i have configured my dovecot-proxy with "shutdown_clients = no" and "service_count = 1" for a "default_process_limit = 5000" and "default_client_limit = 25000". I don't know if this is a prefered setup for so many users/concurrent sessions but so i can reload my dovecot without disconnecting all sessions. The main problem are pop3 sessions - if i

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

Op 20-10-2017 om 4:23 schreef Reuben Farrelly: > On 18/10/2017 11:40 PM, Timo Sirainen wrote: >> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> >> wrote: >>> >>> I haven't been tracking dovecot-2.3 until now, but I've just given >>> it a quick run, and there are a few things that may need some >>> attention.

Hi all, I'm running two directors with lmtp proxy as relay transport for my mail exchangers. relay_transport = lmtp:inet:dovecot-directors.example.net dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4 Now, .3 is down and Postfix tries to deliver it to .4 but this connection gets a timeout: (delivery temporarily suspended: connect to 172.17.1.4[172.17.1.4]:24: Connection

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 Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also

You probably need to increase ulimit -n Aki On 23.08.2017 14:10, Patrick Westenberg wrote: > Hi @all, > > after re-installing one of my two frontends/proxy-servers I get the > following error messages after some time (sometimes after 1h, sometimes > after 24h): > > > 11:23:55 imap-login: Error: socketpair() failed: Too many open files > 11:23:55 imap-login: Error:

Hi @all, I have a 3 server setup (MX ==LMTP==> Proxy ==LMTP==> Backend). After upgrading to 2.2.18 I was able to use LMTPs from MX to the proxy but not from the proxy to the backend: Received: from mf01.example.net ([172.17.1.5]) by mb01.example.net (Dovecot) with LMTP id T+LnDWrvcVWDSwAAJnBBGg for <patrick at example.net>; Fri, 05 Jun 2015 20:50:58 +0200 Received: from

Yes I am running sendmail next to dovecot on backend servers. That works ok. I have some problems with re-routing mail in a proxy setup. -----Original Message----- To: Marc Roos; dovecot Subject: Re[2]: Lightweight LMTP daemon to avoid overkill MTA Hi, I was unclear in my question. The spam filter is only able to deliver mail over SMTP, not over LMTP.. So I would still need some kind of

Hello, are you using systemd? May be you have to edit unit-file for dovecotservice and increase filelimit LimitNOFILE=infinity Hajo Am 23.08.2017 um 14:21 schrieb Patrick Westenberg: > I haven't done this on the old, working machine. > > So there must be a difference between Debian 7 and 9 how open files are > handled? > > Regards > Patrick > > > > Aki

Maybe nice to share some details? -----Original Message----- To: Marc Roos; dovecot Subject: Re[4]: Lightweight LMTP daemon to avoid overkill MTA I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable. Met vriendelijke groeten,