You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... 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
The text was updated successfully, but these errors were encountered:
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.
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
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:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: