All messages being signed

Hello:

am having a little trouble in getting the S/MIME force signing mechanism to work. I have set the encryption mode to None and defined a trigger for signing enforcement. The problem is that every single email that goes out automatically gets signed even though I have not added the trigger. How does one stop that please ?

···

--
Thanks, Phil

Either you have unchecked "only sign when encrypt" (if unchecked, all
email will be signed) or you signing trigger always matches.

Kind regards,

Martijn Brinkers

···

On 08/31/2012 02:07 PM, Phil Daws wrote:

am having a little trouble in getting the S/MIME force signing
mechanism to work. I have set the encryption mode to None and defined
a trigger for signing enforcement. The problem is that every single
email that goes out automatically gets signed even though I have not
added the trigger. How does one stop that please ?

--
DJIGZO email encryption

ah okay ... its the former then ... anyway to override that behavior ?

···

--
Thanks, Phil

----- Original Message -----

On 08/31/2012 02:07 PM, Phil Daws wrote:
> am having a little trouble in getting the S/MIME force signing
> mechanism to work. I have set the encryption mode to None and
> defined
> a trigger for signing enforcement. The problem is that every single
> email that goes out automatically gets signed even though I have
> not
> added the trigger. How does one stop that please ?

Either you have unchecked "only sign when encrypt" (if unchecked, all
email will be signed) or you signing trigger always matches.

Kind regards,

Martijn Brinkers

--
DJIGZO email encryption
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users

What do you mean with "override that behaviour"? You can check or
uncheck it. If checked, message will only be signed if encrypted *or* if
the signing trigger is set (i.e., if the signer trigger is allowed and
the header matches). Oh I guess that's what you mean, whether the
signing trigger overrules "only sign when encrypt". Yes it does. You can
check the MPA mail flow in the appendix of the administration guide. It
shows you all the steps on how email gets handled.

Kind regards,

Martijn

···

On 08/31/2012 02:17 PM, Phil Daws wrote:

ah okay ... its the former then ... anyway to override that behavior ?

--
DJIGZO email encryption

Martijn:

can you see what is wrong with this signing trigger ?

(?i)Subject:\s\[sign\].*

···

--
Thanks, Phil

----- Original Message -----

On 08/31/2012 02:17 PM, Phil Daws wrote:
> ah okay ... its the former then ... anyway to override that
> behavior ?

What do you mean with "override that behaviour"? You can check or
uncheck it. If checked, message will only be signed if encrypted *or*
if
the signing trigger is set (i.e., if the signer trigger is allowed
and
the header matches). Oh I guess that's what you mean, whether the
signing trigger overrules "only sign when encrypt". Yes it does. You
can
check the MPA mail flow in the appendix of the administration guide.
It
shows you all the steps on how email gets handled.

Kind regards,

Martijn

--
DJIGZO email encryption
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com
http://lists.djigzo.com/lists/listinfo/users

Martijn:

can you see what is wrong with this signing trigger ?

(?i)Subject:\s\[sign\].*

I thought you already fixed that :slight_smile:

From previous email about the subject:

"The format for the signing trigger is not exactly a regular
expression. The format is as follows (see the admin guide).

HEADER-NAME:REG-EXP

So, the part before the : should be the name of the header and the
part after : should be a reg expression that matches the header
value."

See page 23 of the admin guide for more info

So you should use:

Note: I have not tested this

Kind regards,

Martijn Brinkers

···

On 08/31/2012 05:04 PM, Phil Daws wrote:
Subject:(?i)\s\[sign\].*

--
DJIGZO email encryption