schleuder issueshttps://0xacab.org/schleuder/schleuder/-/issues2018-10-28T11:48:49Zhttps://0xacab.org/schleuder/schleuder/-/issues/33Language for subscriptions2018-10-28T11:48:49ZpazLanguage for subscriptionsEach subscription should have its own language-setting to enable people with different language-capabilities use a list together.Each subscription should have its own language-setting to enable people with different language-capabilities use a list together.Futurehttps://0xacab.org/schleuder/schleuder/-/issues/49Optionally attach incoming message?2020-01-05T13:19:36ZpazOptionally attach incoming message?Have the originally incoming message attached to the message sent to subscribers (if configured).
Pro:
+ Subscribers would be able to verify some signatures by themselves.
Contra:
- Headers would leak to other subscribers
- Enc...Have the originally incoming message attached to the message sent to subscribers (if configured).
Pro:
+ Subscribers would be able to verify some signatures by themselves.
Contra:
- Headers would leak to other subscribers
- Encrypted messages can't be decrypted by the subscriber, encrypted+signed neither.
My conclusion right now: it's not worth the effort, because only originally unencrypted messages can be verified at all. https://0xacab.org/schleuder/schleuder/-/issues/52Notify subscribers of changes to the list2020-01-05T13:11:30ZpazNotify subscribers of changes to the listSee schleuder/schleuder#10See schleuder/schleuder#10https://0xacab.org/schleuder/schleuder/-/issues/54Add more control over resending2019-10-16T20:50:52ZpazAdd more control over resendingSee schleuder/schleuder#15See schleuder/schleuder#15https://0xacab.org/schleuder/schleuder/-/issues/73Send usage-hints in case of keyword-errors.2020-01-05T13:11:16ZpazSend usage-hints in case of keyword-errors.Currently we're only sending an error-message and people have to guess or try to find documentation via the browser if using a keyword fails.Currently we're only sending an error-message and people have to guess or try to find documentation via the browser if using a keyword fails.https://0xacab.org/schleuder/schleuder/-/issues/75Implement message queuing2020-01-05T15:36:19ZpazImplement message queuingImplement a queue between MTA and schleuder (and back to MTA).
Best idea so far: Use a Maildir-structure and a daemon that monitors the `new`-directory.
* The MTA drops the messages into the Maildir (a global one vs. one per list?)...Implement a queue between MTA and schleuder (and back to MTA).
Best idea so far: Use a Maildir-structure and a daemon that monitors the `new`-directory.
* The MTA drops the messages into the Maildir (a global one vs. one per list?)
* The monitoring daemon detects a new message and writes the message into STDIN of a newly started schleuder-process.
* Either:
* schleuder runs the message and sends outgoing messages via sendmail or smtp (like before)
* Or:
* schleuder runs the message and drops any outgoing message into an outgoing Maildir.
* Another monitoring daemon detects that new message and gives it to the MTA.
The advantage of this setup is a separation of schleuder from the MTA without much responsibility for schleuder to care for MTA-failures. In case of delivery errors the outgoing monitoring daemon simply moves the message back from `tmp` to `new` and tries again in a few minutes. Schleuder only needs to care about successfully writing into a directory.https://0xacab.org/schleuder/schleuder/-/issues/89add a 'description' to list options2020-01-04T12:31:11Zpazadd a 'description' to list optionssometimes (i.e. in the overview in webschleuder) it would be useful to have a 'description' for lists to help identifying them (like mailman has in the list overview).sometimes (i.e. in the overview in webschleuder) it would be useful to have a 'description' for lists to help identifying them (like mailman has in the list overview).Futurehttps://0xacab.org/schleuder/schleuder/-/issues/97Enable replacing list-key2020-01-04T11:47:21ZpazEnable replacing list-keySchleuder should provide the possibility to replace the list-key, either by a newly generated one, or by a provided one.
The new key should optionally (true by default) be signed by the old key to make the transition easier for users....Schleuder should provide the possibility to replace the list-key, either by a newly generated one, or by a provided one.
The new key should optionally (true by default) be signed by the old key to make the transition easier for users.
The option should be provided by the API and be used by Webschleuder and SchleuderConf.
(This feature would also serve the feature request to be able to nuke list-keys in case of compromisation (which was never filed, only told).)Futurehttps://0xacab.org/schleuder/schleuder/-/issues/125Strip signed-text-markers from inline-clearsigned messages and strip surround...2017-12-11T01:54:06ZpazStrip signed-text-markers from inline-clearsigned messages and strip surrounding textmail-gpg makes sure it's clear which part of a inline-clearsigned message actually was signed my checking for or inserting marker-lines so the message looks like this one:
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
blafo...mail-gpg makes sure it's clear which part of a inline-clearsigned message actually was signed my checking for or inserting marker-lines so the message looks like this one:
```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
blafoo
-----END PGP SIGNED MESSAGE-----
```
I would rather strip anything before and after the signed text from being passed on to the list.