yes it is a bug. The autoresponder does not recognize the encryption type. Nevertheless, displaying arabic text should also work without this work around.
If you cannot get it work without it, you have to fix it uddeim.php (approx. line 1050), replace the complete autoresponder block with:
Code:
// ##################################################################################################
// autoresponder
// ##################################################################################################
if ($config->autoresponder==1 || ($config->autoresponder==2 && uddeIMisAdmin($rec_gid))) {
$ison = uddeIMgetEMNautoresponder($savetoid);
if ($ison==1) {
// NOTE: An autoresponder message is created and the outbox message is marked deleted.
// This is not a bug since in my opinion it does not make sense to store autoresponder messages AND the received message.
$autorespondertext = uddeIMgetEMNautorespondertext($savetoid);
$savemessage=addslashes(strip_tags($autorespondertext));
// $sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $savemessage ."', ".$savedatum.", 1,".$savedatum.")";
$themode=0;
if ($config->cryptmode==1) {
$cm = uddeIMencrypt($savemessage,$config->cryptkey,CRYPT_MODE_BASE64);
$sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $cm ."', ".$savedatum.", 1,".$savedatum.")";
} elseif ($config->cryptmode==2) {
// no password entered, then fallback to obfuscating
$themode=1;
$thepass=$config->cryptkey;
$cm = uddeIMencrypt($savemessage,$thepass,CRYPT_MODE_BASE64);
$sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox, cryptmode, crypthash) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $cm ."', ".$savedatum.", 1,".$savedatum.",".$themode.",'".md5($thepass)."')";
} elseif ($config->cryptmode==3) {
$cm = uddeIMencrypt($savemessage,"",CRYPT_MODE_STOREBASE64);
$sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox, cryptmode, crypthash) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $cm ."', ".$savedatum.", 1,".$savedatum.", 3)";
} elseif ($config->cryptmode==4) {
// no password entered, then fallback to obfuscating
$themode=1;
$thepass=$config->cryptkey;
$cm = uddeIMencrypt($savemessage,$thepass,CRYPT_MODE_BASE64);
$sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox, cryptmode, crypthash) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $cm ."', ".$savedatum.", 1,".$savedatum.",".$themode.",'".md5($thepass)."')";
} else {
$sql="INSERT INTO #__uddeim (fromid, toid, message, datum, totrashoutbox, totrashdateoutbox) VALUES (".(int)$savetoid.", ".(int)$savefromid.", '". $savemessage ."', ".$savedatum.", 1,".$savedatum.")";
}
$database->setQuery($sql);
if (!$database->query()) {
die("SQL error when attempting to save a message" . $database->stderr(true));
}
}
}
It will be fixed in the next uddeIM release (you can also pull the developer version from the trunk, if you like).
