On 10/18/20 10:28 PM, Aki Tuomi wrote:
doveadm(myu...@example.com): Panic: file mail-storage.c: line 2112
(mailbox_get_open_status): assertion failed: (box->opened)
...
I can reproduce your problem with the `fts lookup` command. Luckily it's
equivalent to running `doveadm search`.
I have implemented this change and the core dumps went away.
It appears so far that it's indeed the right fix.
Has this change been introduced in 2.3.11.3 ?
Thanks!
On Tuesday, 27/10/2020 at 08:20 John Fawcett wrote:
On 22/10/2020 10:23, John Fawcett wrote:
On 21/10/2020 19:00, John
On Fri, 2020-10-30 at 12:21 -0600, @lbutlr wrote:
> On 30 Oct 2020, at 11:25, Bernd Petrovitsch wrote:
> > On 30/10/2020 17:11, @lbutlr wrote:
> > [...]
> > > echo $1 | sed -e '||* {color:white !important;
> > > background-color: black !important; } |'
> >
> > What should the sed stuff do?
>
>
On Fri, 2020-10-30 at 19:57 +0200, Aki Tuomi wrote:
> > On 30/10/2020 19:25 Bernd Petrovitsch wrote:
> >
> >
> > On 30/10/2020 17:11, @lbutlr wrote:
> > [...]
> > > echo $1 | sed -e '||* {color:white !important;
> > > background-color: black !important; } |'
> >
> > What should the sed stuff
> "@lbutlr" == @lbutlr writes:
@lbutlr> On 30 Oct 2020, at 12:34, @lbutlr wrote:
>> I am not sure about the $1. I think filter just pipes the message (or part
>> of the message.
>>
>> I will see what happens without the echo I suppose.
>>
>> Nope, still the same.
>>
>> 32: starting
On 30 Oct 2020, at 12:34, @lbutlr wrote:
> I am not sure about the $1. I think filter just pipes the message (or part of
> the message.
>
> I will see what happens without the echo I suppose.
>
> Nope, still the same.
>
> 32: starting `:contains' match with `i;ascii-casemap' comparator:
>
> On 30/10/2020 20:34 @lbutlr wrote:
>
>
> On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> > But I think the sed here is missing 's' from start, so this does not
> > actually do anything...
>
> Copy/paste/edit error. The s is there in the file.
>
> darkmode.sh:
> #!/bin/sh
> echo $1 | sed
On Freitag, 30. Oktober 2020 18:11:46 CET @lbutlr wrote:
> echo $1 | sed -e '||* {color:white !important;
> background-color: black !important; } |'
echo $1 | sed -e 's||.* {color:white !important; background-
color: black !important; } |'
Perhaps?
On Fri, Oct 30, 2020 at 11:34 AM @lbutlr wrote:
> On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> > But I think the sed here is missing 's' from start, so this does not
> actually do anything...
>
> Copy/paste/edit error. The s is there in the file.
>
> darkmode.sh:
> #!/bin/sh
> echo $1 | sed -e
On 30 Oct 2020, at 11:57, Aki Tuomi wrote:
> But I think the sed here is missing 's' from start, so this does not actually
> do anything...
Copy/paste/edit error. The s is there in the file.
darkmode.sh:
#!/bin/sh
echo $1 | sed -e 's||* {color:white !important; background-color:
black
On 30 Oct 2020, at 11:25, Bernd Petrovitsch wrote:
> On 30/10/2020 17:11, @lbutlr wrote:
> [...]
>> echo $1 | sed -e '||* {color:white !important;
>> background-color: black !important; } |'
>
> What should the sed stuff do?
Changes to * {color:white !important; background-color: black
On 30 Oct 2020, at 11:26, PGNet Dev wrote:
> wrong, or different, I can't say. if helpful, for my script executions, I
> successfully do
>
> require ["vnd.dovecot.pipe", "vnd.dovecot.filter",
> "vnd.dovecot.execute", "copy", "environment", "variables",
> "vnd.dovecot.debug",
On Fri, 30 Oct 2020 at 20:12, @lbutlr wrote:
> So, I have the sieve working up to the point that it calls the script, and
> the script is called (I get different errors if the script is not there,
> for example).
>
> filter action
> execute program `darkmode.sh'
> [[EXECUTION ABORTED]]
>
>
> On 30/10/2020 19:25 Bernd Petrovitsch wrote:
>
>
> On 30/10/2020 17:11, @lbutlr wrote:
> [...]
> > echo $1 | sed -e '||* {color:white !important;
> > background-color: black !important; } |'
>
> What should the sed stuff do?
> TTBOMK '|' is not known by sed ...
>
> MfG,
> Bernd
On 10/30/20 10:11 AM, @lbutlr wrote:
So, I have the sieve working up to the point that it calls the script, and the
script is called (I get different errors if the script is not there, for
example).
filter action
execute program `darkmode.sh'
[[EXECUTION ABORTED]]
On 30/10/2020 17:11, @lbutlr wrote:
[...]
> echo $1 | sed -e '||* {color:white !important;
> background-color: black !important; } |'
What should the sed stuff do?
TTBOMK '|' is not known by sed ...
MfG,
Bernd
--
There is no cloud, just other people computers.
--
I'm running
dovecot --version
2.3.11.3 (502c39af9)
folder sharing is enabled & working.
as long as I manually enable enable sharing for each folder/subfolder.
e.g., if I enable sharing for each of:
sharedtopfolder
subfolder1
So, I have the sieve working up to the point that it calls the script, and the
script is called (I get different errors if the script is not there, for
example).
filter action
execute program `darkmode.sh'
[[EXECUTION ABORTED]]
There's no other error logged (for example, when I had
On 30 Oct 2020, at 07:27, @lbutlr wrote:
> I have tried the following to match the string '' in the body of an
> email:
>
> if body :raw :contains "" {
> if body :content "text/html" :contains "" {
> if body :contains "" {
Never mind, I was sending the wrong test mail through.
--
If the
I have tried the following to match the string '' in the body of an
email:
if body :raw :contains "" {
if body :content "text/html" :contains "" {
if body :contains "" {
All three result in
matching value `'
with key `' => 0
finishing match with result: not matched
RFC 5173
I doubt there is a way to do that when using the SOGo web UI.
On Fri, 30 Oct 2020 at 15:57, Tom Talpey wrote:
> You might consider adding "stop;" after the fileinto, otherwise
> a second match might process the message again, moving it
> elsewhere, etc.
>
> Tom.
>
> On 10/30/2020 5:47 AM,
You might consider adding "stop;" after the fileinto, otherwise
a second match might process the message again, moving it
elsewhere, etc.
Tom.
On 10/30/2020 5:47 AM, Odhiambo Washington wrote:
Answering to myself,
The issue was as a result of a config parameter for SOGo:
Changed
Hello.
If running dovadm replicator status, i get something like the following.
root@mail2:~# doveadm replicator status
Queued 'sync' requests 0
Queued 'high' requests 0
Queued 'low' requests 0
Queued 'failed' requests 0
Queued 'full resync' requests 4
Waiting
Hi
We are very eager to test the zstd compression in the upcoming Dovecot 2.3.12
release - any pointer as to when that is expected to be released?
Kind Regards,
Sidsel
signature.asc
Description: Message signed with OpenPGP
Answering to myself,
The issue was as a result of a config parameter for SOGo:
Changed
NGImap4ConnectionStringSeparator = "/";
to
NGImap4ConnectionStringSeparator = ".";
and the problem is solved.
On Fri, 30 Oct 2020 at 11:43, Odhiambo Washington
wrote:
> Hello good people,
>
> I have
Hello good people,
I have dovecot- 2.3.7.2 (Ubuntu Ubuntu 20.04.1 LTS) running fine.
However, I have a hitch with mail filtering.
Using SOGo as the webmail UI, I created a filter rule which resulted into
the rule below:
require ["fileinto"];
if allof (address :contains "from" "odhiambo") {
26 matches
Mail list logo
