I think, I've got a response on Serverfault, that helps me and I like to
give a complete example here. I was able to proxy IMAP and Submission
with the following settings:
dovecot.conf:
ssl_cert = password_query = SELECT NULL as password, 'y' as nopassword, 'y' as
proxy, NULL as destuser,
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
Hi Philon,
now, it's time for "Mahlzeit" ;-)
Sorry, that I read the wiki1 instead of wiki2. I thought the 1 means
that it is server one of ... my fault. Also not reading the first line
above the menu. My focus was really on the content. ;-)
Also my problem with the doc of Dovecot2 proxy is,
Hi Thoralf,
I’d say first of all you should read the current docs for 2.x not the archived
stuff. —> https://wiki2.dovecot.org/ - (It’s even mentioned in bold in the
header)
Then to front multiple backends perhaps you want to take a look at Dovecot
Director. —> https://wiki2.dovecot.org/Direct
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 'nopassword'
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, secured,
> session=
>
Forgot to add "doveconf -n" for the proxy server:
# 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.24 (124e06aa)
# OS: Linux 4.14.81-6.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804
(Core)
# Hostname: proxy1.0aditest.local
auth_cache_negative_ttl = 5 mins
auth_cache_
> 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 and are not linked toget
2016-11-17 9:11 GMT+01:00 Gandalf Corvotempesta
:
> Hi to all
> I have some *production* pop3/inappropriate server that i would like to move
> under a proxy
>
> Some questions:
> 1. Keeping the same original hostname on the proxy (in example
> mail.mydomain.tld)
> and changing the hostname on the i
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
I looked into the further and it seems that there is no default port for LMTP in
Dovecot.
I patched the code and this seems right:
https://github.com/wido/core/commit/a5917908850eb570ca441517e6bc33f6ce63ed7a
This will make the LMTP client connect to TCP port 24 if no port has been
provided.
I wi
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
Right.. I stand corrected
On 07/21/2015 12:37 PM, Marcus Rueckert wrote:
On Tue, 21 Jul 2015 12:00:39 -0700
James Lott wrote:
I think RR DNS is the only viable solution under these circumstances.
If you can cope with the fact that failovers won't be seamless, I
don't think there's anything wr
On Tue, 21 Jul 2015 12:00:39 -0700
James Lott wrote:
> I think RR DNS is the only viable solution under these circumstances.
> If you can cope with the fact that failovers won't be seamless, I
> don't think there's anything wrong with that though.
>
> On 07/21/2015 11:54 AM, Laz C. Peterson wrot
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 SmartOS as th
I think RR DNS is the only viable solution under these circumstances. If
you can cope with the fact that failovers won't be seamless, I don't
think there'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 ta
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 returns two IPs,
those
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
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 22.10.2013, at 13.13, Jogi Hofmüller wrote:
> 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. Ins
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
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?
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
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
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
Am 22.09.2013 00:18, schrieb Reindl Harald:
> Am 22.09.2013 00:07, schrieb Reindl Harald:
>> Am 21.09.2013 23:37, schrieb Timo Sirainen:
>>> Different people want different things logged. I think if I started adding
>>> settings to control those from Dovecot configuration it would quickly
>>> b
Am 22.09.2013 00:07, schrieb Reindl Harald:
> Am 21.09.2013 23:37, schrieb Timo Sirainen:
>> On 14.8.2013, at 17.37, Reindl Harald wrote:
>>
>>> login_log_format_elements = user=<%u> method=%m rip=%r %k
>>>
>>> is it possible to get rid of the "proxy(t...@testserver.rhsoft.net):
>>> started proxy
Am 21.09.2013 23:37, schrieb Timo Sirainen:
> On 14.8.2013, at 17.37, Reindl Harald wrote:
>
>> login_log_format_elements = user=<%u> method=%m rip=%r %k
>>
>> is it possible to get rid of the "proxy(t...@testserver.rhsoft.net): started
>> proxying to 127.0.0.1:143: " part
>> because on a prox
On 14.8.2013, at 17.37, Reindl Harald wrote:
> login_log_format_elements = user=<%u> method=%m rip=%r %k
>
> is it possible to get rid of the "proxy(t...@testserver.rhsoft.net): started
> proxying to 127.0.0.1:143: " part
> because on a proxy-only server i know that and it is explicitly not lis
Am 14.08.2013 17:12, schrieb Reindl Harald:
>> is it possible to get rid of the "proxy(t...@testserver.rhsoft.net): started
>> proxying to 127.0.0.1:143: " part
>> because on a proxy-only server i know that and it is explicitly not listed
>> in "login_log_format_elements"
>>
> got it
>
> login
Am 14.08.2013 16:37, schrieb Reindl Harald:
> Hi
>
> login_log_format_elements = user=<%u> method=%m rip=%r %k
>
> is it possible to get rid of the "proxy(t...@testserver.rhsoft.net): started
> proxying to 127.0.0.1:143: " part
> because on a proxy-only server i know that and it is explicitly
On Thu, 2013-02-14 at 10:48 +0100, Antonio Casado Rodriguez wrote:
> Hi all,
>
> I had a imaps dovecot server working normal. I wanted to isolate the
> Internet connection by placing a proxy imap(Intranet connections still
> connect directly to the imap server).
> Yesterday I set up oneproxy ima
Original Message
Subject: Re: [Dovecot] Proxy to join two accounts
From: Timo Sirainen
To: Tomek
Date: 23.11.2012 08:24
You should be able to implement something like that by creating a new
namespace with location=imapc:
http://wiki2.dovecot.org/HowTo/ImapcProxy and
http
On 21.11.2012, at 12.15, Tomek wrote:
> I have server with IMAP on dovecot for user mails and second server on
> archiveopteryx as mail archive.
>
> I'm wondering if it's possible to make some sort of proxy to these two
> servers in way where:
> - dovecot server will be main IMAP service with I
On 18.9.2012, at 2.02, Kelsey Cummings wrote:
> 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 a
On 30.6.2012, at 0.41, Zac Israel wrote:
> # 2.0.19: /etc/dovecot/dovecot.conf
..
> passdb {
> args = proxy=proxy_always nopassword=y host=172.16.0.13 port=143
> proxy_timeout=5 starttls=y ssl=any-cert
v2.0 has some problems with this. You should use v2.1 and use server name as
the "host" value
On Sat, Jun 30, 2012 at 4:52 AM, Charles Marcus
wrote:
> On 2012-06-29 5:41 PM, Zac Israel wrote:
>>
>> The system at 172.16.0.13 is a zimbra proxy. I can see in the logs
>> that it initially complains about my ssl cert, and if I remove
>> ssl=any-cert it fails because my cert is self signed, so
On 2012-06-29 5:41 PM, Zac Israel wrote:
The system at 172.16.0.13 is a zimbra proxy. I can see in the logs
that it initially complains about my ssl cert, and if I remove
ssl=any-cert it fails because my cert is self signed, so I know it is
talking to the proxy and doing starttls which is a req
El Miércoles, 4 de Abril de 2012 13:47:47 Miguel Tormo escribió:
> El Miércoles, 4 de Abril de 2012 13:21:33 Timo Sirainen escribió:
> > On 4.4.2012, at 14.18, Miguel Tormo wrote:
> >
> > > I have a running setup with a dovecot imap4/pop3 proxy to a few dovecot
> > > backend servers which actuall
El Miércoles, 4 de Abril de 2012 13:21:33 Timo Sirainen escribió:
> On 4.4.2012, at 14.18, Miguel Tormo wrote:
>
> > I have a running setup with a dovecot imap4/pop3 proxy to a few dovecot
> > backend servers which actually store the mailboxes. This is running
> > smoothly and allows me to trans
On 4.4.2012, at 14.18, Miguel Tormo wrote:
> I have a running setup with a dovecot imap4/pop3 proxy to a few dovecot
> backend servers which actually store the mailboxes. This is running smoothly
> and allows me to transparently distribute mailboxes.
> I'm using some "extrafield" configured in t
On Wed, Jan 11, 2012 at 10:06:51PM +0100, Stephan Bosch wrote:
> On 1/11/2012 8:01 PM, Nicolas KOWALSKI wrote:
> >
> >I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to
> >backend, and have Managesieve still working. Is this supported?
>
> Although there is no such thing as a stand
On Wed, Jan 11, 2012 at 10:34:33PM +0200, Timo Sirainen wrote:
> On 11.1.2012, at 21.01, Nicolas KOWALSKI wrote:
>
> > I would like to use IMAPs, instead of IMAP+STARTTLS, from proxy to
> > backend, and have Managesieve still working. Is this supported?
>
> You'll need to kludge it a little bit.
On 1/11/2012 8:01 PM, Nicolas KOWALSKI wrote:
Hello,
On a dovecot 2.0.14 proxy, I found that proxying managesieve works well
when using 'starttls' option in pass_attrs, but does not work when using
'ssl' option. The backend server is also dovecot 2.0.14; when using the
ssl option, it reports "no
On 11.1.2012, at 21.01, Nicolas KOWALSKI wrote:
> On a dovecot 2.0.14 proxy, I found that proxying managesieve works well
> when using 'starttls' option in pass_attrs, but does not work when using
> 'ssl' option. The backend server is also dovecot 2.0.14; when using the
> ssl option, it reports
On 09.01.2012 23:39, Timo Sirainen wrote:
On 9.1.2012, at 22.23, Urban Loesch wrote:
I'm using two dovecot pop3/imap proxies in front of our dovecot servers.
Since some days I see many of the following errors in the logs of the two
proxy-servers:
dovecot: pop3-login: Error: proxy: Remote "I
On 9.1.2012, at 22.23, Urban Loesch wrote:
>>> I'm using two dovecot pop3/imap proxies in front of our dovecot servers.
>>> Since some days I see many of the following errors in the logs of the two
>>> proxy-servers:
>>>
>>> dovecot: pop3-login: Error: proxy: Remote "IPV6-IP":110 disconnected:
Am 09.01.2012 19:40, schrieb Timo Sirainen:
On 9.1.2012, at 12.18, Urban Loesch wrote:
I'm using two dovecot pop3/imap proxies in front of our dovecot servers.
Since some days I see many of the following errors in the logs of the two
proxy-servers:
dovecot: pop3-login: Error: proxy: Remote
On 9.1.2012, at 12.18, Urban Loesch wrote:
> I'm using two dovecot pop3/imap proxies in front of our dovecot servers.
> Since some days I see many of the following errors in the logs of the two
> proxy-servers:
>
> dovecot: pop3-login: Error: proxy: Remote "IPV6-IP":110 disconnected:
> Connecti
On Wed, 2011-10-19 at 21:17 -0400, Pedro Paixao wrote:
> Is is posible to use the virtual plugin, in a IMAP proxy configuration, in a
> way that the virtual plugin searches messages on the real server?
>
> Here's my scenario:
>
> [Client][Dovecot Proxy]-[Real Imap Server]
>
> Client conn
On Wed, 2010-11-24 at 15:01 +0100, Oliver Eales wrote:
> postfix main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp
>
> The dovecot proxy tries to connect to the backend server port 0 which is
> obviously not working.
> The proxy always seems to connect to the same port on the backend a
On Sun, 2010-07-18 at 18:22 -0300, Aliet Santiesteban Sifontes wrote:
>
> - In case we use a Proxy with dovecot we know we can use it with
> IMAP/POP but are not sure for ManageSieve and more important for SMTP. The
> question is, how can we proxy for the same user IMAP/POP/ManageSieve and
>
Aliet Santiesteban Sifontes put forth on 7/18/2010 4:22 PM:
> 6- Mail backend.
> - ( n servers)RHEL5/6 using Dovecot.
>
> Now for functional role 6 "Mail Backend" we have some dilemmas.
>- Recommended scalable filesystem to use for such scenario(Clustered or
> not).
You have 3 choices: NFS
BTW, and I'm not sure, if you still need amavis, as direct scanning
(using clamav or some other scanner) will be faster. Same is for
Spamassassin, as long as you use it as filter and not just as some
evaluator.
--
Heiko
signature.asc
Description: Digital signature
Hello,
just my comment on you topic: if I'd design such setup, I'd expect, that
sooner or later some additional flexibility is needed, that there will
be same tasks you never thought about in advance. I'm not sure, if in
such case I'd rely on Postfix. Postfix might be fast, but it is by no
means a
On 17/06/2010 17:31, Chris Hobbs wrote:
I've mostly got our dovecot+postfix+SOGo+openldap open source groupware
replacement working the way I want it to; we're replacing GroupWise in our
organization and I'm thrilled to be doing it. I'm supporting about 1,000 active
staff users (and another 6,
On 6/18/2010 10:03 PM, Michael Orlitzky wrote:
> Have two passwords, a secretary one and your real one. When you want to
> give your secretary access, change it to the secretary password. To
> revoke, change back.
Don't be silly... the feature discussed is a reasonable one.
Maybe the concept if M
On 06/17/2010 12:31 PM, Chris Hobbs wrote:
I've mostly got our dovecot+postfix+SOGo+openldap open source
groupware replacement working the way I want it to; we're replacing
GroupWise in our organization and I'm thrilled to be doing it. I'm
supporting about 1,000 active staff users (and another 6,
Am 17.06.2010 18:31, schrieb Chris Hobbs:
> I've mostly got our dovecot+postfix+SOGo+openldap open source groupware
> replacement working the way I want it to; we're replacing GroupWise in our
> organization and I'm thrilled to be doing it. I'm supporting about 1,000
> active staff users (and an
On Mon, 2010-05-03 at 15:50 +0200, Martin Ott wrote:
> user2::0:0proxy=yes host=[ip-address] ssl=any-cert starttls=yes
> nopassword=y
>
> Is there some kind of catch-all function to pass all users to the main
> dovecot-imapserver without knowing the valid users?
You could do that with sql (
Hi again,
Scrap that, I am now getting along fine writing my response to file
descriptor 4.
Thanks again,
Aaron
-Original Message-
From: dovecot-bounces+aroberts=domicilium@dovecot.org
[mailto:dovecot-bounces+aroberts=domicilium@dovecot.org] On Behalf Of Aaron
R
That helped, it works again. Thanks!
Timo Sirainen schrieb:
On Oct 6, 2009, at 5:54 AM, Adrian Wojcicki | Unternehmensberatung
Wojcicki wrote:
We have a server running dovecot and proxying IMAPS connections to our
internal network. This worked so far very good until we upgraded the
server t
On Oct 6, 2009, at 5:54 AM, Adrian Wojcicki | Unternehmensberatung
Wojcicki wrote:
We have a server running dovecot and proxying IMAPS connections to
our internal network. This worked so far very good until we upgraded
the server to a new SUSE Linux version and with it dovecot from
versio
On Fri, 2008-12-05 at 17:43 +0100, Matthieu Herrb wrote:
> Hi
>
> For some application we need a master user on our IMAP servers. We use
> dovecot 1.1.7 in proxy mode, with proxy_maybe (some mailboxes are on the
> proxy itself, others are on remote servers, also running dovecot).
>
> But the prox
On Tue, 2008-08-26 at 07:20 +0200, Paul Gamble - MWEB wrote:
> Hi Timo
>
> The patch you provided to allow Dovecot-as-proxy's login processes to
> log the "destuser" only does so for successful authentications/logins.
> What is the possibility that this information could additionally be
> logged f
valid
user-name/invalid password?
The patch mentioned is:
http://hg.dovecot.org/dovecot-1.1/raw-rev/5d0406541434
Regards
-Original Message-
From: Timo Sirainen [mailto:[EMAIL PROTECTED]
Sent: 14 August 2008 10:22 PM
To: Paul Gamble - MWEB
Cc: Dovecot Mailing List
Subject: Re: [Dovecot
On Aug 14, 2008, at 4:42 AM, Paul Gamble - MWEB wrote:
Aug 14 10:14:03 withnail dovecot: imap-login: MYPROXY pid=6516,
[EMAIL PROTECTED], method=PLAIN, rsock=127.0.0.1:48157,
lsock=127.0.0.1:1143, proto=IMAP, secured proxy([EMAIL PROTECTED]):
started proxying to 127.0.0.1:143/pgamble*master:
Aug
le" for this (along the lines of %u, %p,
%s, etc, etc)?
Regards,
Paul Gamble
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Timo
Sirainen
Sent: 14 August 2008 09:12 AM
To: Paul Gamble - MWEB
Cc: dovecot@dovecot.org
Subject: Re: [Dovecot] Proxy
On Aug 14, 2008, at 2:36 AM, Paul Gamble - MWEB wrote:
Is it possible for a Dovecot proxy's login process (IMAP and POP3) to
include the "destuser", i.e. the uid used to authenticate to the
backend
IMAP/POP3 server, in its logging? "%u" gives me the uid provided by
the
client of course, but
On 27 Mar 2008, at 19:08, Scott Silva wrote:
on 3-27-2008 11:46 AM Richard Cooper spake the following:
Hi,
I'm trying to use dovecot as a proxy as described on http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy
but without much success. The problem is that when I send a IMAP
login c
on 3-27-2008 11:46 AM Richard Cooper spake the following:
Hi,
I'm trying to use dovecot as a proxy as described on
http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy but without
much success. The problem is that when I send a IMAP login command
dovecot is responding with "BYE Internal
On Mon, 2008-02-04 at 10:41 -0200, bugtraq wrote:
> sql([EMAIL PROTECTED],127.0.0.1): query: SELECT pw_clear_passwd AS password,
> pw_domain AS domain, '192.168.224.1' AS host, 'Y' AS nologin, 'Y' AS
> nodelay, 'Y' AS proxy FROM vpopmail WHERE pw_name = 'diego' AND
> pw_domain = 'domain' limit 1
I
Yes, the proxy verifies if that password is correct before forward and I
want to insert a record on sql table if is succesfuly or not.
On one of proxy (/var/log/dovecot.log) I can see:
dovecot: Feb 04 10:31:16 Info: auth(default): client in: AUTH 1
PLAIN service=imapsecured lip=127.0.0.1
On Thu, 2008-01-24 at 23:38 -0200, diego wrote:
> Hi, I'm testing dovecot 1.1.beta14 on two debian etch with
> drbd+ocfs2[active/active], I use qmail+vpopmail(userdb) and three
> front-end with openbsd 4.2 with dovecot 1.1.beta14 as proxy with passdb
> sql through vpopmail database.
> Is posible
> Patrick Ben Koetter wrote:
> Ed W wrote:
Thanks to both for your comments; very helpful. I just wanted to make
sure it could work in practice before I spent some time on it. Sounds
like it can be done.
Lessons learned?
It works and it worked immediately. Store backend host information as IP
address and not as host name.
I have a setup similar to what the OP described. The other missing
ingredient is that in current stable version you need to change your
mysql query to avoid returning
1 - 100 of 118 matches
Mail list logo
