I think the problem for my script is that I can't get the unique
message ID with an incoming filter script.
I made a script to display the Message ID and attached it to an
Incoming Filter and it doesn't work. Go figure.
I am guessing that is why the "Tag Attachments" scripts might be flaky
(since it tries to set the Message ID also)
Here is the script:
<Snip>
tell application "PowerMail 5.2.3"
try
set theMessages to the current messages
repeat with msg in theMessages
set MessID to the ID of the msg
display dialog "The message ID is:" & MessID
end repeat
end try
end tell
</Snip>
Thanks again,
Justin
On Thursday, March 16, 2006, at 07:27 PM, Mikael Byström wrote:
> Olaf Drümmer said:
>
>> maybe it has to do with the fact the an incoming mail filter works on
>> the mail in an intermediate state (i.e. the mail has not been "fully"
>> received/saved yet), whereas manual operation/running all filters
>> processes the selected mail(s) after it/they has/have been "fully"
>> received/saved?
>
> When the script is run the message should have been fully retrieved,
> unless the account is set to not download messages above a certain size
> in full. There also could a bug in play, as Andy suggested, but in this
> case I think it could be circumvented at least. AFAIK there is no
> general
> problem running scripts on incoming attachments.
>
> PM 5.2.3 Swedish | OS X 10.3.9 | Powerbook G4/400Mhz | 1GB RAM | 30GB
> HD
>
>
>
>
