Moderators: ScalixSupport, admin
ja30278 wrote:
It _IS_ unfortunate. I've spent years watching the groupware space, waiting for a viable linux solution. I definitely don't want to speak negatively about Scalix as a product, because it's very good software, and it's _almost_ there; but there are several deal killers that make it increasingly obvious that I can't roll it into production.
cdclark wrote:Actually that's quite helpful. I'd rather take the step of setting the permissions than expect the end user to configure a secondary profile or imap client. What is the syntax for opening a mailbox on another mailnode within Outlook's dialog box? I would presume its something like Tommy Tester/restore,mydomain or something like that?
Code: Select all
ommodent -e S=Tester/G=Tommy/OU1=scalix/OU2=restore -n EX-CDA-DIRECTORY=1
cdclark wrote:-Clumsy backups/restores
Have you tried the SEP sesam solution to provide some packaging around it?cdclark wrote:-Inability to desktop sync with a modern blackberry (and crazy prizing from Notify link).
Are you talking about USB-based cradle sync here? In that case, please get in touch with our Support (if you're a customer) or Sales (if you're evaluating) teams. We've been working with Intellisync (who provide the sync software the Blackberry ships with) to provide a solution here as the problem was only that they were checking what mailserver they are talking to and unfortunately only accepted Exchange....cdclark wrote:Bring on the funambol!
ja30278 wrote:It _IS_ unfortunate. I've spent years watching the groupware space, waiting for a viable linux solution. I definitely don't want to speak negatively about Scalix as a product, because it's very good software, and it's _almost_ there; but there are several deal killers that make it increasingly obvious that I can't roll it into production.
Anybody have any idea about the return poilcy? Or, at the very least, is the license transferrable?
tanchai wrote:i got this error
sh omrestore -u test" -f "/var/scalix-backup/users/pc-37,frc/Test-20060410-mail.gz" -i "test@pc-37.frc.test.com" -p "jackson" -a "test@pc-37.frc.test.com"
Restore mailnode pc-37,frc exists
Creating user: test/pc-37,frc IA=test@pc-37.frc.test.com AUTH ID=test@pc-37.frc.test.com PASS=test
omaddu : [OM 8256] The Internet Address is already assigned to
another local user on the mailnode.
Error: Failed to create user
Code: Select all
omdelu -n "test/pc-37,frc"
Code: Select all
function validate_user
{
# destroys the restore user account (if it exists) and recreates it.
$SCALIX_BIN/omshowu -n $RESTORE_ID >/dev/null 2>&1
if [ "$?" = "0" ]
then
echo_and_log "Found existing user with ID $RESTORE_ID , deleting"
$SCALIX_BIN/omdelu $RESTORE_ID
[ "$?" != "0" ] && exit_with_error "Unable to delete existing user with ID $RESTORE_ID"
fi
$SCALIX_BIN/omshowu -n "$RESTORE_NAME/$RESTORE_MN" >/dev/null 2>&1
if [ "$?" = "0" ]
then
echo_and_log "Found existing user with name $RESTORE_NAME on $RESTORE_MN , deleting"
$SCALIX_BIN/omdelu -n "$RESTORE_NAME/$RESTORE_MN"
[ "$?" != ")" ] && exit_with_error "Unable to delete existing user $RESTORE_USER"
fi
echo_and_log "Creating user: $RESTORE_USER/$RESTORE_MN IA=${RESTORE_IAM} AUTH ID=${RESTORE_ID} PASS=${RESTORE_PASS}"
$SCALIX_BIN/omaddu -x -n "$RESTORE_USER/$RESTORE_MN/IA=${RESTORE_IAM}" $RESTORE_ID -p $RESTORE_PASS
if [ "$?" != "0" ]
then
exit_with_error "Failed to create user $RESTORE_USER/$RESTORE_MN"
else
echo_and_log "Successfully created user $RESTORE_USER/$RESTORE_MN"
fi
}
##### main program loop begins
# process command line arguments
# -h : help
# -m <mailnode> : restore mailnode
# -i <id> : restore user authid.
# -a <addr> : restore user internet mail address.
# -p <pass> : restore user password
# -l <file> : logfile
# -f <file> : file to restore
# -u <user> : username to restore
while getopts hm:u:p:i:a:l:f: opt
do
case "$opt" in
h) usage ;;
m) RESTORE_MN=$OPTARG ;;
u) RESTORE_USER=$OPTARG ;;
p) RESTORE_PASS=$OPTARG ;;
i) RESTORE_ID=$OPTARG ;;
a) RESTORE_IAM=$OPTARG ;;
l) LOGFILE=$OPTARG ;;
f) RESTORE_FILE=$OPTARG ;;
\?) usage ;;
esac
done
florian wrote:So, the way to resolve this for the time being would be to leave out the -x when creating the user (put it in the system directory), but then immedidately hide it from the addressbook display - either through the respective Checkbox in SAC or through theCode: Select all
ommodent -e S=Tester/G=Tommy/OU1=scalix/OU2=restore -n EX-CDA-DIRECTORY=1
That would then work.
I'll check with engineering if there is any other way.
Also, again, we're working on many fronts to make backup and recovery as easy as possible in the next release; on this subject, the next release will allow you to omcpinu you data into a subfolder of the existing users mailbox, so this pretty complicated login handling will go away completely. Also, you won't need additional licenses for the shadow users then.
Hope this helps,
Florian.[/code]
florian wrote:Have you tried the SEP sesam solution to provide some packaging around it?
florian wrote:
Are you talking about USB-based cradle sync here? In that case, please get in touch with our Support (if you're a customer) or Sales (if you're evaluating) teams. We've been working with Intellisync (who provide the sync software the Blackberry ships with) to provide a solution here as the problem was only that they were checking what mailserver they are talking to and unfortunately only accepted Exchange....
I personally and we as a company strongly believe in Open protocols and are making every sensible effort to work with standards-based solutions such as SyncML. Therefore, we do evaluate a number of options going forward. However, as good as some solutions sound on paper, they are not really ready for prime time yet. SyncML-based eMail synchronisation is a good example of that; it is being introduced in more and more devices in a way where it really works, but unfortunately, it cannot be compared to a full Wireless solution as provided by RIM or Notify, at least yet.
Hope this helps,
cheers,
Florian.
florian wrote:I'd say - this depends - also obviously a lot on your hardware, storage configuration. The time it takes to properly SUR also depends on the backup software in use and the process/cut done.
I wonder why your omcpoutu's take so long - this is typically a rather fast operation; also, one thing that's usually pretty helpful - multiple (if not many) omcpoutu's can be run in parallel, therefore, in absolute time things change quite drastically. (actually, for system moves we've sometimes run 100s or those in par.)
are you in touch with us? it would make sense to look at your actual system configuraition and compare this to our internal timeings and numbers.
-- f.
Users browsing this forum: No registered users and 11 guests