bugSTUMP - Bugs: bug #64290, Add troubleshooting steps to...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #64290: Add troubleshooting steps to documentation to repair/requeue article submissions

Submitter:  Paul Schleck <pschleck>
Submitted:  Fri 09 Jun 2023 11:53:05 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  rayner
Open/Closed:  Closed Planned Release:  2.6

Fri 23 Jun 2023 09:39:38 PM UTC, comment #1: 

STUMP will save failed submissions in its tmp/ directory. There is a submitFailed script that an administrator can use to attempt to resubmit them, once whatever problem caused the failure has been fixed.

I have created a FAQ (faq.md) that documents this, as it was not previously explained anywhere in the documentation. The FAQ should also be expanded with any other useful tips and solutions to common problems.

Rayner Lucas <rayner>
Group administrator
Fri 09 Jun 2023 11:53:05 PM UTC, original submission:  

STUMP documentation should be enhanced to add troubleshooting for repairing/requeueing article submissions by the moderation team on the server side, based on knowledge of how STUMP internally processes and posts submissions, along with the types of posting failures to news servers typically encountered.  This appears to currently be insider knowledge that not every moderation team knows, and should be shared widely among teams that use STUMP.

Speaking from experience, it's usually better to repair an article on the moderation end than ask the submitter to resubmit, particularly if the rejection is related to technical problems on the news server side, a moderator mistake, or is a previously rejected article approved on appeal.

Submitters usually will not resubmit an article again, and even if they do, there's a chance that the article will fail to post again.  While well-meaning, advising a submitter to resubmit comes off as, "Wrong! Try it again." and more than one round of this will discourage this and likely future submissions.

STUMP has at least two ways to do this, including:

- Manually advancing Date or de-duplicating Message-ID headers in the failed article saved in STUMP's failure directory and resending it directly to inews (PGPMoose signing is only impacted if the body of the article is modified).

- Just "bouncing" the original submission e-mail (after deleting loop-detection headers like Delivered-to") back to the moderation submission address, and thus the entire STUMP processing chain, via an e-mail client such as elm, pine, or even the mail client within the Emacs editor, preserving the original headers, including From.  This may be necessary if there are technical problems in the body that can't be fixed without modifying the content, requiring the regeneration of a PGPMoose signature.

STUMP should, of course, be configured to save incoming articles to an archive folder, to enable these repair/resubmission steps.  This is not done within STUMP by default.

These can be attempted multiple times by the moderator on the original submission until posting succeeds.

Paul Schleck <pschleck>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rayner (Updated the item)
  • -email is unavailable- added by pschleck (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-06-23 rayner StatusNone Fixed
        Open/ClosedOpen Closed
    2023-06-16 rayner Assigned toNone rayner
        Planned ReleaseNone 2.6

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code