On 07/28/2011 09:52 AM, Martijn Brinkers wrote: > On 01/-10/-28163 08:59 PM, [email protected] wrote: >> Zitat von Martijn Brinkers <[email protected]>: >> >>> Hi, >>> >>> A new Djigzo Gateway release candidate (2.1.1) is available. >>> >>> http://www.djigzo.com/beta.html >>> >>> Release notes: >>> >>> Improvements >>> >>> * If a certificate was available for a recipient, a user object was >>> always created for that recipient. The user is no longer added by >>> default. >> >> What is the reasoning behind this one? I found it handsome to which >> addresses where handled by S/MIME and which not by consulting the user >> list. > > My thinking was that you only need to add a user when you need to > override an inherited setting. Adding an external user when a > certificate is available for the user resulted in a lot of pointless > users when using domain to domain encryption since a certificate is > available for every sender. > > I can however see your point in that it helps you to see for which > external users a certificate is available. The old behavior can be > reenabled by replacing > > RecipientHasCertificates=matchOnError=false,false > > with > > RecipientHasCertificates=matchOnError=false,true > > but this requires you to change the config.xml file. I guess you want it > to be configurable from the GUI? ;)
I will add a setting that allows you to specify whether you want a user to be created automatically when the recipient has a certificate. If you use domain to domain encryption you can then set the domain setting for that particular domain to not add a user for every recipient of that domain. Kind regards, Martijn -- Djigzo open source email encryption _______________________________________________ Users mailing list [email protected] http://lists.djigzo.com/lists/listinfo/users
