schleuder issueshttps://0xacab.org/schleuder/schleuder/-/issues2021-06-01T19:57:48Zhttps://0xacab.org/schleuder/schleuder/-/issues/497Consider setting Mail-Followup-To header when Reply-To is set to original sender2021-06-01T19:57:48Zabc defConsider setting Mail-Followup-To header when Reply-To is set to original senderWhen REPLY-TO is set to the original sender, users have complained that when they hit "Reply-All" (Reply-To-All) in their clients, they expect to send a mail to the original sender AND the list (`FROM(list)+REPLY-TO(original sender)+TO(r...When REPLY-TO is set to the original sender, users have complained that when they hit "Reply-All" (Reply-To-All) in their clients, they expect to send a mail to the original sender AND the list (`FROM(list)+REPLY-TO(original sender)+TO(recipient)+CC`). Instead, the TO header is set to `REPLY-TO(original sender)+TO(recipient)+CC` and thus not including the list.
I investigated this and it seems that most mail clients [follow this procedure](https://wiki.mozilla.org/Thunderbird:Help_Documentation:Mail-Followup-To_and_Mail-Reply-To) for "Reply All":
```
if MAIL-FOLLOWUP-TO in received mail then use MAIL-FOLLOWUP-TO as TO
else if MAIL-REPLY-TO in received mail then use MAIL-REPLY-TO + TO + CC as TO
else if REPLY-TO in received mail then use REPLY-TO + TO + CC as TO # this
else use FROM + TO + CC as TO
```
This means, when schleuder is configured to set REPLY-TO to the original sender, the clients will set TO to `REPLY-TO (original sender) + TO (recipient) + CC`, which does NOT include the mailing list.
Thus I would suggest to add a MAIL-FOLLOWUP-TO header **when REPLY-TO is set to the original sender**. The MAIL-FOLLOWUP-TO header then includes:
- list
- original sender
- CC
If you don't see any problems, I would implement this and open a MR. Please let me know :)https://0xacab.org/schleuder/schleuder/-/issues/496gpg: insecure memory warnings for tests2022-09-13T14:50:27ZAndreas Schleifergpg: insecure memory warnings for testsHello,
while trying to package schleuder for Archlinux I get the following errors when running the tests during the packaging step:
```
Created database 'db/test.sqlite3'
Randomized with seed 63950
.......................................Hello,
while trying to package schleuder for Archlinux I get the following errors when running the tests during the packaging step:
```
Created database 'db/test.sqlite3'
Randomized with seed 63950
.....................................................................................................................................................................................................................................................................................................................................................................................................................................FFF.F.FF..............................................................................................................
Failures:
1) Schleuder::ListBuilder creates a listdir for the list
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:41:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
2) Schleuder::ListBuilder creates a new, valid list
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:9:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
3) Schleuder::ListBuilder subscribes the adminaddress and ignores the adminfingerprint if an adminkey was given
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:85:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
4) Schleuder::ListBuilder subscribes the adminaddress and respects the given adminfingerprint
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:72:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
5) Schleuder::ListBuilder subscribes the adminaddress and imports the adminkey
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:60:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
6) Schleuder::ListBuilder creates a list-key with all required UIDs
Failure/Error: raise Errors::KeyAdduidFailed.new(exc.to_s)
Schleuder::Errors::KeyAdduidFailed:
Adding a user-ID to the OpenPGP key failed with this message:
gpg: Warning: using insecure memory!
Kind regards,
Your Schleuder system.
# ./lib/schleuder/list_builder.rb:103:in `rescue in adduids'
# ./lib/schleuder/list_builder.rb:88:in `adduids'
# ./lib/schleuder/list_builder.rb:82:in `create_key'
# ./lib/schleuder/list_builder.rb:41:in `run'
# ./spec/schleuder/unit/list_builder_spec.rb:49:in `block (2 levels) in <top (required)>'
# ./spec/spec_helper.rb:48:in `block (3 levels) in <top (required)>'
# ./spec/spec_helper.rb:47:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# RuntimeError:
# gpg: Warning: using insecure memory!
# ./lib/schleuder/list_builder.rb:93:in `block in adduids'
Finished in 4 minutes 20.7 seconds (files took 1.94 seconds to load)
539 examples, 6 failures
Failed examples:
rspec ./spec/schleuder/unit/list_builder_spec.rb:37 # Schleuder::ListBuilder creates a listdir for the list
rspec ./spec/schleuder/unit/list_builder_spec.rb:5 # Schleuder::ListBuilder creates a new, valid list
rspec ./spec/schleuder/unit/list_builder_spec.rb:81 # Schleuder::ListBuilder subscribes the adminaddress and ignores the adminfingerprint if an adminkey was given
rspec ./spec/schleuder/unit/list_builder_spec.rb:69 # Schleuder::ListBuilder subscribes the adminaddress and respects the given adminfingerprint
rspec ./spec/schleuder/unit/list_builder_spec.rb:56 # Schleuder::ListBuilder subscribes the adminaddress and imports the adminkey
rspec ./spec/schleuder/unit/list_builder_spec.rb:45 # Schleuder::ListBuilder creates a list-key with all required UIDs
Randomized with seed 63950
```
During these tests I don't really care about such errors and therefor I tried to ignore them. My current code for running the tests looks like this:
```
export GNUPGHOME=.gnupg
mkdir -p "${GNUPGHOME}"
echo "no-secmem-warning" >> "${GNUPGHOME}/gpg.conf"
export CHECK_CODE_COVERAGE=false
export SCHLEUDER_CONFIG=spec/schleuder.yml
export SCHLEUDER_ENV=test
bundle exec rake db:init
bundle exec rspec
```
Any idea how I can ignore these errors in my tests?
I can't use setuid, as the build environment has no permissions to do that.
Best regards5.0.0pazpazhttps://0xacab.org/schleuder/schleuder/-/issues/495x-add-key fails for binary attachments2023-10-28T10:15:11Zgeorgx-add-key fails for binary attachmentsx-add-key fails for binary attachments, Schleuder tells 'no keys could be found'.x-add-key fails for binary attachments, Schleuder tells 'no keys could be found'.4.0.1georggeorghttps://0xacab.org/schleuder/schleuder/-/issues/494Delete subscription & key together2021-07-07T11:42:38ZngDelete subscription & key togetherHave an option to delete a subscription together with the key. Atm it is a two step process to delete a subscription and than its key. Which is a bit tediousHave an option to delete a subscription together with the key. Atm it is a two step process to delete a subscription and than its key. Which is a bit tedioushttps://0xacab.org/schleuder/schleuder/-/issues/493Bulk delete all unused key2021-07-07T11:42:36ZngBulk delete all unused keyit would be great if there was an option to delete all unused keys from a lists's keyring. So it can be cleaned up.it would be great if there was an option to delete all unused keys from a lists's keyring. So it can be cleaned up.https://0xacab.org/schleuder/schleuder/-/issues/492Running db:init on schleuder install might not be suitable for external DB ad...2021-11-07T20:01:07ZngRunning db:init on schleuder install might not be suitable for external DB adapters with less privileged usersIf you have your schleuder DB in a DBMS (e.g. postgresql) you likely have a user that is not privileged to create the database.
However, on `schleuder install` we blindly do `db:create` which fails.
Related code snippets:
* https://0x...If you have your schleuder DB in a DBMS (e.g. postgresql) you likely have a user that is not privileged to create the database.
However, on `schleuder install` we blindly do `db:create` which fails.
Related code snippets:
* https://0xacab.org/schleuder/schleuder/-/blob/18c1e07a5c414e3ac7d42a495b95603f1a5da837/lib/schleuder/cli.rb#L116
* https://0xacab.org/schleuder/schleuder/-/commit/2ee7f06015a82d5a88e98e8859e15efcb98a7a78
Not sure if we should point it out , be more clever or just document it. Or everybody (except me) runs out of sqlite.https://0xacab.org/schleuder/schleuder/-/issues/491schleuder install has no output on DB authentication failure2022-04-11T21:46:09Zngschleuder install has no output on DB authentication failureI had a wrong password in schleuder.yml and tried to run `schleuder install` but it had no output and just an exit code of 1.
We should be more verbose otherwise debugging becomes really hard.I had a wrong password in schleuder.yml and tried to run `schleuder install` but it had no output and just an exit code of 1.
We should be more verbose otherwise debugging becomes really hard.https://0xacab.org/schleuder/schleuder/-/issues/490recent schleuder releases (past 3.4.0) not available in debian stable apt rep...2021-06-08T20:40:51Zfleishrecent schleuder releases (past 3.4.0) not available in debian stable apt repositoryI had previously updated to Debian's latest stable release (Buster) to stop relying on the older package from stretch-backports as discussed in #436. However, I am not seeing recent updates flowing to the stable repository. I see 3.6.0 i...I had previously updated to Debian's latest stable release (Buster) to stop relying on the older package from stretch-backports as discussed in #436. However, I am not seeing recent updates flowing to the stable repository. I see 3.6.0 in testing, but first wanted to inquire if this is expected and whether or not there are other things to consider before adding this repository to obtain the updated package. The current installation instructions @ https://0xacab.org/schleuder/schleuder/blob/master/README.md#installing-schleuder only mentions installing Schleuder as a ruby gem and makes no mention of any Debian repositories. Thanks in advance for some updated guidance on this.https://0xacab.org/schleuder/schleuder/-/issues/489Feature Request: (Add option to) publish list-key to web key directory2021-05-25T22:30:55Zlu xFeature Request: (Add option to) publish list-key to web key directory**Problem:**
Since many mailclients are moving from SKS to verified keyservers and WKD, it has become rather cumbersome to publish a whole list key.
For example, when publishing a key to keys.openpgp.org, you would need to verify the ...**Problem:**
Since many mailclients are moving from SKS to verified keyservers and WKD, it has become rather cumbersome to publish a whole list key.
For example, when publishing a key to keys.openpgp.org, you would need to verify the identity for its sub-identites too (list-request or list-owner), and for an encrypted-only list you would need to fish the verification link out of the attachment of the bounce-notification
(I am aware that you can write to list-sendkey for the public key, but many schleuder users are either not aware or generally alienated by the idea of managing a subscription via mail commands)
**Solution**
It would be great if schleuder could publish it's list keys via web key directory.
`GnuPG >= 2.2.14` [includes a web key service](https://wiki.gnupg.org/WKS), so this might be possible without adding additional dependencies to schleuder.
I do not know ruby (yet) and my programming experience is almost none, but if you approve the idea I could a look at the codebase and see if I can do a contribution (..and maybe you already know a convenient way to do this and can point me to the direction :smile: )https://0xacab.org/schleuder/schleuder/-/issues/488deprecation warnings when running tests2021-02-18T09:20:10ZAndreas Schleiferdeprecation warnings when running testsWhile running the automated tests of schleuder, I saw these deprecation warnings:
```
DEPRECATION WARNING: Calling `<<` to an ActiveModel::Errors message array in order to add an error is deprecated. Please call `ActiveModel::Errors#add`...While running the automated tests of schleuder, I saw these deprecation warnings:
```
DEPRECATION WARNING: Calling `<<` to an ActiveModel::Errors message array in order to add an error is deprecated. Please call `ActiveModel::Errors#add` instead.
```
The attached file fixes these errors:
[deprecations.patch](/uploads/931279c6027e54676bec685e10e869e1/deprecations.patch)
Best regardshttps://0xacab.org/schleuder/schleuder/-/issues/487cannot load such file -- schleuder/cli (LoadError)2021-02-16T08:39:04ZAndreas Schleifercannot load such file -- schleuder/cli (LoadError)Hi,
while trying to pacakge schleuder for Archlinux, I ran into a problem.
I created the ruby gem via `gem build schleuder.gemspec` and then used `gem install` to install the resulting gem.
When I then try to run schleuder I get this ...Hi,
while trying to pacakge schleuder for Archlinux, I ran into a problem.
I created the ruby gem via `gem build schleuder.gemspec` and then used `gem install` to install the resulting gem.
When I then try to run schleuder I get this error:
```
Traceback (most recent call last):
4: from /usr/bin/schleuder:23:in `<main>'
3: from /usr/bin/schleuder:23:in `load'
2: from /usr/lib/ruby/gems/2.7.0/gems/schleuder-3.6.0/bin/schleuder:12:in `<top (required)>'
1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- schleuder/cli (LoadError)
```
I'm a bit lost as to what this error wants to tell me. Do I need schleuder/schleuder-cli> ?
Best regardshttps://0xacab.org/schleuder/schleuder/-/issues/486CI: Add job to validate DB schema version2021-02-20T11:44:25ZgeorgCI: Add job to validate DB schema versionRecently, the following [was commited](https://0xacab.org/schleuder/schleuder/-/commit/c4a760a64a2498f6d119e0082dc6ad28901bcedb#2cda0c6171fa7d04989507a1dd112e34c40df46d_15_14):
```
- ActiveRecord::Schema.define(version: 20190906194820) ...Recently, the following [was commited](https://0xacab.org/schleuder/schleuder/-/commit/c4a760a64a2498f6d119e0082dc6ad28901bcedb#2cda0c6171fa7d04989507a1dd112e34c40df46d_15_14):
```
- ActiveRecord::Schema.define(version: 20190906194820) do
+ ActiveRecord::Schema.define(version: 20200118170110) do
```
Note the newly added version, ideally, this one should have been named `2020118170110`, that is, one `0` less in between the year and the month.
In this case, this doesn't matter much, but it might be different if this would have been committed at the beginning of a year.
What do you think?4.0.0georggeorghttps://0xacab.org/schleuder/schleuder/-/issues/485Improve helpfulness of error messages in response to keywords2021-02-03T11:37:07ZpazImprove helpfulness of error messages in response to keywordsE.g. If a resend fails due to a string not being a valid email-address.E.g. If a resend fails due to a string not being a valid email-address.Next Big Thinghttps://0xacab.org/schleuder/schleuder/-/issues/484invalid list emails allowed2021-02-03T12:26:18Znginvalid list emails allowedSomebody was able to create a list with `foo bar@lists.example.com` - this should not be possible.
Deleting also requires lots of lowlevel hacking, since the schleuder-api returns `783: unexpected token at 'Bad Request'`Somebody was able to create a list with `foo bar@lists.example.com` - this should not be possible.
Deleting also requires lots of lowlevel hacking, since the schleuder-api returns `783: unexpected token at 'Bad Request'`3.6.0https://0xacab.org/schleuder/schleuder/-/issues/483Properly validate email addresses2021-02-03T12:26:26ZngProperly validate email addressesOur regexp is rather ehm basic:
https://0xacab.org/schleuder/schleuder/-/blob/26e8dc880fde033fa9a37e0cacc05fb0e56baa3c/lib/schleuder/conf.rb#L7
This can lead to issues, when for example subscriptions with invalid email addresses are re...Our regexp is rather ehm basic:
https://0xacab.org/schleuder/schleuder/-/blob/26e8dc880fde033fa9a37e0cacc05fb0e56baa3c/lib/schleuder/conf.rb#L7
This can lead to issues, when for example subscriptions with invalid email addresses are registered, that are later then re-formatted by the mail-gem.
An example of that has been reported as the basis for #482 and went the following way:
* Subscription with email ' my@email.com'
* Key was assigned to subscription
When delivery happends, the following is happening:
gpg_options for mail-gpg gets the following hash (https://0xacab.org/schleuder/schleuder/-/blob/26e8dc880fde033fa9a37e0cacc05fb0e56baa3c/lib/schleuder/subscription.rb#L61):
```ruby
{'encrypt' => true, 'keys' => { ' my@email.com' => '0x.....' } }
```
receivers is set to `mail.to` https://github.com/jkraemer/mail-gpg/blob/481d4096c67bac6a4248604dba0d43753f5b2404/lib/mail/gpg.rb#L34 (+ Line 46) which is: 'my@email.com':
```ruby
Mail.new(to: ' my@email.com').to
=> ["my@email.com"]
```
This is then used to look up the keys for the emails @ https://github.com/jkraemer/mail-gpg/blob/481d4096c67bac6a4248604dba0d43753f5b2404/lib/mail/gpg/gpgme_helper.rb#L14
email_or_shas in this function: https://github.com/jkraemer/mail-gpg/blob/481d4096c67bac6a4248604dba0d43753f5b2404/lib/mail/gpg/gpgme_helper.rb#L121-L154
are the previously recipients, parsed and formatted by Mail. But we then try to find a keyid in the key_data (that is the previously generated keys hash): https://github.com/jkraemer/mail-gpg/blob/481d4096c67bac6a4248604dba0d43753f5b2404/lib/mail/gpg/gpgme_helper.rb#L127-L128
Which obviously fails since, the key for the fingerprint is ' my@email.com', but the recipient is 'my@email.com'
1. We should improve checking the validity of an emailaddress
2. We might likely want to format (besides downcasing) all the emails for subscriptions how mail will treat them. Like this, we will ensure, they will also be found when used by mail-gpg. E.g. `Mail::Address.new(' my@email').address`3.6.0https://0xacab.org/schleuder/schleuder/-/issues/482Please be more informative when you can't encrypt to a list-admin2021-01-18T23:47:57ZcasperPlease be more informative when you can't encrypt to a list-adminSchleuder 3.4.0-2+deb10u3 did sent this uninformative message (Subject: "Error"), when it couldn't find a matching key to one of the list-administrators.
```
No keys to encrypt to!
/usr/lib/ruby/vendor_ruby/mail/gpg/gpgme_helper.rb:17:...Schleuder 3.4.0-2+deb10u3 did sent this uninformative message (Subject: "Error"), when it couldn't find a matching key to one of the list-administrators.
```
No keys to encrypt to!
/usr/lib/ruby/vendor_ruby/mail/gpg/gpgme_helper.rb:17:in `encrypt'
/usr/lib/ruby/vendor_ruby/mail/gpg/encrypted_part.rb:23:in `initialize'
/usr/lib/ruby/vendor_ruby/schleuder/mail/encrypted_part.rb:10:in `initialize'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:43:in `new'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:43:in `block in encrypt'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:113:in `instance_eval'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:113:in `block in construct_mail'
/usr/lib/ruby/vendor_ruby/mail/message.rb:153:in `instance_eval'
/usr/lib/ruby/vendor_ruby/mail/message.rb:153:in `initialize'
/usr/lib/ruby/vendor_ruby/mail/mail.rb:51:in `new'
/usr/lib/ruby/vendor_ruby/mail/mail.rb:51:in `new'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:106:in `construct_mail'
/usr/lib/ruby/vendor_ruby/mail/gpg.rb:29:in `encrypt'
/usr/lib/ruby/vendor_ruby/schleuder/mail/gpg.rb:7:in `encrypt'
/usr/lib/ruby/vendor_ruby/mail/gpg/delivery_handler.rb:11:in `deliver_mail'
/usr/lib/ruby/vendor_ruby/mail/message.rb:260:in `deliver'
/usr/lib/ruby/vendor_ruby/schleuder/logger_notifications.rb:48:in `block in notify_admin'
/usr/lib/ruby/vendor_ruby/schleuder/logger_notifications.rb:29:in `each'
/usr/lib/ruby/vendor_ruby/schleuder/logger_notifications.rb:29:in `notify_admin'
/usr/lib/ruby/vendor_ruby/schleuder/logger_notifications.rb:13:in `error'
/usr/lib/ruby/vendor_ruby/schleuder/list.rb:356:in `rescue in block in send_to_subscriptions'
/usr/lib/ruby/vendor_ruby/schleuder/list.rb:347:in `block in send_to_subscriptions'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/relation/delegation.rb:71:in `each'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.2.1/lib/active_record/relation/delegation.rb:71:in `each'
/usr/lib/ruby/vendor_ruby/schleuder/list.rb:346:in `send_to_subscriptions'
/usr/lib/ruby/vendor_ruby/schleuder/runner.rb:77:in `run'
/usr/lib/ruby/vendor_ruby/schleuder/cli.rb:36:in `work'
/usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
/usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command'
/usr/lib/ruby/vendor_ruby/thor.rb:369:in `dispatch'
/usr/lib/ruby/vendor_ruby/thor/base.rb:444:in `start'
/usr/bin/schleuder:13:in `<main>'
```
To debug, I made everyone a simple user but me. Once the problematic account was a simple user, schleuder would send:
```
The following error occurred while sending a message to user@example.org: No keys to encrypt to!
```https://0xacab.org/schleuder/schleuder/-/issues/481Make the first user list-admin per default2020-08-03T16:52:12ZcasperMake the first user list-admin per defaultSchleuder warns me, that I need at least on list-admin to make the list functional. It would be great, if you could tick the "admin"-box per default for the first user. I just forget too many times.Schleuder warns me, that I need at least on list-admin to make the list functional. It would be great, if you could tick the "admin"-box per default for the first user. I just forget too many times.https://0xacab.org/schleuder/schleuder/-/issues/480undefined method `internal_footer'2020-07-24T10:01:41ZHiroundefined method `internal_footer'I have noticed all the emails are failing with the following error:
```
undefined method `internal_footer' for #<Schleuder::List:0x0000561082264858>
/usr/share/rubygems-integration/all/gems/activemodel-5.2.2.1/lib/active_model/attribute_...I have noticed all the emails are failing with the following error:
```
undefined method `internal_footer' for #<Schleuder::List:0x0000561082264858>
/usr/share/rubygems-integration/all/gems/activemodel-5.2.2.1/lib/active_model/attribute_methods.rb:430:in `method_missing'
/usr/lib/ruby/vendor_ruby/schleuder/mail/message.rb:454:in `add_footer!'
/usr/lib/ruby/vendor_ruby/schleuder/mail/message.rb:127:in `add_internal_footer!'
/usr/lib/ruby/vendor_ruby/schleuder/list.rb:345:in `send_to_subscriptions'
/usr/lib/ruby/vendor_ruby/schleuder/runner.rb:77:in `run'
/usr/lib/ruby/vendor_ruby/schleuder/cli.rb:36:in `work'
/usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
/usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command'
/usr/lib/ruby/vendor_ruby/thor.rb:369:in `dispatch'
/usr/lib/ruby/vendor_ruby/thor/base.rb:444:in `start'
/usr/bin/schleuder:13:in `<main>'
```
Here are some information about our ruby and schleuder version.
```
$ ruby -v
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]
$ schleuder -v
3.4.0
```
We have recently switched from the schleuder gem to the Debian package.https://0xacab.org/schleuder/schleuder/-/issues/479Don't allow to upload expired keys (or inform the user about usability issues...2023-11-14T08:55:40ZcasperDon't allow to upload expired keys (or inform the user about usability issues [expired, revoked])You shouldn't be allowed to upload an unusable key. Or at least, there should be an informative warning flash message as proposed in schleuder-web#12.You shouldn't be allowed to upload an unusable key. Or at least, there should be an informative warning flash message as proposed in schleuder-web#12.5.0.0pazpazhttps://0xacab.org/schleuder/schleuder/-/issues/478CI: specs fail randomly2022-04-12T18:51:16ZgeorgCI: specs fail randomlySee for example these jobs:
- https://0xacab.org/schleuder/schleuder/-/jobs/152036
- https://0xacab.org/schleuder/schleuder/-/jobs/151050See for example these jobs:
- https://0xacab.org/schleuder/schleuder/-/jobs/152036
- https://0xacab.org/schleuder/schleuder/-/jobs/1510504.0.3pazpaz