I had the same problem. Since the update, Samba is no longer following sysmlinks in a share if they lead outside of the share directory (as links to the .shadow directories). The reason is a security problem.
See here:
http://www.samba.org/samba/news/symlink_attack.htmlTo re-enable the previous default behaviour, the /etc/samba.conf needs to contain the line "wide links = yes" (and for good measure "follow symlinks = yes") in each share definition section. To avoid the security issue described in the link above, I understand it is wise to check if "unix extensions = no" is set in the global section of smb.conf.
See, e.g., here:
http://ubuntuforums.org/showthread.php?t=1439092&page=3Because the SME server re-creates the smb.conf automatically, I added some custom templates on my servers so that the changes are permanent:
/etc/e-smith/templates-custom/etc/smb.conf/50homes
with the content:
"[homes]
comment = Home directory
browseable = no
guest ok = no
read only = no
writable = yes
printable = no
create mode = 0660
force create mode = 0660
directory mode = 0770
force directory mode = 0770
path = /home/e-smith/files/users/%S/home
follow symlinks = yes
wide links = yes"
and
/etc/e-smith/templates-custom/etc/smb.conf/ibays/21symlinks
and
/etc/e-smith/templates-custom/etc/smb.conf/ibays/22widelinks
with the respective contents:
"{
$OUT .= "follow symlinks = yes";
}"
and
"{
$OUT .= "wide links = yes";
}"
Maybe not the most elegant solution, but it solved the problem over here.
Hope it helps!