Hi,
I noticed that Djigzo is rewriting the header.
Take the following example:
====
Alice has a Well-Known Encryption Apppliance
Bob has a mail processing appliance to direct the mail
Bob is running Djigzo
Alice sends a message to Bob
Subject:Test 03
Bob's mail processing appliance adds text [DJG-inbound] to the subject, giving:
Subject: Test 03,[DJG-inbound]
The mail processing appliance forwards the message on to Djigzo.
Djigzo forwards the mail on to the maibox server with the the header:
Subject:Test 03
Bob now is confused as to what happened to his subject header.
====
As far as I know this would be correct behaviour if we had specified Content-Type of
message/rfc822, that should trigger SMIME v3.1/3.2 "header protection", but this is NOT the
case as the Content-Type was not set. It's confusing for me as other S/MIME gateways do not have the same behaviour.
Do you maybe know of a setting to stop this happening ?
See james log file extract below to see the disappearing act.
Regards,
Jim
=====
27 Nov 2010 13:49:43 | INFO incoming | MailID: 1fc43643-1598-4837-8fec-652df483cf4b; Sender: jim(a)qa.xxx.net; Remote address: 192.168.50.32; Recipients: [jim(a)secure-mail-sandbox.com]; Subject: Test 03,[DJG-inbound]; Message-ID: <30106702.277.1290862166292.JavaMail.root(a)ncmous01.bank.prd>; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #1]
27 Nov 2010 13:49:43 | INFO internal | MailID: 1fc43643-1598-4837-8fec-652df483cf4b; Sender: jim(a)qa.xxx.net; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #1]
27 Nov 2010 13:49:43 | INFO decryptRemoveSignature | MailID: 1fc43643-1598-4837-8fec-652df483cf4b; Sender: jim(a)qa.xxx.net; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #1]
27 Nov 2010 13:49:43 | INFO postDecrypt | MailID: 1fc43643-1598-4837-8fec-652df483cf4b; Sender: jim(a)qa.xxx.net; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #1]
27 Nov 2010 13:49:43 | INFO transport | MailID: 1fc43643-1598-4837-8fec-652df483cf4b; Sender: jim(a)qa.xxx.net; Remote address: 192.168.50.32; Recipients: [jim(a)secure-mail-sandbox.com]; Subject: Test 03; Message-ID: <30106702.277.1290862166292.JavaMail.root(a)ncmous01.bank.prd>; (mitm.application.djigzo.james.mailets.Log) [Spool Thread #1]
Hello
are there any problems suspected when part of the mailflow will be
IPv6? Djigzo will be sandwiched with IPv4 localhost but we are on the
way to configure Postfix for IPv6. So the question is if there is some
internal processing (mail header etc.) which is purely IPv4 or may
choke on IPv6?
Many Thanks
Andreas
Hi,
A new release of Djigzo can be downloaded from www.djigzo.com. The new
version is a bug fix release which fixes two bugs and adds a new feature
to the Virtual Appliance console.
Release notes:
New
* The Virtual Appliance now allows you to specify which IP addresses can
access the Web Admin login page.
Bug fix
* Fix for "The PDF reply portal no longer attaches the uploaded
attachment" (bug GATEWAY-12). This was a regression of a previous bug
fix (GATEWAY-4).
* Fix for "The telephone number in the subject should be detected before
removing the encryption trigger" (bug GATEWAY-11).
The documentation has been updated/improved as well.
If you want to upgrade to the new version please read the "Upgrade
guide" (http://www.djigzo.com/documents/upgrade-guide.pdf) for instructions.
You only need to upgrade if you are using the PDF reply portal or are
using the SMS gateway with a mobile number on the subject and would like
these bugs to be fixed.
Kind regards,
Martijn Brinkers
--
Djigzo open source email encryption
