No, you don´t understand
There is a core process (/usr/bin/dovecot) running all the time. So I want to
allocate a memory block, the core process keep it and it is retrievable by the
pluging when laded again
At exit of /usr/bin/dovecot, it just does a "delete()" of the said allocation
On 2024-03-1
Hi!
Sorry but that's just not possible, ther is no "core" where to create such
object. There is no "dovecot" where to store things.
When user logs in, dovecot executes /usr/libexec/dovecot/imap and transfers the
connection fd there. then plugins and stuff are loaded, and the user does what
he
On 13-03-2024 17:36, Ralph Seichter via dovecot wrote:
* Lev Serebryakov:
I need to match all messages sent from some specific domain and all
its sub-domains.
I prefer using regular expressions for this kind of tests:
if address :regex "From" "[@.]example\.(com|org)$" {...}
This will
No, I am not referring to that
I want to create an object at first call in memory
that object would be retrievable at second and furthers calls of the plugin, as
long as dovecot is running
On 2024-03-13 16:29, Aki Tuomi via dovecot wrote:
Not really no. You should use e.g. dict inteface fo
* Lev Serebryakov:
> I need to match all messages sent from some specific domain and all
> its sub-domains.
I prefer using regular expressions for this kind of tests:
if address :regex "From" "[@.]example\.(com|org)$" {...}
This will match all addresses for example.com, example.org and their
Hello!
I need to match all messages sent from some specific domain and all its
sub-domains. I can achieve this with:
if address :match :domain "From" [ "domain.com", "*.domain.com" ] { ... }
But it looks ugly, especially if repeated for 5-6 domains.
Is here way better? `:match ["*dom
Hi
I have 1 director and ~8 dovecot nodes. I thinking about Solr cluster beacuse
one server solr probably is not enough.
I thinking about SolrCloud Mode but I don't know if it will work with Dovecot
And if not SolrCloud Mode, then what?
I don't have much experience in Solr clustering and I want t
On 13/03/24 22:30, Stuart Henderson wrote:
I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quie=
t
That's not a valid test. openssl >=1.1.1 s_client uses SNI by default,
with libressl or older openssl you need to use -servername.
Indeed, you want: openssl s_client -conn
Hi,
I'm having some problems after activating the quota plugin: I followed
the guide from the doc[0] but I'm having problems with some virtual user.
I understand that,with my conf,the quota plugin check the limit of a
user and then tell postfix to accept/discard the mail. i have some users
unde
On 2024-03-12, steffan--- via dovecot wrote:
> I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips=
> that=92s been fine for quite some time. Recently I started getting complai=
> nts related to SNI.
>
> I test with this: openssl s_client -connect mail.domain.com:993 -crlf
Dear maintainer,
there is potentially conflicting information in dovecot doc about the
count quota backend.
According to
https://doc.dovecot.org/configuration_manual/quota/quota_count/
the count quota backend is the recommended way of calculating quota on
recent Dovecot
installations.
But
Not really no. You should use e.g. dict inteface for storing this kind of
stateful data. When deinit is called the calling core process will likely die
too.
Aki
> On 13/03/2024 10:19 EET Joan Moreau wrote:
>
>
> Keep a pointer in memory retrievable each time a plugin is called
>
> So the pl
Keep a pointer in memory retrievable each time a plugin is called
So the plugin keep the memory, not has to restart everything at each call
On 12 March 2024 08:53:38 Aki Tuomi via dovecot wrote:
On 11/03/2024 10:42 EET Joan Moreau wrote:
Hi
Is it possible, fro
> On 12/03/2024 22:54 EET steffan--- via dovecot wrote:
>
>
> I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips
> that’s been fine for quite some time. Recently I started getting complaints
> related to SNI.
>
> I test with this: openssl s_client -connect mail.doma
14 matches
Mail list logo