Hey folks,
According to RFC 3028, the bare minimum Sieve actions are...
MUST: keep (deliver to INBOX), discard (drop on the floor), redirect
(aka forward). SHOULD: reject (aka bounce), fileinto (deliver other than
INBOX).
I'm going to get these, except for reject because it's hard, working for
As long as doing things in small steps doesn't make it harder, then I'm
all for it. Small steps are usually the best way to make sure something
gets done. If you try to bite off the whole project at once, it usually
dooms it to failure. The minimum you outlined below would be a HUGE
Aaron Stone wrote:
Hey folks,
According to RFC 3028, the bare minimum Sieve actions are...
MUST: keep (deliver to INBOX), discard (drop on the floor), redirect
(aka forward). SHOULD: reject (aka bounce), fileinto (deliver other than
INBOX).
I'm going to get these, except for reject
The following issue has been ACKNOWLEDGED.
==
http://www.dbmail.org/mantis/view.php?id=293
==
Reported By:weave
Assigned To:
The following issue has been RESOLVED.
==
http://www.dbmail.org/mantis/view.php?id=293
==
Reported By:weave
Assigned To:paul
On Wed, 2006-01-25 at 09:53 +0100, Paul J Stevens wrote:
Don't worry about vacation for now. The auto_reply functionality in 2.1
is doing just fine.
But it cannot be managed except by directly accessing the auto_reply
table. Vacation can be managed through the ManageSieve protocol.
Vacation
Aaron Stone wrote:
On Wed, 2006-01-25 at 09:53 +0100, Paul J Stevens wrote:
Don't worry about vacation for now. The auto_reply functionality in 2.1
is doing just fine.
But it cannot be managed except by directly accessing the auto_reply
table. Vacation can be managed through the
Hey guys Just taking a new look at the code you guys have been working
so hard on. Looks really good! I have a minor patch that doesn't even
warrent a bug report so I have attached it here.
On another note I wanted to know if either Arron or Paul have tried the
current svn trunk on x86_64 bit
