Hi Dale, My apologies for the late reply. I must have missed this message
On 02/13/2014 11:15 PM, de Longpre, Dale wrote: > It appears that the subject trigger only works on the senders domain > and users. I'm trying to make encryption optional for a single > domain. We set the target domain to "no encryption" and then put in > the regex trigger of ".*" to test it. It doesn't work. The MPA > log doesn't seem to indicate that it even checks this. Doing the > same test by putting a subject trigger on the senders email does > work. The subject trigger is a sender specific setting. This means that email encryption will only be forced using the subject trigger if the setting for the sender says so. Supporting a subject trigger for recipients is not straightforward since this would require that email be split based on some value in the subject. > We would only like to have this one domain use triggers and the setup > for the external domain allows us to set the trigger but how would > you ever get it to check it? Can you explain what your use case is? Perhaps there is a different option. If I understand you correctly you want to only encrypt email if there is some keyword in the subject *and* if the recipient domain is some kind of domain? If this is what you want then this is only possible by manually reconfiguring the mail flow in an xml file. Kind regards, Martijn Brinkers -- DJIGZO email encryption _______________________________________________ Users mailing list [email protected] https://lists.djigzo.com/lists/listinfo/users
