-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently some of our organizational roles uses shared secrets (aka the
password) to access the mail account of an organizational role, say
"sales" for example. For one, I don't like shared secrets, for second,
there had been some changes to shared
Dear all,
I tried to do a backport of 'ssl_prefer_server_ciphers'
(http://hg.dovecot.org/dovecot-2.2/rev/897484f45a87/) to Dovecot 2.1
(namely the Debian version of Dovecot) and wanted to ask if there is any
chance to integrate this feature into Dovecot 2.1 'upstream' as well.
As the code structur
Am 18.10.2013 13:57, schrieb Adi Kriegisch:
> I tried to do a backport of 'ssl_prefer_server_ciphers'
> (http://hg.dovecot.org/dovecot-2.2/rev/897484f45a87/) to Dovecot 2.1
> (namely the Debian version of Dovecot) and wanted to ask if there is any
> chance to integrate this feature into Dovecot 2.
Hi!
> > PS: I need that feature to enable PFS while allowing Outlook to still
> > connect and the others not to fall back to a different cipher; I was
> > unable to find a PFS cipher that is supported by Outlook and OpenSSL
>
> ssl_cipher_list =
> EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+
Am 18.10.2013 14:22, schrieb Adi Kriegisch:
>>> PS: I need that feature to enable PFS while allowing Outlook to still
>>> connect and the others not to fall back to a different cipher; I was
>>> unable to find a PFS cipher that is supported by Outlook and OpenSSL
>>
>> ssl_cipher_list =
>> EECDH+E
Thank you, Steffen.
So, you are telling that in correct working environment, each user should
have its own "Sent" and "Drafts" file?
Does anybody knows how to achieve it, or what can cause their
non-separation?
Thanks
--
View this message in context:
http://dovecot.2317879.n4.nabble.com/Having-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2013, SiR wrote:
So, you are telling that in correct working environment, each user should
have its own "Sent" and "Drafts" file?
No, it's a matter of configuration. Usually users have their own Sent and
Drafts, but that is not man
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
Dear all,
> I tried to do a backport of 'ssl_prefer_server_ciphers'
> (http://hg.dovecot.org/dovecot-2.2/rev/897484f45a87/) to Dovecot 2.1
[...]
> (Dovecot code is probably the most beautiful and easy to read C code I've
> seen, but there might also be some pitfalls I missed.)
I'd be very grateful
I'm planning to deploy a personal dovecot IMAP server (i.e. I am the
only user) in a FreeBSD jail.
At present, I have IMAP deployed on the same host as one of my mail
servers, which is running Postfix. I do like Postfix, but it seems to be
a bit overkill for this particular situation.
All my
Am 18.10.2013 20:03, schrieb Dan Langille:
> I'm planning to deploy a personal dovecot IMAP server (i.e. I am the only
> user) in a FreeBSD jail.
>
> At present, I have IMAP deployed on the same host as one of my mail servers,
> which is running Postfix. I do like
> Postfix, but it seems to be
Hello!
A Server running openSUSE 12.3 and dovecot version 2.1.13.
In the log I find
Oct 19 00:23:23 managesieve(anme...@anup.de): Warning: sieve-storage: Active
sieve script symlink /var/spool/vhosts/anup.de/anmeyer/.dovecot.sieve is
broken: invalid/unknown path to storage (points to
/var/spoo
12 matches
Mail list logo
