Hello,
we have made the first catch-up-the-release step from stable working
Ciphermail 4.6.2 to the latest 4.x version 4.11. After that all looks
well but we get the following warning all the time:
WARN XFORWARD error code: 550
(org.apache.james.transport.mailets.RemoteDelivery) [Remote delivery
thread (0)]
The only thing we have found in the release notes which might be
related is from version 4.9.1:
"X-Forward-For header is now by default removed unless the IP address
comes from a trusted proxy (see /etc/httpd/conf.d/x-forward-for.xml)
[PRO/ENT]."
Any idea what Ciphermail actually is complaining about?
Thanks
Andreas
Hello,
I tried to import the Mozilla root ca bundle according to this guide: https://www.ciphermail.com/root-certificates.html
but CipherMail shows me an error: There was an error uploading the certificate file. Cause: Processing of multipart/form-data request failed. Stream ended unexpectedly
How can I import the usual root ca's?
I found also a thread "Is there a way to (automatically) import root CAs from the command-line", is there any working solution out there?
best regards
Jan
Hi,
does anyone know, if ciphermail 5.1.3 supports ECDH Prime256 for S/MIME encryption??
RSA is working smooth but now we have one cert with ECDH and it shows cert key length -1.
I found not even one source which states out the supported algorythm of ciphermail.
Thanks in advance
Sebastian
Hi all,
I was able to send an encrypted PDF to an external recipient.
In the settings i activated OTP, Reply and auto invite.
Login, and code generation worked.
The document could be decrypted/opened and the text and email header is shown as expected.
But if I attach files (so far tried with pdf, txt, zip) the attachment can not be received from the encrypted PDF.
It seems the attachment function has a bug.
In the attachment line inside the PDF it shows the following:
Attachments: attachment.bin; FilenameOfAttachment.txt; attachment.bin;
The file is not linked to anything, it is text only.
When i hit the reply button in the PDF, the Portal page opens up and i can login.
The Webform loads fine, but there is no content shown in the iframe used for attachments.
The pdf-reply-attachments-frame iframe only has an empty #document <html><head></head><body></body></html> element inside.
I am using 5.1.4.0g64f23292
I also tried 5.1.3.0g21575dc87
Centos Stream, Debian 10, Ubuntu 20.04
The issue remains the same.
I use systemd enabled docker images.
The installation worked seamless for all above mentioned systems.
I hope anyone can help.
Best regards,
Sascha
Good morning,
how can tell the backup scipt to connect to our NAS using smb version 2.0? I had a look at the usual places where cronjobs are saved, but did not find a script to add this parameter.
We are using CipherMail version 5.0.5
Kind regards,
Stefan
Hi,
i have a s/mime cert with key usage keyEncipherment and digitalSignature.
I cannot sign with it and i do not know why.
When i open the user preferences it is only shown in encryption certificates but not in signing certificates.
Has anyone a idea what might be the problem here?
Thanks for your help in advance.
Here are a few screenshots:
Regards
Christian Schmid
Hello,
I got a request to make incoming public PGP keys trusted.
The idea is to make a register mail address where a person can send his
pub key and we remove it from the mail and add it to the gateway. That's
fine and working.
Now the tricky part:
We want the user to verify the key via a second way with the key ID. The
second way wrote the pub key ID in a database and from their the verify
process should start and check if the key with that ID exists and if so it
should be trusted.
Now two questions:
1. How can we set the key trusted via cli or something like that?
2. Is it possible to add a header or subject extension after a lookup in
the database to get a value from their which should be added to subject or
as header?
Regards
Robert Wiegand
Hello,
we just switched from the Debian version to the appliance version. So far everything seems to work, but we have one issue.
On our old server only our office365 host was able to connect and deliver mail. I believe the part in config with
"exchange_online_checks = check_client_access cidr:/etc/postfix/cidr-o365-ip-range" should define the hosts which are allowed to connect to ciphermail.
/etc/postfix/cidr-o365-ip-range (more IPs from O365 inside, this is just one for example) being:
104.47.0.0/17 OK
I do realize that this leads to the fact that everybody from an O365 ip address can send to the Ciphermail appliance and it will be forwarded but this is something we are willing to accept.
Unfortunately currently all IP addresses can connect and deliver mail for our domain which leads to intensive spam.
Am I doing something wrong? Would really appreciate some help.
Best Regards,
Vincent