Skip to content
New issue

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

Some malformed sieve filters are not rejected. #23

Open
5 tasks done
JulienPalard opened this issue Sep 25, 2024 · 0 comments
Open
5 tasks done

Some malformed sieve filters are not rejected. #23

JulienPalard opened this issue Sep 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@JulienPalard
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
  • ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
  • ... I have understood that answers are voluntary and community-driven, and not commercial support.
  • ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

Bonjour,

In the filter interface, many typos are properly found and cause the whole script to be rejected, with a redish error message, this is good.

Sadly a few minor errors are **not** detected, leading to a greenish success message (misleading for the user!). Because as the script contains errors it will **not** be applied at all at runtime.

A simple example is:


require ["fileinto"];

if address :is "To" "[email protected]" {
    fileinto :create "pouette";
}


The error here is the missing `mailbox` requirement.

Logs:

ø

Steps to reproduce:

1. Go to the sieve filter editor
2. Copy past my previous example
3. Save it, see green success messag
4. Test the sieve filter by sending an email to your test mailbox
5. See that the filter has not been applied.

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

ø

Server/VM specifications:

ø

Is Apparmor, SELinux or similar active?

ø

Virtualization technology:

ø

Docker version:

ø

docker-compose version or docker compose version:

ø

mailcow version:

ø

Reverse proxy:

ø

Logs of git diff:

ø

Logs of iptables -L -vn:

ø

Logs of ip6tables -L -vn:

ø

Logs of iptables -L -vn -t nat:

ø

Logs of ip6tables -L -vn -t nat:

ø

DNS check:

All those mandatory field are a PITA when reporting a front-end issue.
@JulienPalard JulienPalard added the bug Something isn't working label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant