Unable to Enable Encryption (Solution: webadmin mismatch)

[crocsinsocks]

Issue Description

Unable to Enable Encryption

v0.15.4

ERROR Bad resource parameters (resource.bad-parameters) ... reason = "missing field `allow_spam_training`"

Issue stems from requirement added here:

stalwart/crates/http/src/management/crypto.rs

Lines 89 to 102 in f1fe034

	let request = serde_json::from_slice::<EncryptionType>(body.as_deref().unwrap_or_default())
	.map_err(|err| trc::ResourceEvent::BadParameters.into_err().reason(err))?;
	let (method, algo, mut certs, allow_spam_training) = match request {
	EncryptionType::PGP {
	algo,
	certs,
	allow_spam_training,
	} => (EncryptionMethod::PGP, algo, certs, allow_spam_training),
	EncryptionType::SMIME {
	algo,
	certs,
	allow_spam_training,
	} => (EncryptionMethod::SMIME, algo, certs, allow_spam_training),

Yet, this property/field is not present in the UI resulting in the error.

Thanks

Expected Behavior

No response

Actual Behavior

No response

Reproduction Steps

No response

Relevant Log Output

No response

Stalwart Version

v0.15.x

Installation Method

Built from source

Database Backend

PostgreSQL

Blob Storage

S3-compatible

Search Engine

Elasticsearch

Directory Backend

Internal

Additional Context

No response

I acknowledge that:

• I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.
• I have searched the Stalwart repository (both open and closed Discussions and Issues) and confirm this is not a duplicate.
• I have set the logging level to trace and included relevant log output if applicable.
• I agree to follow the project's Code of Conduct.

[mdecimus]

Update the webadmin to the latest version.

[crocsinsocks]

I am running in a non persistent container compiled with below?

...
RUN git clone https://github.com/stalwartlabs/stalwart.git

WORKDIR /build/stalwart

RUN git checkout "tags/v0.15.4"

RUN cargo build --release -p stalwart --no-default-features --features "postgres s3 redis zenoh"
RUN cargo build --release -p stalwart-cli
...

[crocsinsocks]

I thought on restart the webadm was pulled and moved to local /tmp. This is the case but from the blob store (not from github)..

You can manually update in the UI or set below:

[webadmin]
auto-update = true

See docs: https://stalw.art/docs/management/webadmin/update

I can see why auto-update is not the default as you can end up with the same problem.. This is compatibility issue that I think should be resolved.

Would it not make sense to improve the update or rather webadmin pull, to ensure whatever version of stalwart you a running you are using the most-up-to-date compatible Web UI version (this could mean both downgrade / upgrade due to roll back cases).

[andreymal]

#1567