Skip to content

Fix: os2forms_forloeb: Maestro notification attempts sending digital post that will never be delivered #195

Closed

Description

@jekuaitk

Problem

Digital post, SF1601, requires that recipientID is digits and is either 8 or 10 of them, depending on whether it is a CVR- or CPR-number. As of right now, this is described on page 19 of "SF1601 Postkomponent - KombiPostAfsend - Feltbeskrivelse" found in their compressed documentation package.

Consequently, dashes are not allowed in CPR-numbers.

Handling in digital post handler

This is unintentionally handled during the processing of jobs from the normal Digital Post handler by removing all non-digits which had the intention of helping detecting whether we were dealing with CVR or CPR.

Missing handling in Maestro notification handler

It is not (intentionally or unintentionally) handled during the processing of Maestro notifications jobs. This means that instances where maestro notifications have been sent to 'dashed' CPR-numbers will have never been received despite the submission log claiming it as being sent.

Interestingly, according to Kombit, these would have been sent as 'Fjern print' instead.

Note

As long as we do not use Beskedfordeleren, we have no way of knowing whether digital post has been delivered or not. We can however limit the scenarios in which we know digital post will never be received by removing non-digits as in the Digital Post handler case.

Activity

  1. added 2 commits that reference this issue on Aug 29, 2025
  2. jekuaitk commented on Sep 5, 2025

    @jekuaitk
    ContributorAuthor

    Hi @ds-bellcom

    This is one of the issues we would like a review on!

  3. changed the title [-]os2forms_forloeb: Maestro notification attempts sending digital post that will never be delivered[/-] [+]Fix: os2forms_forloeb: Maestro notification attempts sending digital post that will never be delivered[/+] on Sep 10, 2025
  4. ds-bellcom commented on Sep 11, 2025

    @ds-bellcom
    Contributor

    Estimate: 1h (the review is done)!

  5. added theissue type on Sep 11, 2025
  6. self-assigned this
    on Sep 12, 2025
  7. ds-bellcom commented on Oct 2, 2025

    @ds-bellcom
    Contributor

    @jekuaitk Review is done (3 weeks ago). Will you merge it and close this issue when done?

    CC: @Anna-itk @ChatBotBerg

  8. added a commit that references this issue on Oct 20, 2025
  9. ds-bellcom commented on Nov 12, 2025

    @ds-bellcom
    Contributor

    @Anna-itk @lilosti @gBarlach Har I mulighed for at oprettet en formular med tilhørende flow på test.os2forms.dk, så ovenstående kan testes? Jeg ved desværre ikke hvordan I sætter dette op i Århus, så jeg har svært ved at guide Koordinationsgruppen til at teste dette!

    CC: @ChatBotBerg

  10. ds-bellcom commented on Nov 14, 2025

    @ds-bellcom
    Contributor

    @jekuaitk Troels har lavet en formular til test.

  11. ds-bellcom commented on Nov 17, 2025

    @ds-bellcom
    Contributor

    @jekuaitk Skal denne stadig være åben eller kan den lukkes?

  12. jekuaitk commented on Nov 17, 2025

    @jekuaitk
    ContributorAuthor

    @jekuaitk Skal denne stadig være åben eller kan den lukkes?

    Jeg formoder Troels har fået det til at spille ift. test, så jeg lukker igen :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions