Hello Dovecot Dev team,
In my cpanel, we use your email management. This is what my hosting provider
has allowed.
Our problem:
Since the introduction of "hi def cameras on mobile phones", we are getting
emails with "huge attachments". The email which comes with the attachments
is also
Just to understand that correctly: I could setup a (cron) based process for
doveadm sync, but no longer a setup like
plugin {
mail_replica = tcp:$IMAP_REPLICA_SERVER:$IMAP_REPLICA_PORT
}
where the cron would lead to some delay and would have to check for concurrent
jobs?
nfiguration_manual/config_file/config_variables/
> <https://doc.dovecot.org/configuration_manual/config_file/config_variables/>>
> for details.
>
>
> Key management is pretty much the most difficult thing in mail crypt
> plugin =)
>
>
> Aki
>
&
Do I have to replace the "password" part with the actual password or can I just
copy it like that?
Will dovecot create the keypair automatically or do I have to use doveadm?
4. Sep. 2019, 08:33 von aki.tu...@open-xchange.com:
>
>
>
> On 4.9.2019 9.21, Dustin Schoenwolf via dovecot wrote:
Thank you very much for this idea.
I thought I have already tried this out.
I have copy the *.crt to the official dir of ssl/cert and set the
access to 644.
And now all works correctly.
Tobias
Am 2017-03-21 08:06, schrieb Aki Tuomi:
Could you copy LetsEncrypt.pem to a world-readable
The one that works fine was my openxchange server, that loads contacts
from openldap.
In my opinion I don't have installed a security framework list SELinux
or AppArmor.
The output of namei -l /etc/ssl/certs/LetsEncrypt.pem
f: /etc/ssl/certs/LetsEncrypt.pem
drwxr-xr-x root root /
The user "dovecot" can access and read the cert.
Here is an output of the console:
https://gwarband.de/openldap/dovecot-certs.log
So I think there is nothing what prevent Dovecot to access the file.
Tobias
Am 2017-03-20 20:14, schrieb Tomas Habarta:
Actually, I likely managed to replicate the
I have a new pcap from beginning to the end with openldap "TLS
negoiation failed"
https://gwarband.de/openldap/tracefile.dump
The sourceports are 45376 and 45377
Tobias
Am 2017-03-20 19:59, schrieb Aki Tuomi:
Well, those actually *reduce* the possible algorithms that can be
used, so
I have also tested with 2.2.28 and this version has the same issue.
The finding of compatible ciphers is not the problem because I have
uncommented the ldap entrys:
TLSCipherSuite
SECURE128:-ARCFOUR-128:-CAMELLIA-128-CBC:-3DES-CBC:-CAMELLIA-128-GCM
TLSProtocolMin 3.1
Maybe
Can sombody say something about this request?
This is an email from the openldap-technical mailinglist from openldap.
Systemdetails are mention in the other email.
Originalnachricht
Betreff: Re: Dovecot can't connect to openldap over starttls
Datum: 2017-03-20 16:18
Absender:
I've tested your soulution, but it also says the same error.
I've tested all combinations of:
- tls_ca_cert_file =
- tls = yes
- tls_require_cert = demand
Every time it says "Connection error".
Only when tls is uncommented it says "TLS required".
Additional information
The serverlog of openldap with loglevel "any":
https://gwarband.de/openldap/openldap-connect.log
Note: openldap waits 1 Minute before he says "TLS negotiation failure"
after the connect.
and dovecot says direct "Connect error"
I've also delete the TLSCipherSuite from openldap.
Tobias
Am
I've replicate the settings from ldapsearch to dovecot but no success.
To the certificate:
Yes it's a *.crt file but I have linked the *.pem file to it and
dovecot has read access to that file.
I have enabled the debugging in dovecot and have uploaded the output:
Hello,
I have also installed LE certs.
But nothing helps, I have double-checking all certs.
ldapsearch with -ZZ works see:
https://gwarband.de/openldap/ldapsearch.log
I have also uploaded the TLSCACertificateFile, maybe I have a failure
in the merge of the two fiels:
Hello guys,
actually I'm trying to configure dovecot to access openldap for
passwordcheck.
My openldap is only allow access over "secure ldap".
The dovecot can communicate with the openldap server but there is maybe
a failure in the sslhandshake.
Additional information you can find in the
Hi,
Is it noted somewhere that Dovecot (v 2.0.9) doesn’t use case in directory
names in its config-files?
I found that out the hard way (i.e. a week of debugging)!!
in /etc/dovecot/conf.d/10-master.conf, the line:
unix_listener /var/spool/postOut/auth/dovecot-auth {
creates a:
Jul 29 22:15:58
On Tue, 12 Mar 2013 09:41:42 -0500, l...@airstreamcomm.net
l...@airstreamcomm.net wrote:
On 3/11/13 10:54 PM, i...@stos.se wrote:
Hi again,
this is what I've found regarding how Drupal 7 hashes.
$hash = md5($salt . $password, TRUE);
do {
$hash = md5($hash . $password, TRUE);
} while
Hi
I'm trying to get Dovecot to use Drupal users password for authenticating
IMAP users. But I just cant figure out how to make Dovecot understand the
password hash type that Drupal 7 is using.
My example user with password Teacher1 looks like this in Drupal database:
Do you have any clue on how to rewrite Dovecot to support Drupal 7 hashes?
I have a feeling this is going to become over my head.
Regards
Tobias
On Mon, 11 Mar 2013 20:40:16 -0400, Patrick Domack
patric...@patrickdk.com
wrote:
The issue is, drupal uses a custom password format.
You could
Hi!
I dont know if thats related. The specific error message in the log is that
the hash is not a valid one.
Regards
Tobias
On Mon, 11 Mar 2013 20:38:39 +0100, Andreas Meyer anme...@anup.de wrote:
Hello!
I took the thread back to the list.
Tobias Rådenholt tobias.radenh...@stos.se
Hi again,
this is what I've found regarding how Drupal 7 hashes.
$hash = md5($salt . $password, TRUE);
do {
$hash = md5($hash . $password, TRUE);
} while (--$count);
The whole final hash value is encoded into 16 base64 characters and
prepended by an identifying string, the standard phpass
, estudenoexterior.com, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]], header :contains
Subject E ai!, Essa voce Tem que Ver!) {
discard;
}
I'm using version 1.1.3
Best Regards,
Dennis
Timo Sirainen wrote:
On Wed, 2008-10-08 at 07:29 -0300, info
, estudenoexterior.com, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]], header :contains
Subject E ai!, Essa voce Tem que Ver!) {
discard;
}
I'm using version 1.1.3
Best Regards,
Dennis
Timo Sirainen wrote:
On Wed, 2008-10-08 at 07:29 -0300, info wrote
attached)
Timo Sirainen wrote:
On Tue, 2008-10-07 at 14:38 -0300, info wrote:
When a message header is split along several lines, it seems only the
first one is parsed by sieve.
The following header:
From:
=?iso-8859-1?Q?Cotiatododia=20-=20O=20Jornal=20de=20Not=EDcias=20a=20Se?=
=?iso-8859-1
Dear sirs
Thank you and congratulations for creating Dovecot.
When a message header is split along several lines, it seems only the
first one is parsed by sieve.
The following header:
From:
=?iso-8859-1?Q?Cotiatododia=20-=20O=20Jornal=20de=20Not=EDcias=20a=20Se?=
25 matches
Mail list logo
