Was Tiger mail dictionary changed?

Scripting Forums AppleScript | Mac OS X
,
#1

I had a working script that sets a signture in mail. Now that we have upgraded to Tiger the script no longer works. It creates the signature name but the content is empty. I don’t see anything in the dictionary that indicates I am doing anyting wrong. This is the line that used to work:

make new signature with properties {name:"Standard", content:usersig}

Can someone tell me what I need to change for Tiger? TIA.

#2

let me know if this works. I’m not on a mac atm but it should work

make new signature at beginning of signatures with properties {name:"Standard", content:usersig}
#3

Thanks for the suggestion and I apologize for taking so long to reply (very busy here these days). Anyway, I regret to tell you that it didn’t help. I get the same results. It creates the signature entry but the content is empty. I am posting all of the relevent segment of the script in the hopes someone can see something else that is Tiger incompatable. Thanks again.

tell application "Mail"
	set sigcount to count of signatures
	repeat with i from 1 to sigcount - 1
		set signame to name of signature i
		delete signature named signame
	end repeat
	set sigcount to count of signatures
	set signame to name of signature 1
	delete signature named signame
	make new signature at beginning of signatures with properties {name:"Standard", content:usersig}
	set selected signature to "Standard"
end tell
#4

I need to resurrect this issue. I really need to get this working and I am dead in the water on this. TIA. :frowning:

#5

What’s the content of usersig…?
Is it anything meaningful to Mail…?
You might try copying a meaningful sign into a new sig entry this way and observe in the AS events loop what exactly goes on…