Script Locations
PowerMail stores scripts in 2 locations. One contains the default (built- in scripts). The other contains your scripts. Your scripts appear in the PowerMail scripts menu under the gray Custom Scripts heading. They are stored here: ~/Mail/PowerMail Folder/Custom Scripts/ You can access this folder simply by selecting Open user's folder from the PowerMail scripts menu. The second location is inside the PowerMail program: PowerMail 5.1/PowerMail 5.1/Contents/MacOS/PowerMail Additions/PowerMail Scripts/ You can access this folder simply by selecting Open PowerMail Additions from the PowerMail scripts menu. Here you will find all the default scripts. The long list of default scripts confuses and delays me, especially since I use only 2 of them. So I remove those that I don't need. NOTE: I am not instructing you to do this. I am merely explaining what I do. Richard Hart
Re: Copying Body's Content
*This message was transferred with a trial version of CommuniGate(tm) Pro* ~/Mail/PowerMail Files/Custom Scripts/ -- Andy Fragen On Sat, Dec 11, 2004, Richard Hart said: Giovanni Andreani wrote: Another curious thing: where are PowerMail's Scripts stored? PowerMail scripts are stored in 2 locations. See my message Script Locations in another thread. Richard Hart
Re: Copying Body's Content
Giovanni Andreani wrote: Another curious thing: where are PowerMail's Scripts stored? PowerMail scripts are stored in 2 locations. See my message Script Locations in another thread. Richard Hart
Re: Copying Body's Content
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Here's one for TextEdit.
applescript
tell application PowerMail 5.1.1a1
set s to
set theMessages to current messages
repeat with msg in theMessages
set s to s content of msg
end repeat
tell application TextEdit
make new document at the beginning of documents with properties
{text:s}
end tell
end tell
/applescript
This is a minor variation from the script I use, but should copy all the
content into a single TextEdit document.
--
Andy Fragen
On Sat, Dec 11, 2004, cheshirekat said:
As someone else mentioned, BBEdit Lite doesn't support AppleScript. I
don't think the lite BBEdit versions have ever included scriptability in
the many versions I have tried prior to OS X. I haven't tried any OS X
versions since I haven't been interested in any text editors that
expensive. So, you could use other applications, like TextEdit
Re: Copying Body's Content
On Sat, Dec 11, 20043:13 PM, the following words from Giovanni Andreani
[EMAIL PROTECTED], emerged from a plethora of SPAM ...
...
I don't use BBEdit, but here's an example of getting all the selected
messages into one new PowerMail message with AppleScript, which you could
then select and copy to BBEdit:
Begin AppleScript
property ret : return
property rr : ret ret
property fromLead : From:
property dateLead : Date:
property subLead : Subject:
to sendTheTxt from the txt
tell application PowerMail 5.1
set the newMsg to make new message with properties {content:txt}
set the status of the newMsg to draft
open the newMsg
end tell
end sendTheTxt
tell application PowerMail 5.1
set the sumText to
set the msgList to the current messages
repeat with targetMsg in the msgList
set the targetMsg to (the first item of the msgList)
set the targetMsgSender to the targetMsg's sender
set the sName to the targetMsgSender's display name
set the sAddr to the targetMsgSender's email address
set the sentDate to the targetMsg's time sent as text
set the msgSub to the targetMsg's subject
set the msgBody to the targetMsg's content
set the sumText to (the sumText fromLead sName sAddr
ret dateLead sentDate ret subLead msgSub rr msgBody rr)
end repeat
sendTheTxt of me from the sumText
end tell
End AppleScript
HTH
cheshirekat
Thank you Cheshirekat
I've tried the above script, but the result is the same first message
copied so many times as the number of the total selected messages
Giovanni
Ok, sorry about that. I now see what was wrong. the repeat statement has
an extra line I was using for testing while removing extra stuff that I
have in my personal scripts. ( For some reason I've made the mistake of
leaving test pieces in several scripts I've been working on this week, so
I knew exactly what the problem was when you said the same message was
copied multiple times. The advantage of making your own scripts is that
no one sees the many mistakes you make. When I share scripts I've
created, I try to remove commented lines, extras that may not be
applicable for general use, and error-checking snippets, but sometimes
make errors in the cleanup.) Remove this offending line:
set the targetMsg to (the first item of the msgList)
The script should look like this:
Begin AppleScript
property ret : return
property rr : ret ret
property fromLead : From:
property dateLead : Date:
property subLead : Subject:
to sendTheTxt from the txt
tell application PowerMail 5.1
set the newMsg to make new message with properties {content:txt}
set the status of the newMsg to draft
open the newMsg
end tell
end sendTheTxt
tell application PowerMail 5.1
set the sumText to
set the msgList to the current messages
repeat with targetMsg in the msgList
set the targetMsgSender to the targetMsg's sender
set the sName to the targetMsgSender's display name
set the sAddr to the targetMsgSender's email address
set the sentDate to the targetMsg's time sent as text
set the msgSub to the targetMsg's subject
set the msgBody to the targetMsg's content
set the sumText to (the sumText fromLead sName sAddr
ret dateLead sentDate ret subLead msgSub rr msgBody rr)
end repeat
sendTheTxt of me from the sumText
end tell
End AppleScript
As someone else mentioned, BBEdit Lite doesn't support AppleScript. I
don't think the lite BBEdit versions have ever included scriptability in
the many versions I have tried prior to OS X. I haven't tried any OS X
versions since I haven't been interested in any text editors that
expensive. So, you could use other applications, like TextEdit,
AppleWorks, Microsoft Word, or whatever you are comfortable with to make
the script a little more automatic if they support AppleScript. I send
my messages to a FileMaker Pro database I created with AppleScripts, and
I also send messages to plain text files frequently.
HTH
cheshirekat
Re: No hard wrap of text
From what I've seen, PowerMail puts no breaks in incoming mail. I have some messages here and there that freeflow when the window is resized (plaintext, not HTML/etc.). You just contradicted yourself from yesterday: :-))) PowerMail inserts line breaks in outgoing mail automatically. It's been discussed a few times here. Something official was said by CTM about this (though I can't find it at the moment). See the following... For what it's worth, I agree with you this time. As I said in a post just prior to yours, the line breaks are enforced by the mail servers (and/or relays as others have pointed out). The person generating the email can do what he wants in his e-mail client's window but as long as he is sending plain text, his e-mail will be subject to whatever formatting the intervening hosts apply. No and yes. :) _Sometimes_ extra breaks will be added in the transfer process. PowerMail adds breaks to outgoing. It does not add breaks to incoming. But nothing prevents mail servers/relays from adding breaks. Apparently not all do as I've received some plain text messages that have lines longer than 78 characters. I guess they just used the right relays. Chris --
Re: No hard wrap of text
On Saturday, December 11, 2004, C. A. Niemiec sent forth: From what I've seen, PowerMail puts no breaks in incoming mail. I have some messages here and there that freeflow when the window is resized (plaintext, not HTML/etc.). Chris -- You just contradicted yourself from yesterday: :-))) PowerMail inserts line breaks in outgoing mail automatically. It's been discussed a few times here. Something official was said by CTM about this (though I can't find it at the moment). See the following... Chris For what it's worth, I agree with you this time. As I said in a post just prior to yours, the line breaks are enforced by the mail servers (and/or relays as others have pointed out). The person generating the email can do what he wants in his e-mail client's window but as long as he is sending plain text, his e-mail will be subject to whatever formatting the intervening hosts apply. -- Tim Lapin [EMAIL PROTECTED]
Re: Copying Body's Content
I've tried the script above, but I can't get Bbedit to open a new window. I changed the syntax with tell application BBEdit Lite 6.1 for OS X I didn't think this was supported on the Lite version. Chris --
Re: No hard wrap of text
I ask for this: Make for sending mails the option-choice for - to break automaticaly at 78 character OR - free flow of characters And the same option-choice for incoming mails. From what I've seen, PowerMail puts no breaks in incoming mail. I have some messages here and there that freeflow when the window is resized (plaintext, not HTML/etc.). Chris --
Re: No hard wrap of text
This RFC dates from 2001 - which is a centenary in IT-time! As it is written, it's a more conservative recommendation. But in the meantime all of (serious) mail programs are able to handle it. A mail app can do as it wants, but the mail relays will do as they please as well. This is a case of what you see is not what they will necessarily get. And while the RFC is from 2001, it is the RFC and if folks don't adhere to it, then they can't complain when their way of doing things doesn't work. I ask for this: Make for sending mails the option-choice for - to break automaticaly at 78 character OR - free flow of characters And the same option-choice for incoming mails. Again, just because the mail app supports it doesn't mean the relays won't force their own line breaks on you. Then you end up with very messy text. I know at work our MS exchange server has the ability to remove extra line breaks, and it does all the time. Unfortunately, it also looks pretty bad sometimes when it does this. I would say, you're compromise isn't a bad one, but I'll argue that you'll still end up with mail recipients that complain about your strange line breaks (not that you put them in, but the mail relays did). Wayne -- Somebody's dead forever... - Somebody Got Murdered -- Joe Strummer (1952-2002) OP LoftBed Preferred Builder: http://www.wbwoodworks.com/ Wayne's Music Calendar: http://ical.mac.com/wayneb/Music PowerMail AppleScript Archives: http://www.ctmdev.com/tools/ Music Currently playing:
Re: Copying Body's Content
...
I don't use BBEdit, but here's an example of getting all the selected
messages into one new PowerMail message with AppleScript, which you could
then select and copy to BBEdit:
Begin AppleScript
property ret : return
property rr : ret ret
property fromLead : From:
property dateLead : Date:
property subLead : Subject:
to sendTheTxt from the txt
tell application PowerMail 5.1
set the newMsg to make new message with properties {content:txt}
set the status of the newMsg to draft
open the newMsg
end tell
end sendTheTxt
tell application PowerMail 5.1
set the sumText to
set the msgList to the current messages
repeat with targetMsg in the msgList
set the targetMsg to (the first item of the msgList)
set the targetMsgSender to the targetMsg's sender
set the sName to the targetMsgSender's display name
set the sAddr to the targetMsgSender's email address
set the sentDate to the targetMsg's time sent as text
set the msgSub to the targetMsg's subject
set the msgBody to the targetMsg's content
set the sumText to (the sumText fromLead sName sAddr
ret dateLead sentDate ret subLead msgSub rr msgBody rr)
end repeat
sendTheTxt of me from the sumText
end tell
End AppleScript
HTH
cheshirekat
Thank you Cheshirekat
I've tried the above script, but the result is the same first message
copied so many times as the number of the total selected messages
Giovanni
Re: Copying Body's Content
*This message was transferred with a trial version of CommuniGate(tm) Pro* Try this. applescript tell application PowerMail 5.1.1a1 set theMessages to current messages repeat with msg in theMessages --set s to source of msg set s to content of msg tell application BBEdit make new window set contents of front window to s end tell end repeat end tell /applescript If you select all the messages and run the script you will get a BBEdit window with each message's content. If you want to append the content together you should put all the content into s before the BBEdit part. -- Andy Fragen Thank you Andy, Cheshirekat, Ben and Marco First of all, the Answers to Cheshirekat: What do you mean by automatically? Just as a script would do: in a glimpse without no other intervention Do you want to select the folder, then activate the script to act on all messages in only that folder? Yes, and eventually only the selected messages in that folder Do you want to paste each message into a BBEdit document, or all the selected messages into one new BBEdit document, or all the messages into an already open BBEdit document? There are a lot of ways to accomplish what you want to do with AppleScripts All the selected messages into one new BBEdit document I've tried the script above, but I can't get Bbedit to open a new window. I changed the syntax with tell application BBEdit Lite 6.1 for OS X I've got a trial version of Bbedit which is expired, so it wont open. Am I doing anything wrong? Another curious thing: where are PowerMail's Scripts stored? Thank you all Giovanni
Re: Feature request: Spell check in Subject line
50 billion years ago the universe exploded into existence nothing much of importance has happened since then, until Fri, Dec 3, 2004 at 4: 02 PM, when Max proclaimed I find it somewhat annoying that Spell Checking doesn't check the subject line. if you're willing to buy commercial spellchecking software, try SpellCatcher: http://www.rainmakerinc.com/ I couldn't live without it. -- Jo €º°`°º€ø,??,ø€º°`°º€ø,??,ø€º°`°º€ø,??,ø€º°`°º€ø,? Dijon vu -- the same mustard as before
Re: No hard wrap of text
Where can I stop Powermail to hard wrap the text of my mails? I want Powermail to send my mails without hard line break. PowerMail inserts line breaks in outgoing mail automatically. It's been discussed a few times here. Something official was said by CTM about this (though I can't find it at the moment). See the following... Chris -- Post to list from Wayne Brissette (21 November 2003): Here is the story on line wraps. The Internet spec for mail (now RFC 2822 : http://www.faqs.org/rfcs/rfc2822.html), recommends 78 characters per line. Here is the direct quote: 2.1.1. Line Length Limits There are two limits that this standard places on the number of characters in a line. Each line of characters MUST be no more than 998 characters, and SHOULD be no more than 78 characters, excluding the CRLF. The 998 character limit is due to limitations in many implementations which send, receive, or store Internet Message Format messages that simply cannot handle more than 998 characters on a line. Receiving implementations would do well to handle an arbitrarily large number of characters in a line for robustness sake. However, there are so many implementations which (in compliance with the transport requirements of [RFC2821]) do not accept messages containing more than 1000 character including the CR and LF per line, it is important for implementations not to create such messages. The more conservative 78 character recommendation is to accommodate the many implementations of user interfaces that display these messages which may truncate, or disastrously wrap, the display of more than 78 characters per line, in spite of the fact that such implementations are non-conformant to the intent of this specification (and that of [RFC2821] if they actually cause information to be lost). Again, even though this limitation is put on messages, it is encumbant upon implementations which display messages to handle an arbitrarily large number of characters in a line (certainly at least up to the 998 character limit) for the sake of robustness. Now, there is even more to the story than this. The relays that a message go through (depending on the age of the equipment) may also put a hard wrap at 78 characters. So, when you send your 110 character text it may mean your text shows up on the other end looking very odd. There are ways that can avoid this such as sending the message as a MIME formatted message, but that means the message isn't pure text (which can be a good thing at times, although personally I'm more of a purest and like my mail as text). Anyhow, the bottom line is PowerMail takes the safest route and automatically places messages at 78 characters as it is sent out. It seems like a pain, but really it is the best route when dealing with email, since the lost of a single word can make a huge difference in how things interpreted. A quote from Mark Twain comes to mind -- The difference between the almost right word the right word is really a large matter--it's the difference between the lightning bug and the lightning. - Letter to George Bainton, 10/15/1888 Anyhow, I realize this isn't what you and some others want, but in the overall scheme of things it really is the safest method today.
