~soywod/pimalaya#146: 
Support sieve

Status
REPORTED
Submitter
~liubog2008
Assigned to
No-one
Submitted
10 months ago
Updated
4 months ago
Labels
1:email-lib

~soywod 10 months ago

AFAIK, Sieve is for servers not clients, so I am not sure how it could interface with Himalaya.

Could you explain a bit more what you had in mind?

~liubog2008 10 months ago

Sieve is designed to be implementable on either a mail client or mail server. You can see the abstract in rfc5228.

  1. I hope to use sieve to filter and classify my mails.
  2. Different mail servers may have different filter rules. It's hard to mange.

Sieve script can be executed when himalaya sync.

~soywod 10 months ago

Sieve is designed to be implementable on either a mail client or mail server. You can see the abstract in rfc5228.

I read a bit and the first sentence confirms what I thought:

This document describes a language for filtering email messages at time of final delivery.

The main purpose of Sieve is to produce scripts for servers, so they are executed automatically. There is extensions to execute scripts from clients but it's not the main purpose.

  1. Different mail servers may have different filter rules. It's hard to mange.

Sieve script can be executed when himalaya sync.

IMHO this is out of the scope of Himalaya. But it could make sense as a subproject of Pimalaya. What could be better is to add sync hooks so you can plug whatever. What do you think?

~liubog2008 10 months ago

Fine, I'll try to do it by a new experimental project. Let me re-think the requirement of pimalaya in this project.

~soywod 4 months ago

However, the ManageSieve protocol could be a better fit for Pimalaya:

https://datatracker.ietf.org/doc/html/rfc5804

Register here or Log in to comment, or comment via email.