Wed 08 Aug 2012
MailServe for Mountain Lion 6.0.3
Category : Technology/MailServeForMountainLion6dot0dot3.txt
In the previous version, 6.0.2, I changed the way de-install works by forcing the user to stop Postfix and Dovecot manually before they can do a de-install. This was to ensure I have given every Postfix process sufficient time to finish their work before I delete the Postfix directory that was set up by MailServe.
However that wasn't very popular and so I have reverted it. The users are not used to having to stop Postfix and Dovecot manually before they do a de-install. They expect the system to do it for them. I will have to find some other ways of ensuring the completion of Postfix processes before I kill the system.
This version of MailServe also introduces a new field to allow Dovecot users to control the number of concurrent connections a user can make to the server. The default is 10 but the administrator can increase it when it has multiple clients accessing the server from multiple devices.
Finally this version fixes a bug in the Spam panel whereby the procmailrc file gets saved to the system with environment variables, like $HOME, etc... getting unintentionally expanded to hard-coded paths.
More Mountain Lion Differences
Category : Technology/NSTextFieldsInMountainLion.txt
has been hit by another stealth change Apple made to Mountain Lion.
NSTextFields in Mountain Lion now appear to have auto-formatting turned on (which is not the case with previous versions of OS X). In other words, when a number value is entered into a text field, the text field will automatically format its appearance according to the number display format the user had chosen in System Preferences.
For example if 2012 is entered into a text field, NSTextField will automatically format it as 2,012, as shown below.
If you entered "abcd" into the text field, that will of course be displayed as "abcd". All very convenient. But if 2012 stands for the year we want to capture data for, then displaying it as 2,012 looks rather odd. Worse, when we take the value back as a string value and use it to compare against another string value like "2012", we find we're comparing "2,012" against "2012", thus throwing a lot of the embedded (and assumed) programming logic out of whack.
So, in Mountain Lion, we've had to go through a lot of our code to clean up stuff like that. There may be more lurking that we have not yet spotted. So let us know as soon as you see something that isn't working as it should.