similar to: Dovecot 1.2.17, Proxy and forwarding of remote ip

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:

Dear all, I experience SegFaults in the imap binary on a LIST "" "" command, as sent by Claws mail. Using LIST "" "INBOX" or similar is fine. Here is an example telnet session $ telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE

Mar 26 16:38:58 cartman dovecot: imap(miha at example.com): Error: Couldn't create namespace 'Share/' for user miha-share at example.com: userdb didn't return a home directory, but location used it (%h): maildir:%%h/Maildir:INDEX=%h/index/Shared/%%u Where is the problem, the same config worked with Dovecot 1.2.x -- View this message in context:

Hello, I am getting crash on lmtp for specific message on dovecot 2.3.2 See below the backtrace: Jul 02 22:54:20 Panic: lmtp(xxx)<172769><yL/kH0zXOlvhogIAF3haWw:3>: Buffer write out of range (23153 + 18446744073709551614) Jul 02 22:54:20 Error: lmtp(xxx)<172769><yL/kH0zXOlvhogIAF3haWw:3>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xcdfe4) [0x7f1fc8df9fe4] ->

hello i have a dovecot 1.2.11 and i have implementation of 2 dovecot machines, one proxy one storage part. everything is working fine, i only have one question regarding the message that should go away after the first successful login on proxy server. how to remove it on proxy server? May 7 16:04:19 proxy-server dovecot: pop3-login: proxy(tmihal at example.com): started proxying to

I'll try reproduce this issue, but can you, in the mean time, run this with mail_debug=yes and provide logs? Aki On 23.01.2017 11:45, Thorsten Hater wrote: > Hi, > > I did added the default location and stripped down my config to a very > basic > level, dropping all plugins and database queries, see below. The segfault > still > appears in the same location. > As I

We are seeing a few (0-15) proxy failures like the following out of ~3m successful proxied connections a day. Average session creation load over our peak hour is about 47/sec. The backend servers aren't logging anything that would suggest any internal problem like insufficient processes to handle the load. It doesn't seem to happen when utilization is lowest at night. dovecot:

Thank you for your report. Aki On 23.01.2017 11:56, Thorsten Hater wrote: > OK, I found the problem in my config. If I use an default namespace with an > empty > name, instead of "inbox" it works as expected. Here the log for this case > > Starting program: /usr/local/libexec/dovecot/imap -u **** > imap(****): Debug: auth input: **** home=**** uid=48 gid=48 >

Hi, I am running two dovecot servers active/active. Everything runs pretty great, except for the replication of subscriptions in a shared namespace. When I unsubscribe from a folder the subscription instantly re-appears. The timestamp on the subscriptions file is updated, but the entry is still in there. If the other node is shut down, everything works as expected, which leads me to believe that

Hi, I am running dovecot on 3 qmail-ldap server backend. dovecot configured to use auth_pop3 wrapper for authentication. Users logins to the qmail-ldap pop3&imap pools randomly. If a user is mailhost is not the connected server, dovecot proxies the connection to the user mailhost. In this case, I can not get the original client IP address via post-logins script on user host. I see only the

Hi, today we have exceprienced really major difficulties with our proxy backend servers. Everything started after enabling auth cache: auth_cache_size = 100M auth_cache_verify_password_with_worker = yes auth_cache_ttl = 1 hour auth_cache_negative_ttl = 1 hour Soon after we start receiving lots of calls from our customers about 'missing all e-mail messages'. This was in errors logs on

Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:

Any thoughts on this? --- Daniel ------ Original Message ------ From: "Daniel Miller" <dmiller at amfes.com> To: "Dovecot Mailing List" <dovecot at dovecot.org> Sent: 2/12/2020 6:16:05 PM Subject: Shared Mailboxes with Multiple Domains >Trying to track down a problem I've been dealing with for a while. Everything else works fine - the problem is with

Hello all, I am testing postlogin script with dovecot 2. I works but i would like that the imap and pop session get executed even if the post-login script fail. my postlogin script is very simple: #/etc/dovecot/conf.d/10-master.conf service imap { executable = imap imap-postlogin } # service imap-postlogin { executable = script-login /usr/local/bin/postlogin.sh unix_listener

Hi all; I've setup dovecot (2.1.10) in a cluster configuration. We have two servers acting as frontend which authenticates users and proxy them to other two servers which handles the "real" work. Users credentials are on a mysql cluster; we have one master, in which read/write queries are processed, and many replicated slave, which process read-only queries. The frontend

Hi I tried several variants of suggestions but I can't get it working dovecot-info.log: =========== Aug 25 17:37:48 imap-login: Info: Login: user=<vuser>, method=PLAIN, rip=192.168.1.xx, lip=192.168.1.xx, mpid=11264 Aug 25 17:37:48 imap(vuser): Info: Post-login script denied access to user vuser dovecot.log ======== Aug 25 17:31:28 imap-postlogin: Error: script-login: Error: user pmp

Hello, I'm having trouble understanding how to execute separate scripts with postlogin. According to the documentation, it should be as simple as: You can run multiple post-login scripts by just giving multiple scripts as parameters to|script-login|, for example: executable = script-login rawlog /usr/local/bin/postlogin.sh /usr/local/bin/postlogin2.sh Given this information, I supplied two

Did anyone set up the enviroment in dovecot with post login scripting in which imapsync does sync between two mailservers on users login (on login sync mail from old to new mailserver) is there a alternative or different approach? something like #!/bin/bash /usr/bin/imapsync --syncinternaldates --nosyncacls --authmech1 PLAIN --host1 old.server.com --user1 $USER*master --password1 master

Hi Could someone explain what this strings mean in dovecot 2.1.3 debug log? Mar 27 11:18:11 cartman dovecot: auth: Debug: master in: USER 1 test1 at example.net service=lib-storage Mar 27 11:18:11 cartman dovecot: auth: Debug: master in: USER 2 test2 at example.net service=lib-storage -- View this message in context:

I'm in the processes of running our first dsync backup of all users (from maildir to mdbox on remote server), and one problem I'm hitting that dsync will work fine on first run for some users, and then reliably fail whenever I try a new run: $ sudo dsync -u janfrode at example.net backup ssh -q mailbackup at repo1.example.net dsync -u janfrode at example.net $ sudo dsync -u janfrode