similar to: Submission service, XCLIENT and HELO

service submission-login { ? inet_listener submissions { ? ? haproxy = no ? ? port = 465 ? ? reuse_port = no ? ? ssl = yes ? } } Shouldn't the port be 587 here? My config file looks like: service submission-login { ? inet_listener submission { ??? #port = 587 ? } } The # comment must also mean something.. On 7/27/19 3:21 PM, Jean-Daniel via dovecot wrote: > > >> Le 27

> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit : > > On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote: >> Hello, >> >> I'm having trouble configuring the submission proxy. >> >> I have configured the submission service as follow: >> >> submission_host = smtp.example.com >>

Hi all, while testing the new Dovecot Submission Proxy feature, which we greatly appreciate and have been anticipating for a long time, some issues occured. Dovecot is unable to submit mails via XCLIENT: < XCLIENT ADDR=185.115.176.12PORT=39074 > 501 5.5.4 Bad ADDR syntax: 185.115.176.12PORT=39074 Postfix is unable to parse the XCLIENT command from Dovecot submission proxy, as a

Hello, I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug which has been fixed in 2.3.6 is hitting me: lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server https://github.com/dovecot/core/commit/5d03f39b345127b80d145ee90772739baa7ab810 so I was wondering if there is any workarounds? Maybe like disabling the XCLIENT command from the config file

> On 24 May 2019 10:52 mabi via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I am running Dovecot 2.3.5 package on OpenBSD 6.5 and it looks like this bug which has been fixed in 2.3.6 is hitting me: > > lib-smtp: client: Fix infinite loop in XCLIENT command interaction with server >

Hi, Currently, Dovecot Submission doesn't forward NAME attribute when XCLIENT is enable: Received: from server.example.org (localhost [1.2.3.4]) (Authenticated sender: test at example.org) by localhost (Postfix) with ESMTPA id AAAAAAAAAA for <user at domain.com>; Fri, 8 Mar 2019 12:28:02 Postfix adds a header with the sender IP address (1.2.3.4), but with localhost as hostname.

??????? Original Message ??????? On Friday, May 24, 2019 10:40 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > Try setting login_trusted_networks= Thank you Aki for your answer. Unfortunately on my Dovecot mailbox backend servers I already have login_trusted_networks set to the IP of my Dovecot LMTP proxy server. > or just upgrade to 2.3.6? I was hoping not to have to

On 24.5.2019 12.22, mabi via dovecot wrote: > ??????? Original Message ??????? > On Friday, May 24, 2019 10:40 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> Try setting login_trusted_networks= > Thank you Aki for your answer. Unfortunately on my Dovecot mailbox backend servers I already have login_trusted_networks set to the IP of my Dovecot LMTP proxy

> On 24 May 2019, at 12.22, mabi via dovecot <dovecot at dovecot.org> wrote: > > ??????? Original Message ??????? > On Friday, May 24, 2019 10:40 AM, Aki Tuomi via dovecot <dovecot at dovecot.org> wrote: > >> Try setting login_trusted_networks= > > Thank you Aki for your answer. Unfortunately on my Dovecot mailbox backend servers I already have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello For some reasons, I need to encode in mono a stereo wave file, as with the --downmix option from oggenc. I searched in speexenc man page and in the on line documentation, unsuccessfully. Of course I could first use something like sox to down mix my file, but it would be more practical to have an option directly in speexenc. - -- RIQUER

Hi, there are two problems in devX11.c. The one is an undocumented nuisance and the other isn't a bug until you try to embed an X11 device in another window (think tktoplevel() in tcltk package...). Let's take a look at locator() first: Assuming you call locator() with a current X11 device, this call is handled in X11_Locator (src/unix/X11/devX11.c). When you have one window open and

?Hi, > Am 18.08.2019 um 16:52 schrieb Stephan Bosch via dovecot <dovecot at dovecot.org>: > > ? > >>> On 18/08/2019 10:09, Christian R??ner via dovecot wrote: >> Hi, >> is there some configuration parameter in Dovecot, which sends a TLS client certificate to the SMTP server? I would need this to have XCLIENT enabled and TLS with Postfix. This way I could

Hello, after migrating from self-compiled Dovecot 2.3.3 to Dovecot 2.3.8 from the repository (Ubuntu 18.04 LTS "Bionic" packages) I have issues with the submission service. If I send an email, it will not be forwarded and I get the following error message: Oct 11 09:29:01 srv2 dovecot: submission(hativ at example.com)<15819><XFnL eJ2U0rgqAoEMwMAIoDQqhHgB7k+O>: Panic: file

Hi, For the upcoming 2.3 development, I'd like to re-suggest this: It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. (like a proxy) * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) Often these two uses cases have a

Dear R developers, I've been experimenting with embedding R X11 windows into another application using KDE's QXEmbed on linux. Attempting to do so will crash R (with R 2.4.0, trunk, and I know the bug has been around in prior versions). I used to think this was related to bug #848, but I'm not sure, if / how the solution suggested there still applies to current versions of R.

I just committed a couple of features that will make life easier for some types of proxying setups: 1. IMAP proxying has already for a while supported sending local/remote IP/port to backend server, which can use it for logging and other purposes. I've now implemented this for POP3 as well, although only the remote IP/port is forwarded, not local IP/port. I implemented this also for LMTP in

Hi, It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) However... trustwise, this is trusting two different entities. The first case you put trust in the host. In the second

We are pleased to release v2.3.10 of Dovecot. Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.10.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.10.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * Disable retpoline migitations by default. These can cause severe

We are pleased to release v2.3.10 of Dovecot. Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.10.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.10.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * Disable retpoline migitations by default. These can cause severe

When using dovecot (2.1.5) sasl with postfix (2.8.4) behind nginx smtp proxy I am seeing a ton of errors of the form: postfix/smtpd[7731]: warning: unknown[192.168.0.6]: SASL LOGIN authentication failed: Connection lost to authentication server Nothing is printed by dovecot in the logs regarding the error. It seems that dovecot just hung up on postfix. (side note: no, can't use xclient