am seeing how to set up the S/MIME subject trigger to allow signing of messages independently from encrypting; is this possible ? I have created my domain, added my user, and installed my personal certificate. I set the Encrypt Mode to Allow, enabled S/MIME, checked Strict Mode and unchecked Only sign when encrypt. I defined the subject trigger (?i)(\[secure\]) and then sent a test message to an external user; whom is not defined within Djigzo as a recipient. I thought that as the recipient was not defined, and that I had unchecked only sign when encrypt that the message would have indeed been signed ? I know that its possible to do by using the Force signing trigger but is it possible from the subject line as-well ? Certain email clients do not have the front-end capability to add additional headers so being able to make use of the subject line would be very useful indeed; for both signing and encrypting.
am seeing how to set up the S/MIME subject trigger to allow signing
of messages independently from encrypting; is this possible ? I have
created my domain, added my user, and installed my personal
certificate. I set the Encrypt Mode to Allow, enabled S/MIME,
checked Strict Mode and unchecked Only sign when encrypt. I defined
the subject trigger (?i)(\[secure\]) and then sent a test message to
an external user; whom is not defined within Djigzo as a recipient.
I thought that as the recipient was not defined, and that I had
unchecked only sign when encrypt that the message would have indeed
been signed ? I know that its possible to do by using the Force
signing trigger but is it possible from the subject line as-well ?
Certain email clients do not have the front-end capability to add
additional headers so being able to make use of the subject line
would be very useful indeed; for both signing and encrypting.
Hello
it should work the way you described. Pleas check the following:
- Is the sender marked as "internal" user
- Do you have imported the key/certifcate pair for this user
- Is the external recipient not member of a domain set as internal
- Does the mail touch Djigzo at all
As of subject trigger, this only works for encrypting as of today as
far as i know.
I checked https://jira.djigzo.com/browse/GATEWAY-24 and that does indeed suggest using a regex subject filter would also work. So I have gone ahead and tested it using the following for the trigger:
(?i)^subject :\s\[sign\]
and according to djigzo.log that does indeed trigger the signing:
01 Aug 2012 09:58:04 | INFO Sending SMS messages is not allowed for the sender; MailID: 0b685927-eb6f-441c-a542-431deb24e8f8 (mitm.application.djigzo.james.mailets.Default) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO checkMustEncrypt state | MailID: 0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************; Sender: ************; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO checkSMIMESign state | MailID: 0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************; Sender: ************; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO setupSMIMESignOnly state | MailID: 0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************; Sender: ************; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO sMIMESignOnly state | MailID: 0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************; Sender: ************; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO S/MIME signing the message; MailID: 0b685927-eb6f-441c-a542-431deb24e8f8 (mitm.application.djigzo.james.mailets.Default) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO transport state | MailID: 0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************; Sender: ************; Remote address: 127.0.0.1; Recipients: [************]; Subject: [sign] Test Signing; Message-ID: <891913157.323838.1343829476353.JavaMail.root(a)innovot.com>; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
but when I receive the email on my external account there are no headers, or even the S/MIME attachment, to show that it has been signed.
What am I missing ? I do have a certificate which matches the sending account.
···
--
Thanks, Phil
----- Original Message -----
On 07/31/2012 11:48 AM, lst_hoe02(a)kwsoft.de wrote:
> As of subject trigger, this only works for encrypting as of today
> as
> far as i know.
I can confirm that, but as there is a signing trigger in the UI, it
should work for signing as well. I'll talk to Martijn about that.
Christine
--
dagdag is just a two character rotation of byebye
Resolved through stupidity ... cert chain was incomplete! ;(
···
--
Thanks, Phil
----- Original Message -----
Hi Christine,
I checked https://jira.djigzo.com/browse/GATEWAY-24 and that does
indeed suggest using a regex subject filter would also work. So I
have gone ahead and tested it using the following for the trigger:
(?i)^subject :\s\[sign\]
and according to djigzo.log that does indeed trigger the signing:
01 Aug 2012 09:58:04 | INFO Sending SMS messages is not allowed for
the sender; MailID: 0b685927-eb6f-441c-a542-431deb24e8f8
(mitm.application.djigzo.james.mailets.Default) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO checkMustEncrypt state | MailID:
0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************;
Sender: ************;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO checkSMIMESign state | MailID:
0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************;
Sender: ************;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:04 | INFO setupSMIMESignOnly state | MailID:
0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************;
Sender: ************;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO sMIMESignOnly state | MailID:
0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************;
Sender: ************;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO S/MIME signing the message; MailID:
0b685927-eb6f-441c-a542-431deb24e8f8
(mitm.application.djigzo.james.mailets.Default) [Spool Thread #3]
01 Aug 2012 09:58:05 | INFO transport state | MailID:
0b685927-eb6f-441c-a542-431deb24e8f8; Originator: ************;
Sender: ************; Remote address: 127.0.0.1; Recipients:
[************]; Subject: [sign] Test Signing; Message-ID:
<891913157.323838.1343829476353.JavaMail.root(a)innovot.com>;
(mitm.application.djigzo.james.mailets.Log) [Spool Thread #3]
but when I receive the email on my external account there are no
headers, or even the S/MIME attachment, to show that it has been
signed.
What am I missing ? I do have a certificate which matches the sending
account.
--
Thanks, Phil
----- Original Message -----
> On 07/31/2012 11:48 AM, lst_hoe02(a)kwsoft.de wrote:
> > As of subject trigger, this only works for encrypting as of today
> > as
> > far as i know.
> I can confirm that, but as there is a signing trigger in the UI, it
> should work for signing as well. I'll talk to Martijn about that.
>
> Christine
>
> --
> dagdag is just a two character rotation of byebye
>
> _______________________________________________
> Users mailing list
> Users(a)lists.djigzo.com
> http://lists.djigzo.com/lists/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)lists.djigzo.com http://lists.djigzo.com/lists/listinfo/users