Script to remove any recovery partition other than from the boot drive.

#!/bin/bash
echo "--------------------------------------------------"    
Boot=`mount | grep " / " | cut -d " " -f 1 | cut -d "/" -f 3`
Recovery=`diskutil list | grep Recovery\ HD | awk {'print $NF;}'`
echo Recovery partition found at: $Recovery

for i in $Recovery
    do
    RecoveryMinusOne=`echo $i | cut -c 1-6`$((`echo $i | cut -c 7`-1 ))
    echo
        if [ $RecoveryMinusOne == $Boot ]; then
            echo Ignoring partition $i next to boot partition $Boot
        else
            echo Merging partition $i into $RecoveryMinusOne
            read -r -p "Are you sure? [Y/n] " response
            case $response in
            [yY][eE][sS]|[yY]) 
                diskutil mergePartitions HFS+ MacintoshHD $RecoveryMinusOne $i
                ;;
            *)
                ;;
            esac
            echo
            echo "--------------------------------------------------"    
        fi
done
echo "Copyleft 2012, Daniel Zeller"

Outlook message recall dissected

It appears that Exchange 2010 is transforming a message recall request and packing it into a “standard” SMTP transportable message.

My research indicates that http://stackoverflow.com/questions/2064927/smtp-e-mail-recall-from-php is wrong. 3D 0A is simply line feed carriage return. I don’t think that triggers the recall and my testing supports this.

I have noticed a strong correlation between the Thread-Index of the original message and the recall. These are four messages and then four matching recalls:

Ac2PvBNoEcEDdmRxTvWAknQEITPwwg==
Ac2PvBgtZD4JdnxMSku7d8GsBxG89w==
Ac2PvBwk1kDHotcMSA+WvJ0iYCDWqQ==
Ac2PvB/GWZpqwZw3TnKf/fpIdw90Fg==

Ac2PvBx7EcEDdmRxTvWAknQEITPwwg==
Ac2PvCENZD4JdnxMSku7d8GsBxG89w==
Ac2PvCQZ1kDHotcMSA+WvJ0iYCDWqQ==
Ac2PvCdqWZpqwZw3TnKf/fpIdw90Fg==

Base64 decoded and shown as HEX this pattern emerges (message and recall matched up):

01CD8FBC 182D 643E09767C4C4A4BBB77C1AC0711BCF7
01CD8FBC 210D 643E09767C4C4A4BBB77C1AC0711BCF7

01CD8FBC 1C24 D640C7A2D70C480F96BC9D226020D6A9
01CD8FBC 2419 D640C7A2D70C480F96BC9D226020D6A9

01CD8FBC 1FC6 599A6AC19C374E729FFDFA48770F7416
01CD8FBC 276A 599A6AC19C374E729FFDFA48770F7416

(And that’s about how far I got.)

My testing does not show any “special strings” as suggested by http://www.officekb.com/Uwe/Forum.aspx/ms-outlook/48006/Message-recall#37ertgF5c3059U1individualnet I assume this is how it worked in an earlier version.

10.7: Can’t trusted bind to 10.6 OD Server in Magic Triangle

A Mac OS X v10.7 Lion client may be unable to connect to a Mac OS X v10.6 Open Directory Server. This can happen if Lion uses Authenticated Binding to a Mac OS X v10.6 Open Directory Server that is also bound to Active Directory by means of a magic triangle.

Resolution

To allow the Mac OS X v10.7 clients to connect, either don’t use authenticated binding, or use the following Terminal commands.

Execute these commands on the Mac OS X v10.6 Open Directory Master Server and Replicas:

Note: These commands will turn off GSSAPI authentication for the LDAP Server on the Mac OS X v10.6 Open Directory Master Server and Replicas. The servers will then use CRAM-MD5 authentication.

sudo rm /usr/lib/sasl2/openldap/libgssapiv2.2.so
sudo rm /usr/lib/sasl2/openldap/libgssapiv2.la

Restart the server after making this change.
If you want to restore the original settings, execute these commands:

cd /usr/lib/sasl2/openldap
sudo ln -s ../libgssapiv2.2.so 
sudo ln -s ../libgssapiv2.la

Restart the server after making this change.

 

http://support.apple.com/kb/TS3861

serial port on xserve 10.6

sudo launchctl remove com.apple.xserve.serial-ports

screen /dev/cu.serial <port_speed>

Replace the <port_speed> with the port speed supported by the device you are trying to control. This should allow you to connect to the device and control it.

When you are done, you can reset the Terminal by performing these key strokes

Type Ctrl-A and press Enter, then type Ctrl-\ and press Enter.