similar to: Workaround for infinite loop in XCLIENT command bug

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

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

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

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

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`ve got a question about Dovecot-Director and (Manage)-Sieve: is there any possibility to pass-through the original IP-address to the backend server? In this case I try to pass-through the IP-address of a webmail server. I`ve looked for a solution in different forums and tried it with the parameter "login_trusted_networks", however no success. The above solution is working

I have a proxy setup for pop/imap. The proxies are defined in login_trusted_networks = x.x.x.x and for the imap it works fine but for pop3 connections displays the ip address of proxy IP... Dovecots are both 1.2 from the debian repo deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-1.2 main thanks -- View this message in context:

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

I'd like to get the IP-address of the webmail-klient logged in my maillog (for being compliant with coming data retention policies). I've noticed that with login_trusted_networks pointing at my dovecot directors, we get rip=client-ip logged on the backends. How is the proxy providing this to the dovecot backends? Anybody know what magic we need to implement in our webmail-solution to be

On Tue, 9 Oct 2018 12:08:00 +0200 Sami Ketola <sami.ketola at dovecot.fi> wrote: > How do you deliver then mails to the server? > > also mbox is very unoptimised mailbox format for this. Each time mail is deleted from mbox mailbox the whole mbox while needs to be rewritten to remove the mail. OpenSMTPD and Dovecot run on the same machine. OpenSMTPD receives incoming mails and

what does the output of: netstat -n | grep :587 run as root, show you? the -p will give the program and pid. > Date: Wednesday, July 11, 2018 21:51:09 +0000 > From: Larry Rosenman <larryrtx at gmail.com> > > Yep, you (probably) need to configure openSMTPD to listen on 587 > > (I run exim, so I can't help with that).

forgot to also ask about the maildir set up I have: mail_location = maildir:~/var/mail/%u:LAYOUT=fs for the following structure: /var/mail/[user]/Drafts Inbox Sent Spam Trash but should be wrong cause when I log in into roundcube I can't see the stored emails. If I completely skip

I am using OpenSMTPD. The OpenBSD 6.3 default one. Also, when telnet to 127.0.0.1 25 I get a response! So must be something with 587? On Wed, Jul 11, 2018 at 11:47 PM, Larry Rosenman <larryrtx at gmail.com> wrote: > What's your neomutt connecting to? > > For smtp? > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640

drwxr-xr-x 5 512 Jun 26 21:41 Trash drwxr-xr-x 5 512 Jun 26 21:41 Spam drwxr-xr-x 5 512 Jun 26 21:41 Sent drwx------ 6 512 Jul 7 00:23 Inbox drwxr-xr-x 5 512 Jun 26 21:41 Drafts On Thu, Jul 12, 2018 at 12:00 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > What does an ls -lr of /var/mail/<user> look like? > > > -- > Larry Rosenman

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

obvious correction ... sorry. netstat -np | grep :587 > Date: Wednesday, July 11, 2018 21:57:31 +0000 > From: Richard <inbound-dovecot at listmail.innovate.net> > what does the output of: > > netstat -n | grep :587 > > run as root, show you? the -p will give the program and pid. > > > >> Date: Wednesday, July 11, 2018 21:51:09 +0000 >>

If you telnet to port 25, do an EHLO host, does the response include AUTH? If not, opensmtpd is not offering AUTH over unencrypted port 25 connections. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 ?On 7/11/18, 6:05 PM, "Teno Deuter" <gvgter