9 Nov
2009
9 Nov
'09
2:18 p.m.
Zitat von Martijn Brinkers <martijn(a)djigzo.com>om>:
lst_hoe02(a)kwsoft.de wrote:
From what i have read in the james docu the non-altering behaviour
would be default from james 2.3.2 onward. This, on the other hand
means that there *is* a setting to turn it on again. Maybe the easiest
way would be to use james 2.3.2 with next Djigzo release and include
the setting in the documentation. But i don't know how much the djigzo
internal james differs from the official releases.
Regards
Andreas
Fact is that the actual behavior makes djigzo
unusable for us because
our sending system depends on the message-ID to get a threading like
mail presentation.
You can update to a new James. However, I have added some functions to
James to make it throttle the connections when the queue becomes too
large so if you live without these additions you can use a different
James version. I will see whether I can add a system setting that
ensures that the message will not use a new message-id. If I add this
setting it will not be on by default because it can be problematic with
Exchange (see other messages)