On 05-09-19 16:07, Ralf Kirmis via Users wrote:
we have a cipher mail gateway which has multiple
internal domains, which belong to different customers.
If customer one wants to send an encrypted pdf mail to customer two,
the mail gets not encrypted, because the ciper mail declares the mail as incoming and
doesn't go through the processs of evaulating the subject trigger and encrypting the
mail to pdf.
Is it possible to turn off this behavior, so that's is possible to send encrypted
mails between internal domains?
The Locality setting (internal vs external) determines whether an
incoming email should be handled by the decryption (internal) or by the
encryption (external) pipeline. So email sent to an internal domain will
not be encrypted. The decryption pipeline is needed if you want the
gateway to decrypt incoming S/MIME or PGP encrypted email. If you do not
use S/MIME or PGP you can decide to not make the domains internal. Than
all email sent to those domains will be encrypted, this however also
applies to email sent by others. If this is not the intended behavior
or if you want to keep the internal domains because you need to decrypt
S/MIME or PGP emails than you need some sort of special rule. Something
like: if email comes from an internal domain and it is sent to an
internal domain treat the recipient domain as an external domain (or
some other rule with the same result). This however cannot be configured
from the GUI. You can however change the complete mail flow (see
config.xml) and get almost any type of behavior you need.