similar to: Dovecot for POP3S proxying

I'm a database noob, and it really seems like it would be overkill for my setup: I just want to proxy all connections from my DMZ to my internal mail server -- same internal server for all users. I used to use perdition for this set up, but am having issues getting it to play nicely with my new servers. Can I bypass all of the SQL stuff and just have dovecot forward all POP/IMAP

How exactly is LMTP proxying supposed to work? According to the example on http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I'm only seeing "proxy" in the password_query statements. But LMTP never sends a password. IMAP Proxying is working OK: Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993:

Hey all, I''m just checking my understanding. Would someone be so kind as to comment on the following? Event.observe(''this_link'', ''click'', function() { AJAX.Updater(''that_div'', ''my.php'', { evalscripts: true}) }); <div that_div> </div> /////// my.php

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

Hi I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is configured to act as director and delivers to my two backend servers. I enabled lmtp proxy on director to listen on port 24. Now I see in msg headers that the connection to the lmtp proxy uses STARTTLS but the connection from proxy to backend seems to be unencrypted. Is it possible to enforce the use of STARTTLS in the

Hi, when proxying lmtp from director to backend, director does not use STARTTLS. Delivering mails with postfix via lmtps to backend or director works encrypted. Is there a way to force the use of STARTTLS on dovecot director lmtp proxy? Regards, Matthias -- BOFH excuse #446: Mailer-daemon is busy burning your message in hell. (hbox storage?)

Hello, reading the wiki I found http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy?highlight=(no DNS resolving) I have a setup where the destination of a proxyconnection is an DNS name. Is there a technical reason which currently require host= to be an IP address ? -- Andreas Schulze Internetdienste | P532 DATEV eG 90329 N?rnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196

Before I spend some time experimenting with what might be impossible, maybe someone can just tell me (either "how" or that it's impossible). I'd like to get perdition out of my environment (mainly to have one less moving part in my architecture). I'm looking at dovecot's built-in proxying. In my setup, I don't have dedicated front-end machines. A user can connect

I'm preparing my new Sendmail mail server with pop3s + smtps where user authentication occurs through Microsoft Active Directory by Winbind daemon. OS is Centos 6.4 and Sendmail is 8.14 Mailboxes will be in this server but how to create them !??! It's necessary to add user by 'useradd' command into /etc/passwd or It's only necessary add new entry in '/etc/aliases'

Hi, I'm using Dovecot for pop3-ssl. Unofortunatelly, most of my users are using MS Outlook. I want them to be able to remove standard mesage: "The certificat is not signed by...", but I don't know how :-( In the dialog isn't a button "Trust this certificate forever"... Is there anybody, who know, how to solve this? Many thanks.

In the course of experimenting with getting dovecot proxying to work, I took a guess at two things. These work fine for me, but now I'm wondering if they are "as designed" or just a lucky accident that might stop working in the future. (I'm using dovecot 1.0.rc17, which is the included version in Ubuntu Feisty. (I am aware that some details change in v1.1, and I'm not

Hi, I need to setup a new mail server and before I got my feet wet or losing in the configurations jungle, I really need some advice from the gurus here for what the best software to used for the mailserver base on CentOS 4.x setup. The objective is, the mailserver will be easy to setup, maintained and have some 1. database backend for storing user info ( mysql? ) 2. spam and antivirus

I'm migrating a load of mailboxes from cyrus to a new dovecot server. What I'd like to do is to switch the DNS to dovecot, and set things up so that all old imap mailboxes are accessed through the dovecot proxy. That way I can migrate them one at a time independent of DNS issues. I've got a load of users specified in mysql, and that configuration works well for local mailboxes. How

Hi all, I have some IMAP servers fronted with separate perdition processes, and it would be ideal if I could collapse this down to having dovecot do both the IMAP proxying and the IMAP serving at the same time on the same IP addresses. One of the fields in my LDAP entries contains the canonical name of the server that hosts their mailbox, and if I follow the manual at

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

On my CenOS7 system with stunnel from base stunnel-4.56-4.el7.x86_64 there's a systemd service file /etc/systemd/system/stunnel.service try sudo systemctl enable stunnel.service Hope this helps, K ?al?

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 am interested in running a Dovecot Proxy(with Director) on the same server as the main Dovecot IMAP/POP3 service. I have a basic Proxy/Director configuration working, however I am struggling with getting the Proxy and IMAP/POP3 service to coexist on the same server. I plan to use three IMAP/POP3 servers with a NFS/maildir backend, and I am playing with Dovecot 2.1.5 at the moment. I

Hi, I would like to achieve the following with my dovecot server: - listen von FQDN 'mail.foo.example.com'/IP 'A' for imaps and pop3s with an SSL certificate for 'mail.foo.example.com' - listen von FQDN 'mail.bar.example.com'/IP 'B' for imaps and pop3s with an SSL certificate for 'mail.bar.example.com' I stumbled over a posting by Timo made

NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently - any ssl/starttls extra field is ignored https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy Am 23. November 2017 09:31:41 MEZ schrieb Tobi <tobisworld at gmail.com>: >Hi > >I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is >configured to act as director and delivers to my two backend