Hello,
I manage a Dovecot installation version 2.3.4.1 with a pair of
proxy/director in front and two backends that use the replicator plugin
to synchronize emails between them.
I would like to update all 4 machines and would like to understand if I
can directly jump to the latest version 2.
Hi
I'm setting up a Dovecot Proxy Server to access Gmail.
But It doesn’t work.
I tried to configure Dovecot without proxy authentication.
passdb {
driver = static
args = nopasssword=y proxy=y proxy_mech=xoauth2 ...
}
It works fine. So far so good.
But with proxy authentication It doe
rbird.
Greetings,
Camilo Sperberg
On Tue, Aug 24, 2021 at 2:37 PM Camilo Sperberg wrote:
> Hi list!
>
> I've configured dovecot-proxy to redirect users to another server if their
> data is indeed on that other server.
>
> Webmail (which runs on the same machine) works perfectly
Hi list!
I've configured dovecot-proxy to redirect users to another server if their
data is indeed on that other server.
Webmail (which runs on the same machine) works perfectly fine, but clients
such as Thunderbird and Outlook do not work as intended, I suspect it to be
a problem with t
Dovecot1 doc, but it isn't documented anymore. Also the location under
"authentication" chapter in the Wiki didn't tell me, that this is the
"new Dovecot proxy documentation". I thought, this was only related to
authentication issues. I would recommend to
On 31 Aug 2020, at 03:33, Thoralf Rickert-Wendt wrote:
> documentation https://wiki1.dovecot.org/HowTo/ImapProxy (which is really old
> and should be updated)
That is documentation for Dovecott version 1 (that's the 1 in wiki1).
Other than that, I can't help you, but this documentation is abosl
dn't tell me, that this is the
"new Dovecot proxy documentation". I thought, this was only related to
authentication issues. I would recommend to either restructure the
wiki2, that it makes it more clear to the user or make some notes on
https://doc.dovecot.org/admin_manual/dove
ion here
> (I'm talking about any new dovecot version and I've tested it with 2.3.4.1
> (f79e8e7e4)).
>
> I try to run a dovecot proxy in front of a big number of mail servers
> (serving SMTP-in, submission, IMAP, POP3, Sieve). I need that proxy, because
> I run out of IPv
ut any new dovecot version and I've tested it with
2.3.4.1 (f79e8e7e4)).
I try to run a dovecot proxy in front of a big number of mail servers
(serving SMTP-in, submission, IMAP, POP3, Sieve). I need that proxy,
because I run out of IPv4 addresses. Of course I use IPv6 too, but many
custo
d": false,
"preferred_username": "dome.nico"
[...]
When Dovecot proxy connects to the backend, email attribute and user have the
same value, master-user.
This behavior is a problem because when backend tries login access, login with
the user and not with the mailb
T. 040 - 711 44 96
E. wedwa...@cyberfusion.nl
- Original Message -
From: Aki Tuomi (aki.tu...@open-xchange.com)
Date: 12/27/19 17:42
To: William Edwards (wedwa...@cyberfusion.nl), dovecot (dovecot@dovecot.org)
Subject: Re: Dovecot proxy: authentication best practices
On 27/12/2019 16:02 Wil
On 27/12/2019 16:02 William Edwards wrote:
Hi!
I have a few questions regarding Dovecot proxy:
1.
1.1 If I understand correctly, setting 'nopas
Hi!
I have a few questions regarding Dovecot proxy:
1.
1.1 If I understand correctly, setting 'nopassword' in the proxy passdb file,
authentication is completely up to the destination host. Setting 'nopassword'
in no way means the proxy becomes an open relay. Is this co
Hello.
Sorry.
Organize and describe what I want to do.
There may be no unity, but please forgive me.
Also, I'm not good at English, so I'm sorry if it's difficult to understand.
1. I had to create a proxy server for an external SMTP server (here,
“smtp.example.com” as an example).
So I decided t
On 4.12.2019 15.33, Riku via dovecot wrote:
> Hello.
>
> Sorry.
> Since 2.3.9 was released, I installed it immediately and tried to set
> "lmtp_add_received_header" to "no".
> But it seems different from what I wanted to do.
> The following is my configuration file.
> Please let me know if there
Hello.
Sorry.
Since 2.3.9 was released, I installed it immediately and tried to set
"lmtp_add_received_header" to "no".
But it seems different from what I wanted to do.
The following is my configuration file.
Please let me know if there are any other configuration files that need to be
listed.
I
Hello.
Thank you for teaching.
I'd like to try it out if 2.3.9 comes out.
I look forward to the release of 2.3.9.
Thank you very much.
Best regards.
> On 2 Dec 2019, at 19.23, Tom Sommer via dovecot wrote:
>
>
> On 2019-12-02 13:42, Riku via dovecot wrote:
>> Hello.
>> My name is Riku.
>> Currently, I use Dovecot as a proxy for another SMTP server.
>> However, this seems to cause the IP address of the "received" header
>> to be that of th
On 2019-12-02 13:42, Riku via dovecot wrote:
Hello.
My name is Riku.
Currently, I use Dovecot as a proxy for another SMTP server.
However, this seems to cause the IP address of the "received" header
to be that of the proxy server.
Is it possible to change this so that the IP address of the sen
I thought, I read somewhere I could prevent chroot with[1] but I am
still getting chroot errors[2].
drwxrwxr-x 2 10053 101 6 Dec 2 16:54 empty
drwxr-x--- 2 10053 101 73 Dec 2 17:00 login
drwxr-x--- 2 10053 101 44 Dec 2 17:00 token-login
[1]
service anvil {
chroot =
}
[2]
Dec 2 1
Hello.
My name is Riku.
Currently, I use Dovecot as a proxy for another SMTP server.
However, this seems to cause the IP address of the "received" header to be that
of the proxy server.
Is it possible to change this so that the IP address of the sender is entered?
The version of Dovecot is "2.3.8
Thanks!! Added this.
pass_attrs = uid=user,userPassword=password,host=host
-Original Message-
Subject: RE: Dovecot proxy with ldap, complains about 'host not given'
You need to specify fields you want. Fields are not imported
automatically.
See https://doc.d
wrote:
My query? Is dovecot not getting this field automatically?
-Original Message-
Subject: Re: Dovecot proxy with ldap, complains about 'host not given'
On 23
My query? Is dovecot not getting this field automatically?
-Original Message-
Subject: Re: Dovecot proxy with ldap, complains about 'host not given'
On 23 Nov 2019, at 16:11, Marc Roos wrote:
> It looks like the dovecot proxy can authenticate correctly but fails
&
On 23 Nov 2019, at 16:11, Marc Roos wrote:
> It looks like the dovecot proxy can authenticate correctly but fails
> then on with this message
>
> Nov 23 23:33:33 test2 dovecot: pop3-login: Error: proxy: host not given:
> user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secu
It looks like the dovecot proxy can authenticate correctly but fails
then on with this message
Nov 23 23:33:33 test2 dovecot: pop3-login: Error: proxy: host not given:
user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured,
session=
I have configured a host= in ldap for this user
returning 'namespace/inbox/prefix' value from SQL. Here's the
setup I attempted, briefly:
1. Client connects to the Dovecot proxy, which authenticates the user
and proxies to the backend using a query like this in
/etc/dovecot/conf.d/dovecot-sql.conf.ext:
driver = mysql
connect =
passwo
iki.dovecot.org/Namespaces#Per-user_Namespace_Location_From_SQL
I thought I might be able to overwrite the server configuration per user
returning 'namespace/inbox/prefix' value from SQL. Here's the setup I
attempted, briefly:
1. Client connects to the Dovecot proxy, which authenticates the user
and prox
> On 24 Nov 2017, at 17.36, Federico Bartolucci wrote:
>
> Hello,
>
> has someone already tested the dovecot-proxy with more than 10 nodes? or
> someone knows anyway if is it officially supported up to a certain number?
There is no limit really. Proxies work standalone
Hello,
has someone already tested the dovecot-proxy with more than 10 nodes? or
someone knows anyway if is it officially supported up to a certain number?
Thanks.
ather large number, disrupts new IMAP proxy
connections momentarily).
I reckon this is not an issue with Dovecot, but I'm curious to know if
other folks have observed this behavior when dealing with iOS Mail app
clients?
The log entries look like this:
iOS 10 device = 172.16.0.1
RHE
ging the hostname on the imap server, makes some troubles like MUA
> redownloading all the messages?
> Is dovecot (running on the imap server) happy seeing the hostname change?
> What about maildirs, where the hostname is wrote on the mail file?
>
> 2. Dovecot proxy will proxy the wh
messages?
Is dovecot (running on the imap server) happy seeing the hostname change?
What about maildirs, where the hostname is wrote on the mail file?
2. Dovecot proxy will proxy the whole pop3/imap traffic or only the login
auth?
I don't want to expose the mailservers to internet, all imap se
2016-10-29 17:02 GMT+02:00 Aki Tuomi :
> You could use private ip addresses backends so you don't even need to expose
> them to internet at all.
This means creating a VPN between my local DC with Dovecot servers and
the cloud service provider with proxies.
> On October 29, 2016 at 5:17 PM Gandalf Corvotempesta
> wrote:
>
>
> Hi,
> just a simple question: by using a directory and a proxy, I would be
> able to totally hide the pop3/imap server ip addresses from outside?
> I'm asking this because I would like to hide the real server IP for
> securi
Hi,
just a simple question: by using a directory and a proxy, I would be
able to totally hide the pop3/imap server ip addresses from outside?
I'm asking this because I would like to hide the real server IP for
security reasosn (DDoS and so on).
The proxy would be placed on servers with high bandwi
y
> clients we should keep POP/IMAP-before-SMTP running for some time, but right
> know I don’t know how to hook up a successful authentication in the dovecot
> proxy.
>
> I did read from http://wiki2.dovecot.org/PostLoginScripting:
> “...it's not currently possible t
, but right
know I don’t know how to hook up a successful authentication in the dovecot
proxy.
I did read from http://wiki2.dovecot.org/PostLoginScripting:
“...it's not currently possible to run post-login scripts in proxies,
because they're not actually logging in to the loc
will submitted it as a Pull Request on Github:
https://github.com/dovecot/core/pull/6
Wido
> Op 9 april 2016 om 11:25 schreef Wido den Hollander :
>
>
> Hi,
>
> I am trying to set up a Dovecot proxy which proxies through POP3, IMAP and
> LTMP
> towards a different Dove
Hi,
I am trying to set up a Dovecot proxy which proxies through POP3, IMAP and LTMP
towards a different Dovecot machine.
On the proxy machine I use a MySQL database as a userdb and passwdb backend and
it returns the proper information as described here:
http://wiki2.dovecot.org/PasswordDatabase
Hello,
I want to deploy dovecot proxy/director with the backend and
authorization in LDAP. Dovecot wiki specifies only what is necessary
to apply additional arguments that the scheme would have earned a
proxy, but no solid LDAP schema.
Is there such a scheme, such as the existing scheme
http
On Tue, 22 Sep 2015, Timo Sirainen wrote:
Yeah. The ssl_client_ca_file was implemented later than the SSL proxying
code. I think this may be something that needs to wait for v2.3 to get
fixed. v2.3 hopefully removes the duplicated ssl code and uses
lib-ssl-iostream for proxying also, which mak
On 22 Sep 2015, at 01:11, Alex Bulan wrote:
>
> On Mon, 21 Sep 2015, Edgar Pettijohn wrote:
>
>> doveconf -n?
>
> doveconf -n|grep ssl should suffice:
>
> ssl = required
> ssl_ca = ssl_cert = ssl_key = ssl_require_crl = no
>
> I'm using "ssl_ca = workaround, even though this is not what s
On Mon, 21 Sep 2015, Edgar Pettijohn wrote:
ssl = required
shouldn't it be:
ssl = yes
I was only aware of the choice of yes or no here, but I could be wrong.
See http://wiki2.dovecot.org/SSL/DovecotConfiguration
On 09/21/2015 05:11 PM, Alex Bulan wrote:
On Mon, 21 Sep 2015, Edgar Pettijohn wrote:
doveconf -n?
doveconf -n|grep ssl should suffice:
ssl = required
shouldn't it be:
ssl = yes
I was only aware of the choice of yes or no here, but I could be wrong.
ssl_ca = I'm using "ssl_ca = tempor
On Mon, 21 Sep 2015, Edgar Pettijohn wrote:
doveconf -n?
doveconf -n|grep ssl should suffice:
ssl = required
ssl_ca = I'm using "ssl_ca = temporary workaround, even though this is not what ssl_ca is for. It
happens to work, at least for now, but this is not a fix.
ssl_client_ca_file shoul
doveconf -n?
On 09/21/2015 12:45 PM, Alex Bulan wrote:
On Mon, 21 Sep 2015, Andrew McN wrote:
http://wiki2.dovecot.org/Replication
(quote)
The client must be able to verify that the SSL certificate is valid, so
you need to specify the directory containing valid SSL CA roots:
ssl_client_ca_di
On Mon, 21 Sep 2015, Andrew McN wrote:
http://wiki2.dovecot.org/Replication
(quote)
The client must be able to verify that the SSL certificate is valid, so
you need to specify the directory containing valid SSL CA roots:
ssl_client_ca_dir = /etc/ssl/certs # Debian/Ubuntu
ssl_client_ca_file = /
On Mon, 21 Sep 2015, Christian Kivalo wrote:
Haven't found much about proxying and ssl but found a configuration parameter
ssl_ca =
http://wiki2.dovecot.org/SSL/DovecotConfiguration section Client certificate
verification/authentication
ssl_ca serves a different purpose, it's for setting yo
On 21/09/15 17:28, Alex Bulan wrote:
> The result is the same with or without "<" before the file path. With
> "<" the inode atime is updated at Dovecot startup, so the file is at
> least opened, but Dovecot still can't verify the cert.
>
> The only place in the Wiki that shows an example of ssl
On 2015-09-21 09:28, Alex Bulan wrote:
The result is the same with or without "<" before the file path. With
"<" the inode atime is updated at Dovecot startup, so the file is at
least opened, but Dovecot still can't verify the cert.
The only place in the Wiki that shows an example of ssl_clie
The result is the same with or without "<" before the file path. With "<"
the inode atime is updated at Dovecot startup, so the file is at least
opened, but Dovecot still can't verify the cert.
The only place in the Wiki that shows an example of ssl_client_ca_file is
on this page, and there's
Hi
I've pointed ssl_client_ca_file to my root certificate store, but I
suspect ssl_client_ca_file is only used in imapc context. It seems to
be ignored in proxy context.
doveconf -n ssl_client_ca_file:
ssl_client_ca_file = /usr/local/share/certs/ca-root-nss.crt
You are missing the "<" before
On Monday 21 September 2015 01:53:53 Alex Bulan wrote:
> Dovecot v2.2.18
> OS: FreeBSD 10.1/amd64
>
> Dovecot in proxy mode ignores the root certificate store and can't verify
> the backend's SSL certificate.
>
> I've pointed ssl_client_ca_file to my root certificate store, but I
> suspect ssl_cl
t and it verifies successfully
with "openssl s_client -connect x.x.x.x:110 -starttls pop3 -CAfile
/usr/local/share/certs/ca-root-nss.crt".
But the Dovecot proxy fails to verify the intermediate certificate it
receives from the backend. The inode atime of ca-root-nss.crt is never
Hello,
I run a dovecot proxy (which is doing authentification itself) and a
dovecot backend on separate boxes.
I want to change the actual password scheme.
Since postlogin scripting is not supported by proxies and %w variable is
not forwaded to dovecot backend is there any way that I can update
#x27;s anything wrong with that though.
On 07/21/2015 11:54 AM, Laz C. Peterson wrote:
The consensus seems to say no to RR DNS … I am going to take that
into serious consideration.
With this proxy setup you describe, what would happen if HAProxy or
Dovecot Proxy were to fail?
I think there is
2015 11:54 AM, Laz C. Peterson wrote:
> > The consensus seems to say no to RR DNS … I am going to take that
> > into serious consideration.
> >
> > With this proxy setup you describe, what would happen if HAProxy or
> > Dovecot Proxy were to fail?
> >
> > I thi
On 2015-07-21 02:54 PM, Laz C. Peterson wrote:
The consensus seems to say no to RR DNS … I am going to take that into
serious consideration.
With this proxy setup you describe, what would happen if HAProxy or
Dovecot Proxy were to fail?
Multiple instances of each. I'll be using Smart
… I am going to take that into serious
consideration.
With this proxy setup you describe, what would happen if HAProxy or Dovecot
Proxy were to fail?
I think there is no problem with many moving parts, as long as there is a
backup plan in case something goes awry. My goal is slightly different
The consensus seems to say no to RR DNS … I am going to take that into serious
consideration.
With this proxy setup you describe, what would happen if HAProxy or Dovecot
Proxy were to fail?
I think there is no problem with many moving parts, as long as there is a
backup plan in case something
Round-robin DNS last I checked can be fraught with issues.
While doing something else I came up with this idea: Clients --> Load
Balancer(HAProxy) --> Dovecot Proxy(DP) --> Dovecot Director(DD) --> MS1 / MS2.
When DP checks say user100 it'll find a host=DD-POD1 that return
Am 20.07.2015 um 20:04 schrieb Laz C. Peterson:
> I’m trying to do this too. But the goal would be simply for automatic
> failover to the other datacenter. Everything is working if the server’s
> unique hostname is entered, but I want to do something like round robin DNS
> that mail clients wi
I’m trying to do this too. But the goal would be simply for automatic failover
to the other datacenter. Everything is working if the server’s unique hostname
is entered, but I want to do something like round robin DNS that mail clients
will automatically attempt to connect to the other IP if t
I'm trying to determine which dovecot components to use and how to order them
in the network path from client to mail store.
If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail
stores, configured into 2, 2 node pods.
MS1 and MS2 are pod1 and are configured with replicati
hi all,
I've been tasked to add sieve/managesieve to an existing dovecot cluster
running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts
as directors and some back end dovecot imap hosts all running the same
version.
My problem is that I thought to put the service o
Hi Alessio,
Thank you very much for your detailed explanation.
gdrub
2014-12-01 18:28 GMT+01:00 Alessio Cecchi :
>
> Il 01/12/2014 17:11, rub zorghy ha scritto:
>
>> Why Dovecot Director server isn't used to perform this without Dovecot
>> proxy ? Thus, the loa
On 2014-12-01 19:56, anon_u...@openmailbox.org wrote:
Il 01/12/2014 17:11, rub zorghy ha scritto:
Why Dovecot Director server isn't used to perform this without Dovecot
proxy ? Thus, the load balancer (F5 Big-IP) can distribute requests
based
on IMAP protocol to Dovecot Director clust
Il 01/12/2014 17:11, rub zorghy ha scritto:
Why Dovecot Director server isn't used to perform this without Dovecot
proxy ? Thus, the load balancer (F5 Big-IP) can distribute requests based
on IMAP protocol to Dovecot Director cluster.
I think that the slide is just one example of a sce
his webinar
<http://knowledgebase.open-xchange.com/fileadmin/user_upload/open-xchange/misc/webinar/2013_21_08/Dovecot_Webinar_21.08.2013.pdf>
mentions (slide 7) a Dovecot proxy cluster (doing credentials and user info
lookup) behind the LB device (F5 Big-IP)
Why Dovecot Director server isn't u
Hi,
Thank for your reply.
OK, if I understand I must just read doc with Dovecot Proxy :)
Incoming mail:
Postfix (LMTP) => Dovecot Proxy Server => Dovecot Backend Server (Final server
and storage server)
IMAP:
Dovecot Proxy Server => Dovecot Backend Server (Final server and storage s
On 19.7.2014 00:54, Nathan Schultheiss wrote:
Hello,
For a few days I try to understand what program (Dovecot Director or
Dovecot Proxy) I should use for my email architecture.
We are a hospital, and for security reasons, we must host ourselves our
emails, and we must leave Google Apps...
OT
Hello,
For a few days I try to understand what program (Dovecot Director or
Dovecot Proxy) I should use for my email architecture.
We are a hospital, and for security reasons, we must host ourselves our
emails, and we must leave Google Apps...
I wish to make a Dovecot backend for each
On 8.5.2014, at 15.02, mtrai...@cloud-free.com wrote:
> I need to import mailboxes into my Director NFS setup via
> one of my director proxy's as doing a direct dsync to the backend
> mailstores appears to giving me NFS locking issues. It looks like it may
> be possible to do this using doveadm li
Hi All,
I need to import mailboxes into my Director NFS setup via
one of my director proxy's as doing a direct dsync to the backend
mailstores appears to giving me NFS locking issues. It looks like it may
be possible to do this using doveadm listeners. I have setup doveadm
listeners on a test
Unfortunately, the requirement for this network is that the only pinhole
through the firewall between the main relay and the mail server is IMAP. My
thought was to ship a list of valid usernames to the imap relay that are
allowed to connect, and that list would be constructed from inside the LAN
Is it possible to use backend's passdb on the relay server in your setup?
If you are - for example - using SQL database as passdb on the backend,
you can access it from relay server as well. Let's say you have
"relay_enabled" column in the table of users, then you can use something
like:
sel
Hi everyone,
I have a problem that hopefully has an easy solution.
I am setting up an IMAP proxy in a DMZ network. It will connect to the real
IMAP server and authenticate using "driver = imap", and this I have working
really nicely.
What I want to do is have it look up a list of users that a
) SMTP AUTH using
SASL
from Postfix with Dovecot proxy is still not supported as discussed in
these threads
(especially the first one)?
http://www.dovecot.org/list/dovecot/2012-August/067977.html
http://www.dovecot.org/list/dovecot/2011-May/059107.html
As I understand it is possible to use
Can somebody please verify that currently (v 2.2.9) SMTP AUTH using SASL
from Postfix with Dovecot proxy is still not supported as discussed in
these threads
(especially the first one)?
http://www.dovecot.org/list/dovecot/2012-August/067977.html
http://www.dovecot.org/list/dovecot/2011-May
Dear Alex et al
> Did you happen to have this working? Could you share how?
So far it's not working yet. We are currently exploring more recent
dovecot versions (2.2.9 AFAIR) but had to do some other work to keep the
mailsystem running. Now we have more time to work on migration and will
post a
Hello Jogi,
Did you happen to have this working? Could you share how?
Thanks,
Alex
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/proxy-userdb-and-passdb-tp44860p45200.html
Sent from the Dovecot mailing list archive at Nabble.com.
On 14.10.2013, at 21.22, d...@getodata.ro wrote:
> I am interested in the possibility of using Dovecot IMAP/POP proxying
> capabilities to analyze emails that are passing through and possibly modify
> content on the fly. This subject has been discussed here [1] before.
> I have tried the mail-fi
;
> user:::proxy=y host=IP-ADDRESS starttls=y nopassword=y
> passdb {
> args = session=yes
> driver = pam
> }
> userdb {
> args = /etc/dovecot/proxy-userdb
> driver = passwd
> }
1) Use passwd-file, not passwd
2) userdb has no effect on proxying, it must be passdb
Hi Steffen,
Am 2013-10-22 10:05, schrieb Steffen Kaiser:
see http://wiki2.dovecot.org/PasswordDatabase/ExtraFields
Did, thanks. The errors I mentioned in my previous post are gone.
Still, proxying does not work as expected. Instead I get strange warnings:
Oct 22 12:06:51 server dovecot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2013, Jogi Hofmüller wrote:
We are getting closer to the migration of our mailsystem. Now I have a
special question. We are successfully using
passdb {
driver = pam
}
and that is good. Now, how would I tell dovecot to proxy cert
Dear all,
We are getting closer to the migration of our mailsystem. Now I have a
special question. We are successfully using
passdb {
driver = pam
}
and that is good. Now, how would I tell dovecot to proxy certain users
(the ones not yet migrated) to the old server? My attempts to configur
I am interested in the possibility of using Dovecot IMAP/POP proxying
capabilities to analyze emails that are passing through and possibly
modify content on the fly. This subject has been discussed here [1]
before.
I have tried the mail-filter plugin [2], but the hooks it uses are only
called i
On Mon, 7 Oct 2013, Alex Wanderley writes:
passdb {
args = proxy=y nopassword=y user=remotemail destuser=remotemail@gmail.comhost=
pop.gmail.com port=995 proxy_timeout=15 starttls=y
driver = static
}
...
Oct 7 09:33:13 dserver dovecot: auth: Debug: client passdb out: OK
2 user=remotemai
Am 07.10.2013 18:37, schrieb Charles Marcus:
> On 2013-10-07 12:11 PM, Alex Wanderley wrote:
>> # OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final)
>
> Aaaack!
>
> Makes me wonder what vancient version of openssl, and maybe that is the
> culprit?
openssl-0.9.8e - so what - be
On 2013-10-07 12:11 PM, Alex Wanderley wrote:
# OS: Linux 2.6.18-308.8.2.el5xen x86_64 CentOS release 5.8 (Final)
Aaaack!
Makes me wonder what vancient version of openssl, and maybe that is the
culprit?
Hi,
I've been trying to build a password forwarding proxy to Gmail without
success... The SSL connection to Dovecot is happening no problem (as far as
I can tell), but for some reason the conversation between Dovecot and Gmail
is getting timed out.
I know this is supposed to be simple... :-(
Hello,
I understand the matter of using Dovecot as a forward proxy to Gmail is
very popular (and even trivial), but my lack of Dovecot experience took me
to at point where I truly need your help...
I'm starting my task by trying to have something simple, where I can test
connectivity to Gmail by
On Fri, Sep 27, 2013 at 11:28 AM, Timo Sirainen wrote:
> On 27.9.2013, at 16.57, Justin McAleer wrote:
>
> > I am hoping to support encrypted passwords, which I know is generally not
> > allowed in a proxy setup. However, I can return the password in
> clear-text
> > out of the password database
On 27.9.2013, at 16.57, Justin McAleer wrote:
> I am hoping to support encrypted passwords, which I know is generally not
> allowed in a proxy setup. However, I can return the password in clear-text
> out of the password database, so I was hoping for something similar to the
> destuser field.
Th
I am hoping to support encrypted passwords, which I know is generally not
allowed in a proxy setup. However, I can return the password in clear-text
out of the password database, so I was hoping for something similar to the
destuser field.
I have successfully used the master password functionality
Hi
Am 22.09.2013 03:13, schrieb Reindl Harald:
> Am 22.09.2013 02:20, schrieb Timo Sirainen:
>> %$ is the status, so you're asking for another status variable. Something
>> like in the attached patch, where you can replace %$ with %{login_status}?
>
> *exactly* that's it - many thanks!
>
> %{lo
I've solved the issue by setting ssl to 'any-cert' and starttls to NULL.
This does a proper SSL request to the node.
I still don't understand why Dovecot does a non-SSL request on an SSL port
whenever I enable starttls, but I'm happy using normal SSL.
Regards,
Am 22.09.2013 02:20, schrieb Timo Sirainen:
> On 22.9.2013, at 1.29, Reindl Harald wrote:
>> login_log_format_elements = %status <%u> %r %m %c %cipher
>> login_log_format = %s
>>
>> Sep 21 18:39:47 localhost dovecot: imap-login: OK, ,
>> 192.168.2.2, CRAM-MD5, DHE-RSA-CAMELLIA256-SHA
>>
On 22.9.2013, at 1.29, Reindl Harald wrote:
>>> if fact i would only need "login_log_format = %s" but in case of failed
>>> logins
>>> and dictionary attacks with unknown users "%u" is empty - if %u would
>>> *always*
>>> contain the used loginname, wether if it was successful or not i would ha
1 - 100 of 262 matches
Mail list logo
