Displaying 20 results from an estimated 6000 matches similar to: "Dovecot as caching proxy"
2013 Jun 18
3
Matching username in ssh_config
Hi all openssh devs out there.
I have quite a few Host-stanzas in my .ssh/config to keep track of all the
different settings and credentials needed to access all different hosts I
connect to.
Now I have ran in to a problem where I need to switch settings based on what
user I'm trying to login to a host as. A simple case is:
ssh -i rootkey root at host123
vs.
ssh -i userkey username at
2013 Aug 28
2
mailbox_list_index, stops showing new mails in mailboxes
Hello.
I'm having some weird problem with (probably) mailbox_list_index,
that it doesn't see new mail in mailboxes.
I'm using 2.2.4 over imap and ssh/imap, and after a while dovecot
stops noticing new mail in some folders. Its always the same 2-3
folders of about 30.
I read something about list-index corruption in 2.2.2, and i thought
it was that i was running into earlier, but this
2015 Oct 13
0
dovecot as proxy and verification of the backends certificate
On 11 Oct 2015, at 20:04, Heiko Schlittermann <hs at schlittermann.de> wrote:
>
> Hello,
>
> I'm using a dovecot as proxy, connecting to one or more backends.
> The backends use X.509 certificates.
>
> The proxy's passdb returns
>
> extra fields:
> user=foo
> proxy
> host=backend1.<domain>
> ssl=yes
> nopassword=y
2012 Oct 11
1
imap proxy setup - "killed with signal 11"
hi-
i'm setting up an imap proxy in front of a novell groupwise server. it
seems to so far be partially working, but dovecot is having trouble in
certain cases. i expect that it's ultimately due to what i believe is a
very poor implementation of imap provided by groupwise [at least based
on other experiences in the past] - but that's a big part of why i'd
like to have
2015 Oct 11
2
dovecot as proxy and verification of the backends certificate
Hello,
I'm using a dovecot as proxy, connecting to one or more backends.
The backends use X.509 certificates.
The proxy's passdb returns
extra fields:
user=foo
proxy
host=backend1.<domain>
ssl=yes
nopassword=y
Thus the proxy connects to the backend but can't verify the backends
certificate.
The following comment suggests using ssl_client_ca_file for
2017 Jan 05
2
IMAP proxy for Exchange - encrypted backend Communication?
Hello,
I try to setup a IMAP proxy for my old Exchange server.
Running Dovecot v2.x on Centos 7.
So far I follow http://wiki2.dovecot.org/HowTo/ImapcProxy and it seem
to work. The only but major thing is with this setup - the
communication between proxy and backend is not encrypted. :(
To fix this, I changed the config and add:
imapc_ssl=imaps
imapc_port=993
but it doesnt work, because of
2013 Jun 16
3
Transparent IMAP proxy
Hi,
I'm considering patching Dovecot to work as a transparent (and virus
scanning) IMAP proxy.
What is the appropriate feature to extend? (I've considered the
following: IMAPC and reverse proxying, with IMAPC looking more promising
since it actually parses IMAP communication).
Can anyone who is familiar with the IMAPC code recommend what are the
most appropriate locations in the
2017 Sep 11
0
Is it possible to disable pipelining in imapc?
On 11.09.2017 13:09, Nagy, Attila wrote:
> On 09/11/2017 11:14 AM, Aki Tuomi wrote:
>>
>> On 11.09.2017 11:59, Nagy, Attila wrote:
>>> On 09/11/2017 10:42 AM, Sami Ketola wrote:
>>>>> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote:
>>>>> I use dovecot with a broken IMAP server (which doesn't properly
>>>>>
2014 Sep 19
1
doveadm with multiple instances on same machine(s)
Couple questions about running doveadm with multiple instances... I have
Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and
main instance running. When I try to lookup something on the main
instance (which is handling user auth) via its auth-userdb socket
directly, I get an error:
# doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser
doveadm(root): Error: passdb
2019 Jul 15
0
Authdb NSS module
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/07/2019 02:54 Eugene via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
</div>
<div>
2019 Jul 14
2
Authdb NSS module
Hello!
Upgrading manual tells that authdb [NSS module was removed][1] some time ago.
[1]: https://wiki2.dovecot.org/Upgrading/2.3#line-100
> userdb nss was removed. Use userdb passwd instead.
Can this change be reverted?
I'd like to use only libnss_sss.so.2 as dovecot userdb source. It's also essential for me to enable files backend in nsswitch.conf so the system could use local
2019 Jul 15
1
Authdb NSS module
I use LDAP right now, but local cached sssd queries are much faster and reliable.
On July 15, 2019 6:49:18 AM GMT+03:00, Aki Tuomi <aki.tuomi at open-xchange.com> wrote:
>
>
>On 15/07/2019 02:54 Eugene via dovecot < dovecot at dovecot.org> wrote:
>
>
>
>Hello!
>
>
>Upgrading manual tells that authdb [NSS module was removed][1] some
>time ago.
>
2014 May 16
1
imapc Proxy to IMAPS Exchangeserver?
I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy
to our Exchange Server, which has LOGINDISABLED on Port 143, and I
offering LOGIN on Port 993.
How do I go about this?
Simply changing imapc_port to:
imapc_port = 993
doesnt work:
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS
2017 Sep 11
2
Is it possible to disable pipelining in imapc?
On 09/11/2017 11:14 AM, Aki Tuomi wrote:
>
> On 11.09.2017 11:59, Nagy, Attila wrote:
>> On 09/11/2017 10:42 AM, Sami Ketola wrote:
>>>> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote:
>>>> I use dovecot with a broken IMAP server (which doesn't properly
>>>> implement command pipelining amongst others) as an imapc backend.
2017 Sep 29
0
imapc and masteruser
> On 28 Sep 2017, at 23.08, Computerisms Corporation <bob at computerisms.ca> wrote:
>
> Hi Sami,
>
> Thank you for your reply.
>> yes you do need to define imapc_user if you want to switch user and master user around for imapc. like:
>> imapc_user = authapps
>> imapc_master_user = %u
>> without imapc_user dovecot would login to the secondary server
2017 Apr 10
2
v2.2.29 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig
* passdb/userdb dict: Don't double-expand %variables in keys. If dict
was used as the authentication passdb, using specially crafted
%variables in the username could be used to cause DoS (CVE-2017-2669)
* When Dovecot encounters an internal error, it logs the real error
2017 Apr 10
2
v2.2.29 released
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.29.tar.gz.sig
* passdb/userdb dict: Don't double-expand %variables in keys. If dict
was used as the authentication passdb, using specially crafted
%variables in the username could be used to cause DoS (CVE-2017-2669)
* When Dovecot encounters an internal error, it logs the real error
2017 Sep 28
2
imapc and masteruser
Hi Sami,
Thank you for your reply.
> yes you do need to define imapc_user if you want to switch user and master user around for imapc. like:
>
> imapc_user = authapps
> imapc_master_user = %u
>
> without imapc_user dovecot would login to the secondary server like A bob.test*bob.test password
When I add the 'imapc_user = authapps' option to the primary instance
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig
Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
* When Dovecot encounters an internal error, it logs the real error and
usually logs another line saying what function failed. Previously the
second log line's error message was
2017 Apr 06
2
v2.2.29.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.29.rc1.tar.gz.sig
Planning to release v2.2.29 on Monday. Please find and report any bugs before that.
* When Dovecot encounters an internal error, it logs the real error and
usually logs another line saying what function failed. Previously the
second log line's error message was