Mail-app failed the integrity check after updating

ℹ️ Support
, ,
1

Hi All,

After updating to [Nextcloud Hub 9] (30.0.2) i get the follow warming:

There are some errors regarding your setup.

**** Some files have not passed the integrity check. List of invalid files… Rescan… For more details see the documentation :arrow_upper_right:.***

Mail app Version 4.0.5

Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results
=======
- mail
	- EXCEPTION
		- OC\IntegrityCheck\Exceptions\InvalidSignatureException
		- Certificate is not valid.

Raw output
==========
Array
(
    [mail] => Array
        (
            [EXCEPTION] => Array
                (
                    [class] => OC\IntegrityCheck\Exceptions\InvalidSignatureException
                    [message] => Certificate is not valid.
                )

        )

)

any scan do not fix the issue.
Does anyone know the solution to fix this problem?
Thank you for your reply.

4 Likes
2

I have the exact same issue.

3

I have the exact same issue.

4

I just found this post after today updating nextcloud to the 30.0.2 version, seems like a bug, cause I did not change anything in configuration. It looks like “mail” app was updated 2 days ago.

5

Hi people, a Groupware developer here.

I did some investigation and it seems that there was a problem during the signing phase of the release. We recently switched to a new, automated process so please bear with us.

I manually checked the released archive. It is valid and has not been tampered with. It’s just an incomplete signature.

We will fix our release workflow and will publish a fixed release as soon as possible.

2 Likes
6

I just saw that the latest release on 3.7.x is also affected. The same applies here as well.

7

Mail 4.0.6 and 3.7.14 are out with fixed signatures.

1 Like
8

for the records:

9

Mail 4.0.7 has invalid signature. I don’t know if 4.0.6 fixed my problem.
Weird!

Rescan solved!