Re: sieve question

Hello,

In the Message; 

  Subject    : Re: sieve question
  Message-ID : <[email protected]>
  Date & Time: Fri, 03 Jul 2026 11:07:41 +0200

[mh] == [email protected] has written:

mh>  On Freitag, 3. Juli 2026 04:08:47 Mitteleuropäische Sommerzeit Masaru Nomiya wrote:
mh>  > Hello,
mh>  > 
mh>  > In the Message; 
mh>  > 
mh>  >   Subject    : sieve question
mh>  >   Message-ID : <[email protected]>
mh>  >   Date & Time: Thu, 02 Jul 2026 20:40:33 +0200
mh>  > 
mh>  > [mh] == [email protected] has written:
[...]
mh> >> It always gets to the else branch, when I get a mail from the bug
mh> >> list.
mh> >> If I copy the Subject line from the file in my dovecot maildir
mh> >> and send a mail manually with this subject it works as expected -
mh> >>  the mail will be filed into bugs-vul.
 
MN>> How about this?
 
MN>>     header :regex "Subject" "\\s+VUL\-[0-9]:\\s+"
                      |
                      Y
MN>>     header :regex "Subject" "VUL\-[0-9]:\\s+"

mh>  thx, but this also doesn't work,

MN>> In short, don't emails from ML start without a space?

mh>  The subject line looks like that:

mh>  "Subject: [Bug 1270051] VUL-0: chromium: security fixes in 150.0.7871.46"
mh>  I can check my regex against that string using perl, python,
mh>  ... - it always succeeds, but not within my sieve script.

Ah, I see.

The [] symbol needs to be escaped.

How does this?

    header :regex "Subject" "\\[[^]]*\\]\\s*VUL-[0-9]+:"

But as a safe and reliable method, I'd recommend doing it this way,
wouldn't you?

	 if anyof(
    	    header :contains "Subject" "VUL-",
    	    header :contains "Subject" "VUL.0"
	 ) {
    	    fileinto :create "Mailarchiv/nach Themen/Computer & Elektronik - System - linux - opensuse - bugs-vul";
	 } else {
            fileinto :create "Mailarchiv/nach Themen/Computer & Elektronik - System - linux - opensuse - bugs";
}

Best Regards & Good Night.

--
┏━━┓彡   Masaru Nomiya                   mail-to: nomiya @ ab.auone-net.jp
┃＼／彡
┗━━┛       "Charlie is different. There are several steps to how it works,
	        but to lay it out simply, imagine that all your data is stored
		in a vault owned and controlled by you. Charlie is effectively
		the gatekeeper to that vault and will interact on your behalf
		with any LLMs that request access to your data. Before it hands
		anything over, it will first ask for your permission. "

  --"Charlie Is an AI Assistant Built to Serve You, Not Our AI Overlords" --