ManageSieve for Everyone #504
Conversation
|
Your Render PR Server URL is https://infra-pr-504.onrender.com. Follow its progress at https://dashboard.render.com/static/srv-cr6bi78gph6c73bmungg. |
github-actions
bot
added
group: ansible
| Sieve scripts are managed via [the ManageSieve | ||
| protocol](https://datatracker.ietf.org/doc/html/rfc5804). Your e-mail client | ||
| should have built-in functionality for writing and editing these scripts. For a | ||
| listing of clients, see [the official Sieve website](sieve.info/clients.). |
There was a problem hiding this comment.
This link renders wrong, also, sieve.info only works over HTTP:
| listing of clients, see [the official Sieve website](sieve.info/clients.). | |
| listing of clients, see [the official Sieve website](http://sieve.info/clients). |
There was a problem hiding this comment.
Fixed in amended commit.
| protocols = imap lmtp | ||
|
|
||
| # PYDIS CONFIG END | ||
|
|
There was a problem hiding this comment.
I'm sure there is a reason, but why is this diff removed?
There was a problem hiding this comment.
The default protocols includes the managesieve endpoint. I figured instead of amending it here, just relying on the bundled protocols setting (via the include) is good.
There was a problem hiding this comment.
Have I understood correctly that our mail server already supports sieve, but we were merely blocking it in our firewall?
We're using Dovecot, so do we have the sieve plugin already installed and configured?
Correct, it came in the Dovecot PR but we didn't enable it.
Yes, Sieve is installed and configured. By default, it's looking for config in the |
A spectre is haunting Python Discord -- the spectre of proprietary mail filtering programs. All the Powers of Big Mail have entered into a holy alliance to exorcise this spectre: Outlook and GMail, Yahoo and Zoho, AOL adn iCloud. Where is the open protocol in opposition that has not been decried as unprofessional, free and open source by its opponents in power? Where is the Opposition that has not hurled back the branding reproach of Internet Standards, against the more advanced opposition protocols, as well as against its reactionary adversaries? Two things result from this fact. I. Sieve is already standardized as a protocol via the IETF. II. It is high time that Python Discord users should openly, in the face of the TLS-encrypted internet, filter their notifications, their love letters, their mailing lists, and meet this nursery tale of the Spectre of ManageSieve with a Manifesto of Python Discord Devops itself. To this end, ManageSieve users of various nationalities have assembled on jitsi.pydis.wtf, and sketched the following commit, to be published on the lovelace Python Discord e-mail service.
jchristgit
force-pushed
the
managesieve
branch
from
9cd674b
to
10e297a
Compare
Directories under /var/vmail are no longer all owned by `vmail`, but instead `$ldap_uid:vmail`.
|
@jb3 please check again, this is live |
There was a problem hiding this comment.
Works great.
Can we recommend https://github.com/thsmi/sieve as a client as well as sieve-connect?
I've tried this myself and not only does it work great but it also has a nice graphical overview of rule processing which might be easier for non-technical users (as well as of course allowing for manual sieve editing).
OctoDNS Plan for
|
| Operation | Name | Type | TTL | Value | Source |
|---|---|---|---|---|---|
| Delete | munin | CNAME | 300 | lovelace.box.pydis.wtf. |
Summary: Creates=0, Updates=0, Deletes=1, Existing Records=43
|
@jb3 added, please check again |
As suggested by Joe.
|
Merged into main. Thanks! |
A spectre is haunting Python Discord -- the spectre of proprietary mail
filtering programs. All the Powers of Big Mail have entered into a holy
alliance to exorcise this spectre: Outlook and GMail, Yahoo and Zoho,
AOL adn iCloud.
Where is the open protocol in opposition that has not been decried as
unprofessional, free and open source by its opponents in power? Where is
the Opposition that has not hurled back the branding reproach of
Internet Standards, against the more advanced opposition protocols, as
well as against its reactionary adversaries?
Two things result from this fact.
I. Sieve is already standardized as a protocol via the IETF.
II. It is high time that Python Discord users should openly, in the face
of the TLS-encrypted internet, filter their notifications, their love
letters, their mailing lists, and meet this nursery tale of the Spectre
of ManageSieve with a Manifesto of Python Discord Devops itself.
To this end, ManageSieve users of various nationalities have assembled
on jitsi.pydis.wtf, and sketched the following commit, to be published
on the lovelace Python Discord e-mail service.