Re: [Djigzo users] Djigzo with James 2.3.2 (recreating of message-IDs)

The main question is "should a modified message get a new message-id"? You could argue that when you send a message to one recipient that the message should keep the same message-id even though the message is encrypted or signed by the gateway. My view is that the message was altered and the message should therefore get a new message-id. Now to make things a bit more complicated, what should the message-id be when a message is sent to multiple recipients with different encryption requirements. For example recipient A cannot read encrypted or signed email so no encryption, recipient B requires S/MIME encrypted email, recipient C only wants digitally signed email and recipient D wants to receive it encrypted by PDF. Djigzo splits the message into 4 different messages because the 4 recipients have non-compatible requirements. Do you expect all the 4 messages to have the same message-id? My view would be that every message should have a different message-id. Different messages with the same message-id can lead to problems. For example Exchange has a filter that removes messages with a duplicate message-id. This means that messages can sometimes magically 'disappear'. A possible 'solution' I have been thinking of, but I have not yet implemented, is to add a "X-Original-Message-ID" header that contains the message ID of the source message. Note that only messages that are modified (signed/encrypted etc.) have a new message-id. Kind regards, Martijn Brinkers lst_hoe02(a)kwsoft.de wrote: -- Djigzo open source email encryption