Roundup Tracker - Issues

Message8418

Author rouilj
Recipients ThomasAH, rouilj
Date 2025-12-07.22:29:53
Message-id <1765146593.87.0.83762454172.issue2551152@roundup-tracker.org>
In-reply-to
Thomas:

You said:

> And if a key (or encryption subkey) expires, you can't add new messages to
> issues where the corresponding user is in the nosy list

Does this block anybody from adding a message to the issue (via email or http)?
Or is only the user with the expired key blocked?

Mi initial interpretation made me think all message addition fails when 
Roundup is unable to create an encrypted nosy email to the user with the expired key.
But I don't see how that would happen as email is sent in a reactor after the message
has been added. I also would have expected the user to be able to add a message via HTTP
since I see the PGP machinery invoked only via the email gateway.

I would like to add this case to the admin_guide. Also I don't have access to the
script https://hg.intevation.de/adminton/file/default/shebang/gpg-keyring-check-expire.
hg.intevation.de is taking too long to respond.

Thanks.

-- rouilj
History
Date User Action Args
2025-12-07 22:29:53rouiljsetmessageid: <1765146593.87.0.83762454172.issue2551152@roundup-tracker.org>
2025-12-07 22:29:53rouiljsetrecipients: + rouilj, ThomasAH
2025-12-07 22:29:53rouiljlinkissue2551152 messages
2025-12-07 22:29:53rouiljcreate