Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot upload S/MIME in SOGo IMAP settings #6127

Open
5 tasks done
SimplyCorbett opened this issue Oct 27, 2024 · 4 comments
Open
5 tasks done

Cannot upload S/MIME in SOGo IMAP settings #6127

SimplyCorbett opened this issue Oct 27, 2024 · 4 comments
Labels
bug investigating Still under investigation undecided

Comments

@SimplyCorbett
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
  • ... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
  • ... I have understood that answers are voluntary and community-driven, and not commercial support.
  • ... I have verified that my issue has not been already answered in the past. I also checked previous issues.

Description

SOGo will not upload or accept my passphrase on the S/MIME I am trying to upload.

Have tried many different S/MIME combinations (with and without passphrase) with no success.

Logs:

77] FATAL: could not parse PKCS12 certificate with provided password: unsupported

Steps to reproduce:

Try uploading and saving a pkcs12 file for s/mime under sogo imap settings.

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

Debian 12

Server/VM specifications:

3700x, 64GB RAM, 2TB NVME

Is Apparmor, SELinux or similar active?

not sure, dont think so.

Virtualization technology:

none

Docker version:

27.3.1

docker-compose version or docker compose version:

2.29.7

mailcow version:

2028-08a

Reverse proxy:

None

Logs of git diff:

None

Logs of iptables -L -vn:

Too large to post (2000+ dropped networks)

Logs of ip6tables -L -vn:

IPv6 is disabled on the server

Logs of iptables -L -vn -t nat:

Not relevant to the issue

Logs of ip6tables -L -vn -t nat:

not relevant to the issue

DNS check:

Correct ips listed
@DerLinkman
Copy link
Member

DerLinkman commented Oct 29, 2024

Sounds like a upstream issue to me? Maybe open up a ticket at sogo for this.

@SimplyCorbett
Copy link
Author

SimplyCorbett commented Oct 30, 2024

I will try to contact their mailing list and go from there, thanks!

Are you sure it’s not a missing dependency in the docker build though? I know the error doesn’t point to that but I can’t imagine they would release sogo with the option if it doesn’t work. Seems to be an issue with decrypting the passphrase, I think.

@DerLinkman
Copy link
Member

Could you try installing libsofthsm2 inside the docker container?

Try:

docker compose exec sogo-mailcow bash
apt update
apt install libsofthsm2 -y

It could be a missing dependency.

@DerLinkman DerLinkman added undecided investigating Still under investigation and removed upstream labels Oct 30, 2024
@SimplyCorbett
Copy link
Author

Well... it changed the error.

79] FATAL: could not parse PKCS12 certificate with provided password: mac verify failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug investigating Still under investigation undecided
Projects
None yet
Development

No branches or pull requests

2 participants