Although, if it does not scare you, and you find this interested in how I did it anyway, you can read more about it in The lesson of verifying Git commits. 😉
-----BEGIN PGP MESSAGE-----
hQIMA+vud8VzRJSmAQ//TEZwWw77MXJMXLds5zTEznJlyuRIIN/DR5xi+Fc/CX4u
FnGdS8lMlczDeQj5u1607HhmB/2MqnzZUlYATA+OLJswX4B2nqdWVo+u4Z+ijjCW
...
...
...
+FC1gpSOnEH9TMGtvW/ogKcAYkbFj4FMhfT+1cfcyEQ=
=c4x/
-----END PGP MESSAGE-----encrypted_message.txt (as it will be a bit easier to decrypt it in a later step). Additionally, it does not matter which extension you will use to encode your message.→ gpg --search-keys matbit@secmail.pro
gpg: data source: http://83.227.87.55:11371
(1) Hu2020 (Hu <matbit@secmail.pro>) <matbit@secmail.pro>
3072 bit RSA key CBFD27BAA73638F2, created: 2020-06-14
Keys 1-1 of 1 for "matbit@secmail.pro". Enter number(s), N)ext, or Q)uit > sgpg --receive-keys CBFD27BAA73638F2→ gpg --decrypt ~/encrypted_message.txt.gpg
gpg: encrypted with 4096-bit RSA key, ID EBEE77C5734494A6, created 2019-03-17
"Maciej Sypien <maciejsypien@gmail.com>"
Dear Maciej,
...After I search something about secmail in general, it become more obvious to me that this person just paid for anonymity and an easy pre-configured platform for sending encrypted emails. At this moment I knew that there was something not right - disappointing.