From: Joan Moreau
> I am trying to avoid closing/ reopening a file pointer to the exact same file
> between each call to the plugin
Can't you do an end-run around all this by having a persistent standalone
process that holds all your persistent data, and the plugin collects session
data and
Thanks Eduardo
I am trying to avoid closing/ reopening a file pointer to the exact same file
between each call to the plugin
On 14 March 2024 20:08:37 Eduardo M KALINOWSKI via dovecot
wrote:
On 14/03/2024 02:49, Joan Moreau via dovecot wrote:
No, you don´t understand
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
I could be wrong, but i believe dovecot submission is only a proxy to postfix
submission. Dovecot does not directly delivery mail to the world. Meaning the
mail is still passing through postfix
Hi,
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
On 14/03/2024 02:49, Joan Moreau via dovecot wrote:
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
* Tom Hendrikx via dovecot:
> Or in readable sieve: [...]
Do you mean to imply that regular expressions are not readable? ;-) All
it takes is a little practice. Besides, regex are more efficient. It is
well worth learning about them, and regex are really not as bad as some
make them out to be.
I do understand, and the problem is that your question is similar to asking how
to get a memory pointer from systemd for your program.
The short answer is, not doable.
The bit longer answer is that /usr/sbin/dovecot is a fancy service supervisor,
it's job is to launch and manage processes, it
