similar to: Submission / Postfix / XCLIENT

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.

Hello, I'm using version 2.3.4.1 and I have a fairly simple setup based on a submission server where I run dovecot and a relay server with postfix. The relevant part of dovecot's config is as follows (sanitized): hostname = submission.domain.local submission_client_workarounds = whitespace-before-path submission_relay_host = 192.168.1.1 <- postfix submission_relay_port = 25

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

??????? 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

Hi list, just a small issue with deliver_log_format. Although, the parameter is altered in the config and is correctly shown with "dovecot -n", deliver uses only its default log_format. > root at terra:~# dovecot -n | grep -e deliver -e "^#" > # 1.2.rc3: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.26-1-686 i686 Debian 5.0.1 > deliver_log_format: %m:%$:%f:%s

> 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 >

Per the instructions here http://wiki.dovecot.org/LDA and here http://wiki.dovecot.org/LDA/Postfix I set postmaster_address = postmaster at hardwarefreak.com in /etc/dovecot/dovecot.conf and mailbox_command = /usr/lib/dovecot/deliver in /etc/postfix/main.cf When I restart dovecot I get this: [07:17:00][root at greer]/etc/dovecot$ /etc/init.d/dovecot restart Restarting IMAP/POP3 mail server:

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 permit sending based on the certificates fingerprint. Thanks in advance Christian Von unterwegs aus gesendet -- R??ner-Network-Solutions Karl-Br?ger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil:

> 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, after inserting another sieve-rule, I get the following backtrace on deliver. The mail gets delivered into the Mailbox, but as deliver does not exit with 0, postfix bounces the mail. The additional rule is the same as all others in my .dovecot-sieve: > require ["fileinto", "include"]; > > if header :contains ["From"]

Hello all. I am reading the mailinglist for a long time now, and there was a thread i believe called webgui or something. In this thread there was a company i believe german, that was working on a dovecot appliance with a web based gui to administrate a dovecot mail server. The problem is i did not save the URL of that company. Does anyone know which company make the appliance. Or does

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

Hello I need to have a information popup will be send when my thunderbird's users connect to our server. Is there a function in Dovecot to do so ? Thank you

?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

On 8/20/20 2:56 PM, Admin Beckspaced wrote: > If postfix is handling your submission service you can have a look at > postfwd > > https://www.postfwd.org/ > > I use it to limit sending of emails, recipients, etc, etc Thanks for the suggestion! I am using Postfix as the relay host behind dovecot-submissiond. Unfortunately, unless I'm missing something, submissiond does not

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

Hi, Just found out that Postfix does not implement/support the AUTH=sender parameter. So, back to Dovecot, can we use variables in the submission_relay_user = submission_relay_password = then Dovecot will forward the username and password information of the current user to the Postfix submission service for authentication? Best regards, Jacky On 10/1/2019 10:46 AM, Jacky wrote: >

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

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