-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 20 Sep 2015, li...@lazygranch.com wrote:
No problem sending email, but I can't receive email. Diagnostics follow:
this is a pretty unspecific information. At which stage the message is
stuck and not delivered to Dovecot? Which MTA do you
I managed to write a ugly but working checkpassword script for dovecot,
having multiple passwords for a user.
But now I found this:
https://github.com/dweuthen/roundcube-application_passwords
I think this is the better way to go. the crypt passwords are the
biggest problem because you need the sto
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
Op 9/21/2015 om 2:34 PM schreef Hajo Locke:
> Hello,
>
> i use sieve extension sieve_extprograms to send incoming mail to some
> script.
> For security reasons it is needed that script-paths etc. are
> registered in dovecot.conf
> This is my current dovecot.conf
>
> plugin {
> sieve = ~/.dovecot.
Op 9/21/2015 om 12:16 AM schreef T.B.:
> Hi Stephan Bosch,
> any update on this?
Unfortunately, no.
It is not high up my list at the moment. :/
Regards,
Stephan.
>
>
> Regards,
>
> T.B.
>
>
> Am 08.05.2014 um 14:37 schrieb Stephan Bosch:
>> T.B. schreef op 7-5-2014 10:40:
>>> I think it would
On 09/21/2015 12:11 PM, B. R. wrote:
Hello,
Thanks for your answer.
I read this Wiki tip, but it does not fit, as I serve emails for several
domains, each using its iwn (potentioally enciphered) private key.
I thus need to use the directive as port of a local_name block.
I tried to create 2
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
Am 21.09.2015 um 14:34 schrieb Hajo Locke:
> Hello,
>
> i use sieve extension sieve_extprograms to send incoming mail to some
> script.
> For security reasons it is needed that script-paths etc. are registered
> in dovecot.conf
> This is my current dovecot.conf
>
> plugin {
> sieve = ~/.dovecot
Hello,
Thanks for your answer.
I read this Wiki tip, but it does not fit, as I serve emails for several
domains, each using its iwn (potentioally enciphered) private key.
I thus need to use the directive as port of a local_name block.
I tried to create 2 blocks in 2 different files automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21-09-15 14:34, Hajo Locke wrote:
> Hello,
>
> i use sieve extension sieve_extprograms to send incoming mail to
> some script. For security reasons it is needed that script-paths
> etc. are registered in dovecot.conf This is my current
> dovecot.
Hello,
i use sieve extension sieve_extprograms to send incoming mail to some
script.
For security reasons it is needed that script-paths etc. are registered
in dovecot.conf
This is my current dovecot.conf
plugin {
sieve = ~/.dovecot.sieve
sieve_plugins = sieve_extprograms
sieve_extensio
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
19 matches
Mail list logo
