similar to: Issue with LMTP proxying and port number

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

Op 06/01/2019 om 17:02 schreef Steven Craig: > Thanks, its a weird one. > > On 1/6/2019 8:00 AM, Stephan Bosch wrote: >> >> 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

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 Sami, yes, see below. We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22 (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because it only happened after the update from 2.2.10->36. ?Just to understand it would be great. I'm actually checking out the configs now ... Our SQL userdb does not specify port. ?So I'm guessing this may be to blame? (This was

Op 06/01/2019 om 17:05 schreef Stephan Bosch: > > Op 31/12/2018 om 06:32 schreef Laz C. Peterson: >> Hello Sami, yes, see below. >> >> We run Dovecot at a different versions, mainly 2.2.10 (CentOS), >> 2.2.22 (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because >> it only happened after the update from 2.2.10->36. ?Just to >> understand it

> On 31 Dec 2018, at 0.43, Laz C. Peterson <laz at paravis.net> wrote: > > 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

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 > then used to send it to our internal mail servers on port 24. > > Besides

Thanks, its a weird one. On 1/6/2019 8:00 AM, Stephan Bosch wrote: > > 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 >>>

* Stephan Bosch <stephan at rename-it.nl>: > > > Op 08/05/2018 om 10:34 schreef Olaf Hopp: > > Hi, > > > > I had an email with 58 recipients in the "To" and 13 in the "CC" > > Delivering it from exim to dovecot lmtp panics (see below) > > Panic: file smtp-address.c: line 533 (smtp_address_write): assertion > > failed:

Op 31/12/2018 om 06:32 schreef Laz C. Peterson: > Hello Sami, yes, see below. > > We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22 > (Ubuntu) and now 2.2.36 (CentOS). ?The issue is weird, because it only > happened after the update from 2.2.10->36. ?Just to understand it > would be great. > > I'm actually checking out the configs now ... Our

On 04/23/2018 03:22 PM, Stephan Bosch wrote: > > > Op 20-4-2018 om 14:01 schreef Olaf Hopp: >> Hi (Stephan?), >> is it a new feature of dovecot 2.3 /pigeonhole 0.5 that a sieve "redirect" changes the envelope sender of >> a redirected mail or simply a bug ? >> >> A sends mail to B, B redirects to C >> C sees B (not A!) as envelope sender.

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

Hi, I had an email with 58 recipients in the "To" and 13 in the "CC" Delivering it from exim to dovecot lmtp panics (see below) Panic: file smtp-address.c: line 533 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p)) # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS

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

I'm trying to set an IMAP Flag with the detail part of an address, but getting an internal error: an 3 13:37:27 thebighonker exim[537]: 1eWoqt-00008f-4u <= ler at lerctr.org H=(lrosenman.local) [74.203.163.58]:4650 I=[192.147.25.65]:587 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA3 84:256 CV=no SNI="smtp.lerctr.org" A=dovecot_login:ler S=769 id=20180103193716.oofszdaxopnkgfvd at

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

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=

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.

Op 25/06/2018 om 21:42 schreef Stephan Bosch: > > > > Op 14/06/2018 om 22:24 schreef grupo correo: >> Hi, >> I need to use lmtp server proxy, to proxy a remote smtp server, the >> documentation says "It's possible to use Dovecot LMTP server as a >> proxy to remote LMTP or SMTP servers", but i do not find how to >> configure. Can anybody

https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.36.1.tar.gz.sig ??? * CVE-2019-3814: If imap/pop3/managesieve/submission client has ??? ? trusted certificate with missing username field ??? ? (ssl_cert_username_field), under some configurations Dovecot ??? ? mistakenly trusts the username provided via authentication instead ??? ? of failing.