Am 14.03.2023 schrieb Tristan Miller <tmiller@big-8.org>:

> I find it a bit odd as well. The Board was approached by someone who
> wanted to volunteer as a moderator, and I thought that
> comp.os.linux.announce would be a good candidate since it was fairly
> active before the former moderator became inactive. (We had
> previously successfully revived comp.ai, which was in a similar
> situation, and is now getting several posts per month.) I can ping
> the moderator to double-check that his moderation software is still
> working. It could be that, unlike with comp.ai, everyone who was
> previously posting to the group has left and doesn't know or care
> about its revival.

I now posted to comp.os.linux.announce and got an empty email from
devnull@dynamicmalloc.com.

Greetings.

On 28/04/2023 12.34, Marco Moock wrote:
>> I find it a bit odd as well. The Board was approached by someone who
>> wanted to volunteer as a moderator, and I thought that
>> comp.os.linux.announce would be a good candidate since it was fairly
>> active before the former moderator became inactive. (We had
>> previously successfully revived comp.ai, which was in a similar
>> situation, and is now getting several posts per month.) I can ping
>> the moderator to double-check that his moderation software is still
>> working. It could be that, unlike with comp.ai, everyone who was
>> previously posting to the group has left and doesn't know or care
>> about its revival.
>
> I now posted to comp.os.linux.announce and got an empty email from
> devnull@dynamicmalloc.com.

Thanks for letting me know. I've alerted the moderator to your article
and asked him to investigate.

Regards,
Tristan

--
Usenet Big-8 Management Board
https://www.big-8.org/
board@big-8.org

Greetings.

On 2023-04-28 15:59, Tristan Miller wrote:
> On 28/04/2023 12.34, Marco Moock wrote:
>> I now posted to comp.os.linux.announce and got an empty email from
>> devnull@dynamicmalloc.com.
>
> Thanks for letting me know.  I've alerted the moderator to your article
> and asked him to investigate.

We've traced the problem to a bug in a (possibly little-used)
configuration option in STUMP involving the processing of PGP-signed
messages. We provided the moderator with a patch, and he reports that
the submission system should now be working.

Regards,
Tristan

--
Usenet Big-8 Management Board
https://www.big-8.org/
board@big-8.org

Am 02.06.2023 um 16:26:49 Uhr schrieb Tristan Miller:

> We've traced the problem to a bug in a (possibly little-used)
> configuration option in STUMP involving the processing of PGP-signed
> messages. We provided the moderator with a patch, and he reports
> that the submission system should now be working.

Can he now publish my article?

Dear Marco,

On 2023-06-03 09:19, Marco Moock wrote:
> Am 02.06.2023 um 16:26:49 Uhr schrieb Tristan Miller:
>
>> We've traced the problem to a bug in a (possibly little-used)
>> configuration option in STUMP involving the processing of PGP-signed
>> messages. We provided the moderator with a patch, and he reports
>> that the submission system should now be working.
>
> Can he now publish my article?

I think you'll need to resubmit it. His upstream news server is
rejecting the article because it's too old. If you do so and still
encounter any problems, let me and/or the moderator know.

Regards,
Tristan

--
Usenet Big-8 Management Board
https://www.big-8.org/
board@big-8.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In <u5n51c$nhuj$1@dont-email.me> Tristan Miller <tmiller@big-8.org> writes:

>Dear Marco,

>On 2023-06-03 09:19, Marco Moock wrote:
>> Am 02.06.2023 um 16:26:49 Uhr schrieb Tristan Miller:
>>
>>> We've traced the problem to a bug in a (possibly little-used)
>>> configuration option in STUMP involving the processing of PGP-signed
>>> messages. We provided the moderator with a patch, and he reports
>>> that the submission system should now be working.
>>
>> Can he now publish my article?

>I think you'll need to resubmit it. His upstream news server is
>rejecting the article because it's too old. If you do so and still
>encounter any problems, let me and/or the moderator know.

>Regards,
>Tristan

I just submitted the following ticket in the GNU Savannah tracking
system for the STUMP project:

Add troubleshooting steps to documentation to repair/requeue article submissions
https://savannah.gnu.org/bugs/index.php?64290

- --
Paul W. Schleck
pschleck@panix.com

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAmSDvMEACgkQ6Pj0az779o5p9ACgke0mZBWlUBc3BwvtmQuqM9vF
YZ4AoLM/Y+/19eukWTaUFGBk1kFgiHsW
=yBZi
-----END PGP SIGNATURE-----

In article <u60ejl$6tq$1@reader1.panix.com>, pschleck@panix.com says...

> I just submitted the following ticket in the GNU Savannah tracking
> system for the STUMP project:
>
> Add troubleshooting steps to documentation to repair/requeue article
> submissions https://savannah.gnu.org/bugs/index.php?64290

Thanks, Paul, this is a good idea. STUMP does have a script to resubmit
articles that have been rejected by the NNTP server at injection time,
but as far as I can see it was never documented anywhere.

I'm overhauling the STUMP docs at the moment anyway, so I might as well
also add some mention of how to do this.

Regards, Rayner