What I can think of without any experience using mail-crypt
- who says they need to be stored on the server? They need to be
available on the server when you start dovecot.
- and if you are using 3rd party external storage mounted on your
server. At least this 3rd party cannot access the email
I was reading through Dovecot mail-crypt plugin documentation and I'm
wondering what is the benefit of turning the encryption on if private
and public keys are both stored on the server?
What are the benefits and how the key can be protected (apart from
file permissions).
Cheers,
Chris
signatu
Hi,
My dovecot process seam blocked on dovecot/imap [blocking on log write],
only restart fix it.
How solve that's?
Cheers,
--
alpha_one_x86/BRULE Herman
Main developer of Supercopier/Ultracopier/CatchChallenger, Esourcing and server
management
IT, OS, technologies, research & development,
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 3:10 PM, Aki Tuomi wrote:
> > I am also not sure about sha512 hash because the Dovecot Variable wiki page
> > does not mention sha512 but only sha256. Is sha512 also available?
>
> Yes
Thank you Aki for confirming. I tried it out and it
Hi all,
The guidance provided so far has been really helpful, and has helped a
great deal to bringing down wasted energy on finding and executing a
viable path. I am now at the final due action to complete our Dovecot
application to our use-case, but am stuck on an issue that I cannot
find any eas
On 4.7.2019 16.05, mabi via dovecot wrote:
> ‐‐‐ Original Message ‐‐‐
> On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot
> wrote:
>
>> It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables
>>
>> I think the safest option would be setup LDAP so that the priv
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:18 AM, Aki Tuomi via dovecot
wrote:
> It depends. You can use either one, seehttps://wiki2.dovecot.org/Variables
>
> I think the safest option would be setup LDAP so that the private
> password would be only readable by self, and have
On 4.7.2019 15.35, mabi via dovecot wrote:
> ‐‐‐ Original Message ‐‐‐
> On Thursday, July 4, 2019 11:17 AM, @lbutlr via dovecot
> wrote:
>
>>> Is it possible to delete the inactive keypair? if yes how?
>> Wouldn’t you then be unable to *unencrypt* previous emails?
> That's also what I t
‐‐‐ Original Message ‐‐‐
On Thursday, July 4, 2019 11:17 AM, @lbutlr via dovecot
wrote:
> > Is it possible to delete the inactive keypair? if yes how?
>
> Wouldn’t you then be unable to *unencrypt* previous emails?
That's also what I thought but based on my understand and on the documen
Hi everybody...
I've inherited 2 servers with dovecot and fts_lucene enabled, which I
plan to switch to fts-solr instead. My plan is to disable lucene in
dovecot.conf, delete all cache associated files, and start configuring
the fts plugin from scratch. I need to make sure that I don't mess up
Hi,
Is Clucene no longer prefered/developed indexer?
Thanks.
Dave.
On 7/4/19, Felix Zielcke via dovecot wrote:
> Am Donnerstag, den 04.07.2019, 12:27 +0300 schrieb Aki Tuomi via
> dovecot:
>> On 4.7.2019 12.22, Maciej Milaszewski IQ PL via dovecot wrote:
>> > Hi
>> > So you're advised to use a
Am Donnerstag, den 04.07.2019, 12:27 +0300 schrieb Aki Tuomi via
dovecot:
> On 4.7.2019 12.22, Maciej Milaszewski IQ PL via dovecot wrote:
> > Hi
> > So you're advised to use a solr or something else?
> >
>
> Using any FTS is advisable, currently suitable ones would be SOLR or
> Xapian (see https
On 4 Jul 2019, at 03:17, @lbutlr via dovecot wrote:
> On 3 Jul 2019, at 06:38, mabi via dovecot wrote:
>> Is it possible to delete the inactive keypair? if yes how?
>
> Wouldn’t you then be unable to encrypt previous emails?
UNencrypt, of course.
On 4.7.2019 12.22, Maciej Milaszewski IQ PL via dovecot wrote:
>>> A few clients have 25K and more e-mail
>>>
>>> I thinking about use solr like:
>>> fts = solr
>>> fts_solr = debug url=http://IP:8983/solr/ (solr in external machine)
>>>
>>> Does it make sense ? use dovecot_indexes and fts ?
>>
>> A few clients have 25K and more e-mail
>>
>> I thinking about use solr like:
>> fts = solr
>> fts_solr = debug url=http://IP:8983/solr/ (solr in external machine)
>>
>> Does it make sense ? use dovecot_indexes and fts ?
>> What is the difference in performance?
>>
> Hi!
>
> Dovecot indexes a
On 4.7.2019 12.14, Maciej Milaszewski IQ PL via dovecot wrote:
> Hi
> I have a question about tunning dovecot-2.2.36.x
>
> Mail was stared in storage via nfs in MAILDIR via
> /home/us/usern...@domain.ltd/MAILDIR/
> I use additionally local dovecot_indexes via SSD disk
> (/var/dovecot_indexes%h)
>
On 2.7.2019 23.27, mabi wrote:
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, July 2, 2019 6:32 PM, Aki Tuomi via dovecot
> wrote:
>
>> I don't actually recommend using password directly from user as password for
>> private keys, I recommend running them thru some hash / pkcs5 before that.
>
On 3 Jul 2019, at 06:38, mabi via dovecot wrote:
> Is it possible to delete the inactive keypair? if yes how?
Wouldn’t you then be unable to encrypt previous emails?
On 4.7.2019 12.14, @lbutlr via dovecot wrote:
> On 3 Jul 2019, at 02:55, Peter Kahl via dovecot wrote:
>> I failed to disclose that the described problem occurs on iOS 13.0 beta.
>>
>> After trying again and again, it appears that a bug in iOS 13.0 beta is the
>> likely culprit. I am readin
Hi
I have a question about tunning dovecot-2.2.36.x
Mail was stared in storage via nfs in MAILDIR via
/home/us/usern...@domain.ltd/MAILDIR/
I use additionally local dovecot_indexes via SSD disk
(/var/dovecot_indexes%h)
A few clients have 25K and more e-mail
I thinking about use solr like:
fts =
On 4.7.2019 9.45, Laura Smith via dovecot wrote:
> There was a post on this topic to the list Aug 06, 2018 to which Aki replied
> "Thank you for reporting this, we'll take a look at this.".
>
> But its not clear what (if anything) has happened since ? The problem still
> seems to exist in 2.3.3
On 3 Jul 2019, at 02:55, Peter Kahl via dovecot wrote:
> I failed to disclose that the described problem occurs on iOS 13.0 beta.
>
> After trying again and again, it appears that a bug in iOS 13.0 beta is the
> likely culprit. I am reading on Reddit that there is some bug in iOS with
> cer
On 3 Jul 2019, at 01:28, Stephan Bosch via dovecot wrote:
> On 03/07/2019 04:44, @lbutlr via dovecot wrote:
>> I have the following in my active sieve file, and there are no errors logged.
>>
>>
>> if header :contains "to" "+root" {
>>setflag "\\Seen";
>>fileinto :create "root";
>>st
23 matches
Mail list logo
