Apple scripts dont work for IMAP?

[kevs12]

Version: 2004
Operating System: Mac OS X 10.4 (Tiger)
Processor: Power PC
Email Client: imap

I just have a handful of scripts, but important. don't seem to work with IMAP, why not? thanks.

 

[William Smith [MVP]]

I just have a handful of scripts, but important. don't seem to work
with IMAP, why not? thanks.

Not enough information to provide an answer.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[kevs12]

Bill,
I'm using Entourage POP for 10 years. I have some scripts, for example, check size of messages, or soft wrap text.
I just created my first IMAP accounts. Those scripts, none of them, work for my new IMAP email accounts.

 

[Diane Ross]

I just created my first IMAP accounts. Those scripts, none of them, work for
my new IMAP email accounts.

Did you create them under the IMAP tab in rules?

Each type of account has to have it's own rules.

 

[kevs12]

YEs, Diane, but these are scripts that are in MUD, and are in the Script folder, visible on the menu bar.

 

[William Smith [MVP]]

I'm using Entourage POP for 10 years. I have some scripts, for
example, check size of messages, or soft wrap text. I just created my
first IMAP accounts. Those scripts, none of them, work for my new
IMAP email accounts.

Can you point us to some of these scripts online? I'd need to see this
behavior to understand what's happening.

--

bill

Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>

 

[kevs12]

I hope these are same one I have:
soft wrap text ( written by Paul Berkowitz -- what happened to him?

<http://mac.wareseeker.com/download/soft-wrap-text-entourage-1.0.rar/328050>

The real favorite is nuke messages. Control D, and instead of messages going to trash, they just get nuked in one shot. not sure where find this online.

 

[Diane Ross]

I hope these are same one I have:
soft wrap text ( written by Paul Berkowitz -- what happened to him?

His real life got too busy.

<http://mac.wareseeker.com/download/soft-wrap-text-entourage-1.0.rar/328050>

Have you used the Entourage AutoText Cleanup. Select some text, hold down
the Contextual key and select AutoText Cleanup > then select the option you
want.

The real favorite is nuke messages. Control D, and instead of messages going
to trash, they just get nuked in one shot. not sure where find this online.

I use the nuke script on IMAP and don't have any problems. Are you trying to
run from a shortcut? Try running it from the script menu.

 

[kevs12]

Diane, thanks,
I tried the auto text clean up, never works for me. But I'll try again.

just tried nuke from the menu, and I always get in IMAP
"Microsoft Entourage got an error: Apple Event timed out"

 

[Diane Ross]

just tried nuke from the menu, and I always get in IMAP
"Microsoft Entourage got an error: Apple Event timed out"

Testing in a new User will quickly tell you if the problem is system wide or
if it¹s your User¹s folder that contains the problem.

Go to System Preferences --> Create a New User in Accounts. Switch to the
New User by logging out/in or use Fast User Switching.

Move some scripts to the Shared folder for testing along with a few
messages.

In the new User, drag the test files to the desktop for access.

 

[kevs12]

Diane, not a user issue. The problem just started when I made my first IMAP accounts. The scripts were perfectly still in POPs, just not in new IMAPS.

 

[kevs12]

just tried nuke from the menu, and I always get in IMAP
"Microsoft Entourage got an error: Apple Event timed out"

Testing in a new User will quickly tell you if the problem is system wide or
if it�s your User�s folder that contains the problem.

Go to System Preferences --> Create a New User in Accounts. Switch to the
New User by logging out/in or use Fast User Switching.

Move some scripts to the Shared folder for testing along with a few
messages.

In the new User, drag the test files to the desktop for access.
[/QUOTE]

 

[Diane Ross]

Diane, I just checked on my laptap which is, of course, a different user, and
the scripts do not work with Entourage with imap. what can i do?

This is strange. I still think you should try in a new User. It's possible
the same thing is keeping it from running on both systems if you have them
set up the same.

 

[kevs12]

Diane, so I spend 1/2 loading up scripts in new user and then works, then what?
I not gong to redo my user.
Huge hassle no?
what's procedure?
Take scripts and put them in new user? something like that?

 

[kevs12]

Always suspicious the the:

try new user.
Delete preferences...

 

[Diane Ross]

Always suspicious the the:

try new user.
Delete preferences...

This doesn't make a lot of sense. I've given you my best advice and if you
don't want to take it, you can't expect us to solve your problems for you.

 

[kevs12]

Diane, you are not just saying create new identity, but do new user on computer?

 

[Diane Ross]

Diane, you are not just saying create new identity, but do new user on
computer?

Yes. Go to System Preferences --> Create a New User in Accounts. Switch to
the New User by logging out/in or use Fast User Switching.

It's a totally clean environment to test. No login items, corrupt
preferences, caches.

If you need items to test, move them to Shared folder for access in the new
User.

 

[kevs12]

Diane,
spent 1/2 hour on this today.
Have test user, got my idtenity in shared and MUD of test, then when switch to it, says,
"Entourage cannot access database, please rebuild database"
Go to rebuild and then says, "cannot... error 5000"

 

[Diane Ross]

Have test user, got my idtenity in shared and MUD of test, then when switch to
it, says,
"Entourage cannot access database, please rebuild database"
Go to rebuild and then says, "cannot... error 5000"

Error 5000

Access Permission Denied

If you're receiving this error, it could be due to incorrect permission
settings for files within the Office folder.