https://bugs.koozali.org/show_bug.cgi?id=13244
--- Comment #2 from Brian Read <[email protected]> ---
Enhance the sieve variant as follows:
Here is a formatted list of the suggested things that Sieve could examine and
trigger on for email filtering:
- Standard Email Headers:
- List-Id
- From
- To
- Cc
- Subject
- Any other header, including custom headers
- Authentication-Results (SPF, DKIM, DMARC results added by MTA)
- Reply-To
- Received headers (e.g., checking path hops or specific addresses)
- Envelope-To and other envelope-related headers
- Spam-related headers (Spam Status, Spam Score) if added by spam filters
- Message Body Content:
- Keywords or phrases anywhere in the body
- Beginning or ending patterns
- Message Properties:
- Presence or absence of attachments (requires preprocessing, not native to
Sieve)
- Message size (usually handled outside Sieve)
- Session and Connection Information (via Dovecot or extended environments):
- Local IP address (server)
- Remote IP address (client)
- Local and remote ports
- Session identifiers
- Authentication-related environment variables (via vendor-specific
extensions)
- Custom Headers Added by Filters:
- Headers inserted by spam or virus scanners
- Headers indicating previous processing steps (e.g., X-Scanned headers added
by Sieve)
- Actions available include:
- Filing into mailboxes based on any of the above conditions
- Redirect or reject messages
- Adding/modifying headers (e.g., adding scan date header)
This list reflects the breadth of conditions that can be applied within Sieve
scripts, augmented by extensions or pre-delivery processing where needed. While
Sieve itself natively filters mainly on headers and body content, integration
with MTAs, spam filters, and server environments expands the scope of practical
filtering.[1][4][5][9][10][11][12][13]
This variety allows creating powerful and flexible server-side email filtering
tailored to a wide range of needs.
[1](https://doc.dovecot.org/main/core/man/sieve-test.1.html)
[2](https://manpages.debian.org/testing/dovecot-sieve/sieve-test.1.en.html)
[3](https://doc.dovecotpro.com/3.0.2/core/admin/testing.html)
[4](https://stackoverflow.com/questions/36306660/test-received-email-header-in-sieve)
[5](https://doc.dovecot.org/main/howto/sieve.html)
[6](https://gist.github.com/Hotrod369/6b7a24e1ea060e48e0c02459cbb950a0)
[7](https://dovecot.dovecot.narkive.com/EJCRZAFo/allowing-clients-to-test-their-sieve-scripts)
[8](https://talk.plesk.com/threads/global-dovecot-sieve-rule.341552/)
[9](https://blog.mailfence.com/email-filtering/)
[10](https://en.wikipedia.org/wiki/Email_filtering)
[11](https://www.cynet.com/malware/6-email-filtering-techniques-and-how-to-choose-a-filtering-service/)
[12](https://sebworks.com/sieve-email-filtering/)
[13](https://doc.dovecot.org/main/core/man/sieve-filter.1.html)
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
