We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot start stalwart server anymore. after changing a system sieve script via web admin some part might got written that cannot be interpreted.
I can reproduce the problem by doing the following steps: no, because I have no access at the moment due to the error.
v0.10.x
RocksDB
LDAP
Linux
~# RUST_BACKTRACE=full /opt/stalwart-mail/bin/stalwart-mail -c /opt/stalwart-mail/etc/config.toml thread 'main' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/sieve-rs-0.5.2/src/compiler/grammar/instruction.rs:915:72: index out of bounds: the len is 11 but the index is 11 stack backtrace: 0: 0x55abc927777b - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h304520fd6a30aa07 1: 0x55abc7f6fd0b - core::fmt::write::hf5713710ce10ff22 2: 0x55abc923b682 - std::io::Write::write_fmt::hda708db57927dacf 3: 0x55abc9278a90 - std::panicking::default_hook::{{closure}}::he1ad87607d0c11c5 4: 0x55abc92799bf - std::panicking::rust_panic_with_hook::had2118629c312a4a 5: 0x55abc9279485 - std::panicking::begin_panic_handler::{{closure}}::h7fa5985d111bafa2 6: 0x55abc92793e9 - std::sys::backtrace::__rust_end_short_backtrace::h704d151dbefa09c5 7: 0x55abc92793d4 - rust_begin_unwind 8: 0x55abc6b86802 - core::panicking::panic_fmt::h3eea515d05f7a35e 9: 0x55abc6b867c6 - core::panicking::panic_bounds_check::hab02a8df06d3a143 10: 0x55abc8f2df2f - sieve::compiler::lexer::string::<impl sieve::compiler::grammar::instruction::CompilerState>::tokenize_string::h96cabd0372e6bd08 11: 0x55abc8f27fe0 - sieve::compiler::grammar::<impl sieve::compiler::grammar::instruction::CompilerState>::parse_strings_token::h8a81060531f7439d 12: 0x55abc8f178bf - sieve::compiler::grammar::test::<impl sieve::compiler::grammar::instruction::CompilerState>::parse_test::hac98798ea5482868 13: 0x55abc8ef6158 - sieve::compiler::grammar::instruction::<impl sieve::Compiler>::compile::he70dff95a469ae2d 14: 0x55abc78b32ce - common::config::scripts::Scripting::parse::{{closure}}::h9f011f904d021687 15: 0x55abc78ac78e - common::config::<impl common::Core>::parse::{{closure}}::hf1396920f2e331f4 16: 0x55abc78c0db7 - common::manager::boot::BootManager::init::{{closure}}::hf25178651833245c 17: 0x55abc7b7f099 - stalwart_mail::main::{{closure}}::h08437ce716068ba4 18: 0x55abc7b7c590 - stalwart_mail::main::hf1e7fe55ff7f3909 19: 0x55abc6e2b933 - std::sys::backtrace::__rust_begin_short_backtrace::he4029bbf106fc265 20: 0x55abc6e2b730 - std::rt::lang_start::{{closure}}::h072958b473fb9e84 21: 0x55abc7b8f2e0 - main 22: 0x7f9a0624624a - <unknown> 23: 0x7f9a06246305 - __libc_start_main 24: 0x55abc6c83bde - _start 25: 0x0 - <unknown>
The text was updated successfully, but these errors were encountered:
stalwartlabs/sieve@0e24d13
Bump sieve-rs to 0.5.3 (fixes #941)
6d26cb5
Can you try compiling the latest version from the main repository? Here are the instructions.
main
Once you have Stalwart back online please kindly post here the sieve script that is failing to compile.
Sorry, something went wrong.
No branches or pull requests
What happened?
cannot start stalwart server anymore. after changing a system sieve script via web admin some part might got written that cannot be interpreted.
How can we reproduce the problem?
I can reproduce the problem by doing the following steps:
no, because I have no access at the moment due to the error.
Version
v0.10.x
What database are you using?
RocksDB
What blob storage are you using?
RocksDB
Where is your directory located?
LDAP
What operating system are you using?
Linux
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: