similar to: Dovecot proxy/director and mail pop3/imap backend service on same server

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

Hello, I want to test dovecot proxying, on a user basis, in a simple set up (proxy, no proxy_maybe and forward the passwd to the remote server). This seem pretty simple except that, in order to test it alongside the production server, I set up 3 servers : . the proxy, listening to pop and imap on non standard ports 9143, 9993, 9110, 9995 . a proxy destination for some users, listening on

Sure ! # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 4.4.2-hardened x86_64 Gentoo Base System release 2.2 auth_mechanisms = plain login auth_verbose = yes default_client_limit = 4096 default_internal_user = mailer default_process_limit = 300 dict { sqlquota = pgsql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext }

I'm trying to setup our first director server. Trying to keep the initial config simple really as just maybe a proof of concept and its got me pulling my hair out today. Initially I just tried to convert one of my already running IMAP servers to be a director just to see if I could do it. I modified the configs as it appeared they needed based on: https://wiki2.dovecot.org/Director

Op 7/7/2017 om 1:18 PM schreef j.emerlik: > Solved temporary by replacing X-Spam-Status to X-Spam-Flag. > > X-Spam-Flag in my system is added only to SPAM e-mail, anyway it looks like > a bug. Can you show your configuration (output from `dovecot -n`)? An example message may also be useful. Regards, Stephan. > Regards, > Jack > > > 2017-07-07 12:41 GMT+02:00

Hello, I've been using the dovecot 1.2.x branch server software for a while now. With the advent of the 2.0.x branch going 'stable' I decided to attempt a migration and make use of some of the features that I've not needed before. One of these is the shared folder/namespace feature. No luck. I've hit a wall and can not determine the problem. At the

Working again. Explains a lot actually. Inital box I was experimenting on PAM was already setup and had worked. That error I got caught up in was with SSSD and PAM wasn't working. Fixing the error shot myself in the foot in other ways. Thank you! -Jesse C. Smillie On 3/13/17 4:38 PM, Aki Tuomi wrote: >> On March 13, 2017 at 10:21 PM "Jesse C. Smillie" <jsmillie at

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with

Hi all, I have observed with my Dovecot setup that unique failed logins cause legitimate correct logins to be slowed. I am running two servers, each with two Dovecot instances, a Proxy with Director, and a backend Dovecot. I suspect that the backend instance is throttling connections from the same IP, and because I am running a Proxy, the backend will only see either of the two server IPs. I

Dave McGuire writes: >> http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets >> >> then setup fail2ban to manage extrafields > > Now that's a very interesting idea, thank you! I will investigate this. If you don't expect yor firewall to handle 45K+ IPs, I'm not how you expect dovecot will handle a comma separated string with 45K+ entries any

This patch allows the dovecot proxy processes to lookup the destination host by name instead of IP address. Tested agains 1.2.10, expected to work against 1.2.11. The patch is pretty straightforward, it's making it work within the restrictions of the login process that's more interesting. I have made some changes to the wiki (pending approval) to - enhance the discussion of proxy

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director

On 03/01/2015 06:34 PM, Benny Pedersen wrote: >> The other side of this equation, Postfix, has had this capability >> for years. Why it hasn't been added to dovecot is a mystery. It's >> the only thing (really, the ONLY thing!) that I dislike about dovecot. > > http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets > > then setup fail2ban to

Hello again, I did a lot of trial and error already, but I can't seem to find a way to encrypt my dovecot director to dovceot mailbox traffic. Is there a way to configure dovecot director to only use ssl/tls encrypted connections for specific tagged mailbox clusters? (or all clusters, in fact does not matter if it could be restricted to tags) Looks like there is also no documentation

Hello, I like to enable the allow_nets Feature (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets) for my customers. To help them knowing there own IP I imagine a special mailbox/loginuser at the pop3 server. That user could give a valid pop3 answer from a dummy pop3 server or simply throw a login error with customised answer containing the IP information. Has anybody done

The wiki <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy> page says this: "The connections created to the destination server can't be TLS/SSL encrypted.". Hrmm. Right now, with perdition, I'm forcing the use of STARTTLS on the internal connections. I'd just as soon get rid of perdition (to have one less moving part in my architecture), but I need the

I am doing some research on Dovecots IMAP-Proxy features mentioned in <http://wiki.dovecot.org/HowTo/ImapProxy> and <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy>. The docs only mention SQL as backend to hold required data. Is it also possible to use LDAP? TIA, p at rick -- state of mind Agentur f?r Kommunikation, Design und Softwareentwicklung Patrick Koetter

We are using the following to record conversations. exten => _1XXX.,1,SetVar(CALLFILENAME=call_to_${EXTEN:1}_dated_${TIMESTAMP}) exten => _1XXX.,2,Monitor(wav,${CALLFILENAME},m) exten => _1XXX.,3,Dial(IAX2/4506:zj5S3A5a@nl.voipgate.nl/${EXTEN:1}) exten => _1XXX.,4,Congestion exten => _1XXX.,104,Congestion This was working previously to record both sides of the conversation but now

Abstract from http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy > > host=s: The destination server's *IP address*. This field is required. > Note that currently it's required to use an IP address since no DNS > resolving is done. > Hello Timo, Here goes one more item for the v2.0 wishlist: Will it become possible to do dovecot imap proxying based on a

Hello. dovecot 2.2.26.0 When testing nopassword extra field (http://wiki2.dovecot.org/PasswordDatabase/ExtraFields) with CRAM-MD5 dovecot doesn't allow any password (while it should) and returns " Authentication failed" while in logs: Nov 17 08:22:34 auth-worker(1551): Info: sql(pepe,127.0.0.1,<Y8amDXpBptV/AAAB>): Requested CRAM-MD5 scheme, but we have a NULL password