MACSCRPT Archives

July 2006

MACSCRPT@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Apple Message framework v752.2)
Content-Type:
text/plain; charset=US-ASCII; delsp=yes; format=flowed
Date:
Mon, 3 Jul 2006 08:40:57 -0700
Reply-To:
Macintosh Scripting Systems <[log in to unmask]>
Subject:
From:
John Baxter <[log in to unmask]>
In-Reply-To:
Content-Transfer-Encoding:
7bit
Sender:
Macintosh Scripting Systems <[log in to unmask]>
Parts/Attachments:
text/plain (22 lines)
On Jul 2, 2006, at 6:36 AM, Duane Mitchell wrote:

> I have this idea that Mail.app started off as being intended to be  
> integrated with the .mac accounts and the iLife products rather  
> than just an email application.

Mail's origin was long ago at NeXT, before the acquisition.  And long  
before iLife.  (I don't know how it compares with the earliest .Mac).

It is quite possible that it knows about Apple events which are not  
exposed in the scripting dictionary (some of the iLife integration  
might suggest that).

Also, if one is writing general code, one needs to look at .Mac  
accounts, IMAP accounts (.Mac seems to be a special case of those,  
where Mail knows some of the settings), Exchange accountsm, and POP  
accounts.  At the moment, I'm primarily using .Mac and IMAP accounts  
with Mail.

   --John (who has never had an Exchange account and would like to  
keep it that way)

ATOM RSS1 RSS2