[Bug 3184] New: -bI:sieve crashes if DISABLE_SIEVE_FILTER=yes

Exim Bugzilla via Exim-dev <[email protected]>
Newsgroups gmane.mail.exim.devel
Message-ID <[email protected]/>
https://bugs.exim.org/show_bug.cgi?id=3184

            Bug ID: 3184
           Summary: -bI:sieve crashes if DISABLE_SIEVE_FILTER=yes
           Product: Exim
           Version: 4.99
          Hardware: x86
                OS: FreeBSD
            Status: NEW
          Severity: bug
          Priority: medium
         Component: General execution
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

# exim -bI:sieve
2025-12-22 09:07:59 SIGSEGV (fault address: (nil))
2025-12-22 09:07:59 SIGSEGV (null pointer indirection)
2025-12-22 09:07:59 SIGSEGV (fresh-exec:   519 initializing
)
2025-12-22 09:07:59 backtrace
2025-12-22 09:07:59 ---
2025-12-22 09:07:59     0x27e1e4 <stackdump+0x24> at /usr/local/bin/exim
2025-12-22 09:07:59     0x287178 <segv_handler+0x98> at /usr/local/bin/exim
2025-12-22 09:07:59     0x8295e24af <pthread_sigmask+0x54f> at /lib/libthr.so.3
2025-12-22 09:07:59     0x8295e1a6b <pthread_setschedparam+0x85b> at
/lib/libthr.so.3
2025-12-22 09:07:59     0x820e932d3 <OCSP_RESPONSE_new+0x820b6cd93> at ???
2025-12-22 09:07:59     0x27d533 <misc_mod_find+0x53> at /usr/local/bin/exim
2025-12-22 09:07:59     0x287feb <show_exim_information+0x2b> at
/usr/local/bin/exim
2025-12-22 09:07:59     0x28506e <main+0x631e> at /usr/local/bin/exim
2025-12-22 09:07:59     0x82798fe34 <__libc_start1+0x124> at /lib/libc.so.7
2025-12-22 09:07:59 ---

Commenting out DISABLE_SIEVE_FILTER=yes

# exim -bI:sieve
comparator-i;ascii-numeric
copy
encoded-character
enotify
envelope
fileinto
subaddress
vacation

Exim version 4.99.1-121-7873db47a #1 built 18-Dec-2025 12:33:47

also with 4.99.1-135-6d75a89d2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.