Hi, See my comments inline:
>> ciphermail-appliance-centos-community-1.2.0-0.noarch This is an rpm. I guess you mean version ciphermail-community-virtual-appliance-4.3.0-1? > Now, the customer asked me to go back an not force encryption, but > make it an option using the Subject Line trigger. I changed the > settings for the domain in question backup to Encryp Mode = ‚Allow‘ > etc. > > But as it seems, the appliance doesn’t care and continues to encrypt > mails wether a trigger sentence is used or not. Encrypt mode "Allow" means, "Encrypt if possible". If you want encryption to be off by default unless encryption is forced (for example by some trigger) you should set Encrypt Mode to "No Encryption". The documentation for the gateway has recently been updated. https://www.ciphermail.com/documentation/adminguide/ It now also contains a full state diagram. Although is large and might look scary at first, it gives a good overview of all the decision steps taken by the gateway. Start at the beginning an answer every question along the way. https://www.ciphermail.com/documentation/diagrams/ciphermail-gateway-state-diagram.html Kind regards, Martijn Brinkers On 05-07-19 14:56, dirk bonengel | bios-tec via Users wrote: > Hi there, > > > > I’m a new user of Ciphermail (the VA variant, running > ciphermail-appliance-centos-community-1.2.0-0.noarch), installed it > recently with a customer’s network, work’s fine so far, awesome piece > of software. > > Today however I stumbled on something that might be a bug (or I’m > simply doing things wrong) > > > > This is what I did: > > * Set up Cipermail, creating a CA etc.pp. and set the Global > Preferences to use a trigger to encrypt mails with S/MIME, i.e. > Encrypt Mode = ‚Allow‘, S/MIME enabled, Set up a trigger regular > expression, enabled that one and check ‚Remove match‘ * Then I added > an external domain, set the Encryption Mode to ‚mandatory‘. For > testing purposesm this external domain happened to be that of our > company * This worked fine, each mail I sent me an my colleagues were > signed and encrypted. * Following that, I added another, productive > domain (example.com) as I was told > > Now, the customer asked me to go back an not force encryption, but > make it an option using the Subject Line trigger. I changed the > settings for the domain in question backup to Encryp Mode = ‚Allow‘ > etc. > > But as it seems, the appliance doesn’t care and continues to encrypt > mails, wether a trigger sentence is used or not. > > > > I’m clearly lost. What am I doing wrong? > > > > > > > > Mit freundlichen Grüßen, > > > > > > > > > > > Dirk Bonengel > > > > > > > <mailto:[email protected]> [email protected] > > > > > > > <tel:+4989416127717> +49 (0)89 4161 277-17 > > > > <https://www.bios-tec.de/> > > <https://www.bios-tec.de/> bios-tec GmbH | > <mailto:[email protected]> [email protected] | Nymphenburger Str. > 13 | 80335 München | <https://www.bios-tec.de/impressum> > Impressum > > > > > > _______________________________________________ Users mailing list > [email protected] > https://lists.ciphermail.com/mailman/listinfo/users > -- CipherMail email encryption Email encryption with support for S/MIME, OpenPGP, PDF encryption and secure webmail pull. W: https://www.ciphermail.com/ E: [email protected] T: +31 20 290 0088 _______________________________________________ Users mailing list [email protected] https://lists.ciphermail.com/mailman/listinfo/users
