Encrypt, decrypt and signings fails under MacOS X 10.4.2
Brought to you by:
simon450
When trying to sign or encrypt an message under
Entourage 2004 a message box appears after the mantra
dialoge stating:
TEC OSAX had an error:
kTECNoConversionPathErr
When trying to decrypt a message under Entourage 2004 a
message box appears after the mantra dialoge stating:
ls:
/private/var/tmp/folders.501/TempraryItems/EntourageGPG
Temp/Messages/148771: No such file or directory
This is all under MacOS X 10.4.2
Logged In: NO
I think, 'kTECNoConversionPathErr' may be caused by
'Unicode-1-1-UTF-8' strings in EntourageGPG's AppleScripts.
I changed them to 'UTF-8'.
( But, I found another problem. Is EntourageGPG compatible
with international charsets ? )
Logged In: NO
I get a similar message with 10.4.2 and Entourage 2004 but my says folders.503
I saw a folder called "503" in that /private/var/tmp that had
TemporararyItems....
Logged In: YES
user_id=1400652
> I think, 'kTECNoConversionPathErr' may be caused by
> 'Unicode-1-1-UTF-8' strings in EntourageGPG's
> AppleScripts.
> I changed them to 'UTF-8'.
This worked for me.
Logged In: NO
ditto in 10.4.4
Logged In: NO
Please, could you describe, WHERE you changed the UTF ...?
Which script, which path? I'd appreciate that!
Logged In: YES
user_id=1400652
/Users/username/Documents/Microsoft User Data/Entourage/Script Menu
Items/EntourageGPG/
Replace it globally. MacOS X 10.4.5 also.
Logged In: YES
user_id=1400652
The no such file or directory error seems to be related to the following line:
Common's MUAOutputDecryptInWindow(blurbText, decryptedText, theMessage,
lstrings)
theMessage variable is set to the number you see at the end of the error.
Logged In: YES
user_id=1400652
The no such file or directory error seems to be related to the following line:
Common's MUAOutputDecryptInWindow(blurbText, decryptedText, theMessage,
lstrings)
theMessage variable is set to the number you see at the end of the error.
Logged In: YES
user_id=1400652
Go to /Users/username/Library/Application Support/EntourageGPG and find
the file called "common.incl".
set fileExists to do shell script "ls '" & POSIX path of fileLocation & "'"
if fileExists is "" or fileExists contains "No such file or directory" then
set fp to open for access file fileLocation with write permission
set eof fp to 0
write windowContents to fp
close access fp
end if
The output of the ls command on the first line above isn't being captured by
the script. The bad way around this is to remove the checking. i.e. comment
out or remove the first two lines and the last line above. The better way
would be to figure out why the script isn't processing the error like it is
supposed to.