Re: Sending Email from AppleScript Without Garbling It
Re: Sending Email from AppleScript Without Garbling It
- Subject: Re: Sending Email from AppleScript Without Garbling It
- From: Paul Berkowitz <email@hidden>
- Date: Tue, 04 Jun 2002 09:34:25 -0700
I'd be extremely surprised Entourage it doesn't comply with every RFC that
exists. Really, if it doesn't, they will want to know about it and will
change. Write me off-list with more details and I'll pass them on, and let
you know what reply I get. They absolutely want to adhere to all RFC
standards, and are pretty meticulous about doing so, even when other email
apps don't. (They even take a "hard-line" interpretation about not allowing
messages with BCC recipients only - you can't do that in Entourage.)
In the meantime, you can work around this if you need to by parsing the
headers and message source, removing what you don't want, copying the rest
to a variable and making that the source of a new message, and deleting the
original. You do have to be careful: I have discovered a bug that Entourage
gives a false negative when searching for a search string in a longer
string if it is found beginning after character 1 and ending after character
255. There are ways of working around this bug. When searching with TIDs for
"Content-type: multipart/mixed;" you'd need to watch out for this.
--
Paul Berkowitz
>
From: "Simon Kornblith (Mailing Lists)" <email@hidden>
>
Date: Tue, 04 Jun 2002 07:33:00 -0400
>
To: Applescript-Users <email@hidden>
>
Subject: Re: Sending Email from AppleScript Without Garbling It
>
>
On 6/4/02 12:00 AM, "Paul Berkowitz" <email@hidden> wrote:
>
>
> Can you explain again why you can't send the message by scripting Entourage
>
> (example please)? Everything, including encoding, should be scriptable
>
> within Entourage.
>
>
Okay, this is a multipart MIME message. The headers have to contain the
>
following:
>
>
Content-type: multipart/encrypted; protocol="application/encrypted";
>
boundary="=--"
>
>
I have the AppleScript compile the message source, make a new outgoing
>
message with this source, and send it, but before the message is sent
>
Entourage adds its own headers. We end up with:
>
>
Content-type: multipart/encrypted; protocol="application/encrypted";
>
boundary="=--"
>
Content-type: multipart/mixed; boundary="B_3106020281_91382"
>
>
Not a good thing. It also adds its own boundaries. Entourage interprets it
>
fine, working by the first content type, but I'm pretty sure this doesn't
>
comply with RFC 3156 or the MIME RFC.
>
>
Simon
>
>
--
>
They that can give up essential liberty to obtain a little temporary safety
>
deserve neither liberty nor safety.
>
-- Benjamin Franklin, Letter to Josiah Quincy, Sept. 11, 1773.
>
>
Those who desire to give up freedom in order to gain security will not have,
>
nor do they deserve, either one.
>
-- President Thomas Jefferson
>
>
To those who scare peace-loving people with phantoms of lost liberty, my
>
message is this: your tactics only aid terrorists.
>
-- John Ashcroft
>
_______________________________________________
>
applescript-users mailing list | email@hidden
>
Help/Unsubscribe/Archives:
>
http://www.lists.apple.com/mailman/listinfo/applescript-users
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.