powermail-discuss Digest #2938 - Friday, January 9, 2009
Re(2): 6.0 Crashing
by "Alan Harper" <[email protected]>
Re: Long delay after clicking "send message"
by "Alan Harper" <[email protected]>
Re: 6.0 Crashing
by "Michael J. Hußmann" <[email protected]>
Re(2): 6.0 Crashing
by "Bill Schjelderup" <[email protected]>
PM6 clippings and URL behaviors changed?
by "Tom Bulat" <[email protected]>
Re: PM6 clippings and URL behaviors changed?
by "Michael J. Hußmann" <[email protected]>
Re: PM6 clippings and URL behaviors changed?
by "C. A. Niemiec" <[email protected]>
Re(2): PM6 clippings and URL behaviors changed?
by "Tom Bulat" <[email protected]>
Re: PM6 clippings and URL behaviors changed?
by "Michael J. Hußmann" <[email protected]>
Re: Long delay after clicking "send message"
by "PowerMail Engineering" <[email protected]>
Re(2): PM6 clippings and URL behaviors changed?
by "Tom Bulat" <[email protected]>
Re: Long delay after clicking "send message"
by "PowerMail Engineering" <[email protected]>
----------------------------------------------------------------------
Subject: Re(2): 6.0 Crashing
From: "Alan Harper" <[email protected]>
Date: Thu, 8 Jan 2009 14:36:10 -0800
Matthias--could you explain in more detail? I use Pathfinder too. Does
it cause this problem, or fix this problem? Which version of StuffIt do
you suspect?
A
Matthias Schmidt ([email protected]) said on 1/8/09:
>Hello,
>looks like the crashes are connected to the installed stuff it engine.
>Long time ago I had a simular problem.
>Meanwhile I use Pathfinder, which installs always the last engine and I
>also bought stuff it.
>all the best
>Matthias
>
>Am/On Wed, 7 Jan 2009 11:43:47 -0800 schrieb/wrote Alan Harper:
>
>>Well, PM support asked me to send crash logs, which I did regularly, but
>>I never heard anything from them. I inquired whether they wanted me to
>>continue, and didn't hear anything, so I stopped.
>>
>>Your symptoms are identical to mine.
>>
>>A
>>
>>Bill Schjelderup ([email protected]) said on 1/7/09:
>>
>>
>>>Alan,
>>>
>>>I've been having these for a long time also.
>>>
>>>Higher frequency with v5 than v6, but still the same problem.
>>>
>>>I've sent many crash logs to ctmdev, but I have no idea if they have
>>>helped or not.
>>>
>>>The vast majority of these seem to occur when I'm performing a drag
>>>event and a message is received; other times when PM is trying to image
>>>a HTML email and some background operation occurs.
>>>
>>>My theory is it's a threading problem...and clearly it's hard for them
>>>to find.
>>>
>>>Perhaps if we ALL send crash logs it will help....
>>>
>>>(about 50% of the time a relaunch is quick, the other 50% it needs to
>>>rebuild sort indexes...)
>>>
>>>Oh, and this occurs on both my home and office machine (I carry my PM
>>>database between offices via an external hard disk..)
>>>
>>>+-------------------------------------------+
>>> Bill Schjelderup -- [email protected]
>>>+-------------------------------------------+
>>>>Hi
>>>>
>>>>PM 6 is crashing on me a few times a week. I can't discover any pattern
>>>>to the crashes, but they are usually (> 50%) followed by a 6-minute
>>>>reindexing when I relaunch PM. It makes it difficult to respond quickly
>>>>to emails!
>>>>
>>>>Has anyone else found this? Any thoughts on how to minimize crashing?
>>>>
>>>>Alan
>>>>
>>>>PS, FWIW, I had similar problems with PM 5. I have since reinstalled my
>>>>entire system, and upgraded to PM 6. It appears that PM 6 crashes less
>>>>often than 5, but not significantly so.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>Thanks and all the best
>
>Matthias
>
>
----------------------------------------------------------------------
Subject: Re: Long delay after clicking "send message"
From: "Alan Harper" <[email protected]>
Date: Thu, 8 Jan 2009 14:55:33 -0800
When my computer locks up like that, it is almost always because the
network is trying to find something that isn't available, like an alias
to a volume that is not on-line.
My first suggestion would be to create a new user account on this
computer, set up PM on that new account (be careful that this new
account does NOT delete mail from server!), and see the delay goes away.
If it does, search through your preferences, or throw out your
preferences and start over.
Best I can think of....
A
Stéphane Terreaux ([email protected]) said on 1/7/09:
>[Third time I send the message, it seems the two firsts were
>unsuccessfull, maybe because I attached a sampling file. I apologize if
>you received it twice.]
>
>Hi everybody,
>
>my best wishes to all for a colourfull and joyfull year !
>
>I notice a small problem with PM6, which I have never seen before.
>When a new mail is ready and I click on the "Send" stamp button, I have
>to wait a long time before the new msg window closes and I can work with
>PM. A "long time" means, more or less, 2 minutes.
>
>At the beginning, I thought this delay was related to the message size
>and attached file size, but in fact it seems not.
>
>In the meantime, PM shows me the rotating coloured wheel. The Activity
>monitor tells me that PM is not responding (displayed in red), with 0
>CPU consumption. It looks like PM is waiting for something...
>
>My message database is only around 100 Mo big. Not that fat. Freshly
>compacted, same problem. Rebuild the search index (through the menu), no
>change (it looks like the command did nothing). When I try to compact
>the search index (through the menu), PM crashes.
>
>I have compacted again and rebuilt the indexes through the maintenance
>dialog, no change. I have not tried the low level database rebuild.
>
>below is a sampling of PM, obtained with the Activity monitor during the
>"no response" time. I can't read it but maybe it can help.
>
>Does anyone have the same problem, or did anyone find a way to end with
that ?
>
>Thanks in advance,
>
>Stéphane.
>
>Analysis of sampling pid 4053 every 10.000000 milliseconds
>Call graph:
> 300 Thread_0f07
> 300 start
> 300 start
> 300 start
> 300 LApplication::Run()
> 300 start
> 300 LTSMDocApp::ProcessNextEvent()
> 300 WaitNextEvent
> 300 WNEInternal
> 300 GetNextEventMatchingMask
> 300 GetOrPeekEvent
> 300 ToolboxEventDispatcher
> 300 SendEventToEventTarget
> 300 SendEventToEventTargetInternal
>(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*)
> 300 DispatchEventToHandlers
>(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*)
> 300 ToolboxEventDispatcherHandler
>(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)
> 300 SendEventToEventTarget
> 300 SendEventToEventTargetInternal
>(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*)
> 300 DispatchEventToHandlers
>(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*)
> 300 StandardWindowEventHandler
> 300 HandleMouseEvent
> 300 HandleWindowClick
> 300 SendEventFromMouseDown
> 300 SendEventToEventTarget
> 300
>SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
>HandlerCallRec*)
> 300
>DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*)
> 300
>StandardWindowEventHandler
> 300
>HandleWindowEvent
> 300
>HandleClickAsHIView
> 300
>HIView::Click(OpaqueEventRef*)
> 300
>SendEventToEventTarget
> 300
>SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
>HandlerCallRec*)
> 300
>DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*)
>
>300 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)
>
>300 HIView::ClickSelf(OpaqueEventRef*)
>
> 300 HIView::ClickInternal(CGPoint
>const&, unsigned long, void (*)(OpaqueControlRef*, short),
>OpaqueEventRef*, bool)
>
> 300 HIView::NotifyControlHit
>(short, unsigned long)
>
> 300 SendControlHit(HIView*,
>short, unsigned long)
>
> 300 SendEventToEventTarget
>
> 300
>SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*,
>HandlerCallRec*)
>
> 300
>DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*)
>
> 300
>LHIToolbarItem::StaticCustomToolbarItemDelegate
>(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)
>
> 300
>LHIToolbarItem::CustomToolbarItemDelegate(OpaqueEventHandlerCallRef*,
>OpaqueEventRef*)
>
> 300
>LHIToolbarItem::PerformAction(short)
>
> 300
>LCommander::ProcessCommand(long, void*)
>
> 300 start
>
> 300
>CSpellCheckingWaste::ObeyCommand(long, void*)
>
> 300
>WTextView::ObeyCommand(long, void*)
>
> 300
>LCommander::ObeyCommand(long, void*)
>
> 300
>LCommander::ProcessCommand(long, void*)
>
> 300 start
>
>
300 start
>
>
>300 start
>
>
>300 VKOpaqueCall
>
>
> 300 RVLookerNew
>
>
> 300 RVLookerNew
>
>
> 300 start
>
>
> 300 CMAS::SmtpQueueMsg
>(CDatabase::IDType)
>
>
> 300 CSMTPEngine::QueueMsg
>(CDatabase::IDType)
>
>
> 300
>CSMTPEngine::CBuilderQueue::QueueMsg(CDatabase::IDType)
>
>
> 300
>CMsgFilteringEngine::DoFilterMsg(CMsg*,
>CMsgFilteringEngine::madeActionStruct*, bool,
>std::vector<CFilter::FilterLog, std::allocator<CFilter::FilterLog> >*, bool)
>
>
> 300
>CMsgFilteringEngine::DoFilterMsg(CFilter&, CMsg*, bool*,
>CMsgFilteringEngine::madeActionStruct*, CFilter::FilterLog*)
>
>
> 300
>CMsgFilteringEngine::DoAction(CFilter::CAction const&, CMsg*,
>CMsgFilteringEngine::MatchingCriteria&,
>CMsgFilteringEngine::madeActionStruct*)
>
>
> 300 start
>
>
> 300
>LPeriodical::DevoteTimeToRepeaters(EventRecord const&)
>
>
> 300
>URun1Script::SpendTime(EventRecord const&)
>
>
> 300 OSAExecute
>
>
> 300
>CallComponentDispatch
>
>
> 300
>AGenericManager::HandleOSACall(ComponentParameters*)
>
>
> 300
>AppleScriptComponent
>
>
>
>300 CallComponentFunction
>
>
>
>300 CallComponentFunctionCommon
>
>
>
> 300 ASExecute(unsigned long,
>unsigned long, long, unsigned long*)
>
>
>
> 300 UASExecute(unsigned char)
>
>
>
> 300 UASExecute1()
>
>
>
> 300 BCMessageSend()
>
>
>
> 300 UASSend(unsigned char,
>TUASSendMode)
>
>
>
> 300 UASSend1(unsigned
>char, unsigned char, unsigned char, TUASSendMode)
>
>
>
> 300 UASRemoteSend
>(unsigned char, unsigned char, unsigned char, unsigned char, unsigned
>char, unsigned char*)
>
>
>
> 300
>TUASApplication::Send(TStackFrame_UASRemoteSend*, AEDesc*, AEDesc*,
>unsigned char, unsigned char, unsigned char)
>
>
>
> 300 ComponentSend
>(AEDesc const*, AEDesc*, long, long)
>
>
>
> 300 InvokeOSASendUPP
>
>
>
> 300
>AEDefaultSendProc(AEDesc const*, AEDesc*, long, short, long, unsigned
>char (*)(EventRecord*, long*, OpaqueRgnHandle**), unsigned char (*)
>(EventRecord*, long, long, AEDesc const*), long)
>
>
>
> 300 AESend
>
>
>
> 300 aeSend
>
>
>
> 300
>AESendMessage
>
>
>
> 300
>CFRunLoopRunInMode
>
>
>
> 300
>CFRunLoopRunSpecific
>
>
>
> 300
>mach_msg_trap
>
>
>
>
>300 mach_msg_trap
> 300 Thread_1003
> 300 _pthread_body
> 300 __ape_agent
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1103
> 300 _pthread_body
> 300 ah_serv_loop
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1203
> 300 _pthread_body
> 300 CooperativeThread
> 300 LThread::DoEntry(void*)
> 300 LThread::Cleanup::Run()
> 300 LSemaphore::Wait(long)
> 300 LThread::SemWait(LSemaphore*, long, QHdr&, unsigned
char&)
> 300 SetThreadStateEndCritical
> 300 SetThreadState
> 300 YieldToThread
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1303
> 300 _pthread_body
> 300 CarbonSelectThreadFunc
> 300 syscall
> 300 syscall
> 300 Thread_1403
> 300 _pthread_body
> 300 CarbonOperationThreadFunc
> 300 semaphore_wait_signal_trap
> 300 semaphore_wait_signal_trap
> 300 Thread_1503
> 300 _pthread_body
> 300 CarbonATOperThreadFunc
> 300 semaphore_wait_signal_trap
> 300 semaphore_wait_signal_trap
> 300 Thread_1603
> 300 _pthread_body
> 300 forkThreadForFunction
> 300 +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:]
> 300 CFRunLoopRunInMode
> 300 CFRunLoopRunSpecific
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1703
> 300 _pthread_body
> 300 select
> 300 select
> 300 Thread_1803
> 300 _pthread_body
> 300 forkThreadForFunction
> 300 +[NSURLCache _diskCacheSyncLoop:]
> 300 CFRunLoopRunInMode
> 300 CFRunLoopRunSpecific
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1903
> 300 _pthread_body
> 300 CooperativeThread
> 300 LThread::DoEntry(void*)
> 300 start
> 300 start
> 300 CSemaphore::Wait(CMutex&)
> 300 CConditionImp::Wait(CMutex*)
> 300 CThreadImp::SuspendPPThread(CPPThread*)
> 300 LThread::Suspend()
> 300 SetThreadStateEndCritical
> 300 SetThreadState
> 300 YieldToThread
> 300 mach_msg_trap
> 300 mach_msg_trap
> 300 Thread_1a03
> 300 _pthread_body
> 300 CarbonInetOperThreadFunc
> 300 semaphore_wait_signal_trap
> 300 semaphore_wait_signal_trap
>
>Total number in stack (recursive counted multiple, when >=5):
> 12 start
> 11 _pthread_body
> 7 mach_msg_trap
> 5 DispatchEventToHandlers(EventTargetRec*,
>OpaqueEventRef*, HandlerCallRec*)
> 5 SendEventToEventTarget
> 5 SendEventToEventTargetInternal(OpaqueEventRef*,
>OpaqueEventTargetRef*, HandlerCallRec*)
>
>Sort by top of stack, same collapsed (when >= 5):
> mach_msg_trap 2100
> semaphore_wait_signal_trap 900
> select 300
> syscall 300
>Sample analysis of process 4053 written to file /dev/stdout
>Sampling process 4053 each 10 msecs 300 times
>
>
>
----------------------------------------------------------------------
Subject: Re: 6.0 Crashing
From: "Michael J. Hußmann" <[email protected]>
Date: Fri, 9 Jan 2009 00:09:45 +0100
Alan Harper ([email protected]) wrote:
> Matthias--could you explain in more detail? I use Pathfinder too. Does
> it cause this problem, or fix this problem? Which version of StuffIt do
> you suspect?
And btw, does PM really rely on StuffIt? After all, it doesn't support
creating StuffIt archives anymore. (I still have some version of StuffIt
installed, but I have stopped using it a long time ago.)
- Michael
Michael J. Hußmann
E-mail: [email protected]
WWW (personal): http://michael-hussmann.de
WWW (professional): http://digicam-experts.de
----------------------------------------------------------------------
Subject: Re(2): 6.0 Crashing
From: "Bill Schjelderup" <[email protected]>
Date: Thu, 8 Jan 2009 18:43:04 -0700
Matthias,
I wish it was this easy.
All I found on my boot volume were some old stuffit plist files which I
trashed. I don't use Stuffit any more and couldn't find any files with
"stuffit" in the name to delete. Looked on the root Library folder, and
my user Library folder.
Is there a particular file you suspect that doesn't have "stuffit" in
the name?
+-----------------------------------------------------------+
Bill Schjelderup, President [email protected]
COMPanion Corporation 801-365-0555 voice
1831 Fort Union Blvd. 801-943-7752 fax
Salt Lake City, Utah 84121-3041 www.companioncorp.com
+-----------------------------------------------------------+
Nusquam est qui ubique est. - He who is everywhere is nowhere.
This email message is for the sole use of the intended recipient(s) and
may contain confidential and privileged information. Any unauthorized
review, use, disclosure, or distribution is prohibited. If you are NOT
the intended recipient, I'm sorry to bother you and will attempt to
address my messages more carefully in the future.
>Hello,
>looks like the crashes are connected to the installed stuff it engine.
>Long time ago I had a simular problem.
>Meanwhile I use Pathfinder, which installs always the last engine and I
>also bought stuff it.
>all the best
>Matthias
>
>Am/On Wed, 7 Jan 2009 11:43:47 -0800 schrieb/wrote Alan Harper:
>
>>Well, PM support asked me to send crash logs, which I did regularly, but
>>I never heard anything from them. I inquired whether they wanted me to
>>continue, and didn't hear anything, so I stopped.
>>
>>Your symptoms are identical to mine.
>>
>>A
>>
>>Bill Schjelderup ([email protected]) said on 1/7/09:
>>
>>
>>>Alan,
>>>
>>>I've been having these for a long time also.
>>>
>>>Higher frequency with v5 than v6, but still the same problem.
>>>
>>>I've sent many crash logs to ctmdev, but I have no idea if they have
>>>helped or not.
>>>
>>>The vast majority of these seem to occur when I'm performing a drag
>>>event and a message is received; other times when PM is trying to image
>>>a HTML email and some background operation occurs.
>>>
>>>My theory is it's a threading problem...and clearly it's hard for them
>>>to find.
>>>
>>>Perhaps if we ALL send crash logs it will help....
>>>
>>>(about 50% of the time a relaunch is quick, the other 50% it needs to
>>>rebuild sort indexes...)
>>>
>>>Oh, and this occurs on both my home and office machine (I carry my PM
>>>database between offices via an external hard disk..)
>>>
>>>+-------------------------------------------+
>>> Bill Schjelderup -- [email protected]
>>>+-------------------------------------------+
>>>>Hi
>>>>
>>>>PM 6 is crashing on me a few times a week. I can't discover any pattern
>>>>to the crashes, but they are usually (> 50%) followed by a 6-minute
>>>>reindexing when I relaunch PM. It makes it difficult to respond quickly
>>>>to emails!
>>>>
>>>>Has anyone else found this? Any thoughts on how to minimize crashing?
>>>>
>>>>Alan
>>>>
>>>>PS, FWIW, I had similar problems with PM 5. I have since reinstalled my
>>>>entire system, and upgraded to PM 6. It appears that PM 6 crashes less
>>>>often than 5, but not significantly so.
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>Thanks and all the best
>
>Matthias
>
>
>
----------------------------------------------------------------------
Subject: PM6 clippings and URL behaviors changed?
From: "Tom Bulat" <[email protected]>
Date: Fri, 9 Jan 2009 09:42:38 -0500
Hi,
I'm now using PM6 and I went to drag a URL into my e-mail and instead of
being entered into my text document it becomes an attachment, same thing
happens with clippings.
This is wrong. Why is this happening.
I do not like this new behavior.
Also, I used to be able to select text and drag and drop it from Subject
lines, and now that isn't do-able anymore either.
Any help would be appreciated to get it working "correctly" as in the past.
Thanks, and so long for now, TOM
----------------------------------------------------------------------
Subject: Re: PM6 clippings and URL behaviors changed?
From: "Michael J. Hußmann" <[email protected]>
Date: Fri, 9 Jan 2009 16:29:54 +0100
Tom Bulat ([email protected]) wrote:
> I'm now using PM6 and I went to drag a URL into my e-mail and instead of
> being entered into my text document it becomes an attachment, same thing
> happens with clippings.
I can confirm that text clippings get added as attachments (not sure it
worked before). URLs dragged from Safari, Firefox, or a text editor, on
the other hand, are inserted as text enclosed within "<>" into the body
text, just as it should be.
> Also, I used to be able to select text and drag and drop it from Subject
> lines, and now that isn't do-able anymore either.
I have no idea whether it used to work before (I prefer copy&paste to
drag&drop myself), but indeed it doesn't work with the current version.
- Michael
Michael J. Hußmann
E-mail: [email protected]
WWW (personal): http://michael-hussmann.de
WWW (professional): http://digicam-experts.de
----------------------------------------------------------------------
Subject: Re: PM6 clippings and URL behaviors changed?
From: "C. A. Niemiec" <[email protected]>
Date: Fri, 9 Jan 2009 10:23:48 -0500
>I'm now using PM6 and I went to drag a URL into my e-mail and instead of
>being entered into my text document it becomes an attachment, same thing
>happens with clippings.
>
>This is wrong.
I can confirm this. I thought it was a fluke when it happened the other
day, but I guess not after deliberately playing with it.
Do change this back!
Chris
--
PowerMail 6 v4587, Tiger 10.4.11 both PCC and Intel
----------------------------------------------------------------------
Subject: Re(2): PM6 clippings and URL behaviors changed?
From: "Tom Bulat" <[email protected]>
Date: Fri, 9 Jan 2009 10:57:17 -0500
Hi Michael,
I tried again to drag a safari URL from the Finder desktop into my e-
mail and it comes in as an attachment!
I sure hope this gets changed.
What is up with all these changes for the worse?
So long for now, TOM
>Tom Bulat ([email protected]) wrote:
>
>> I'm now using PM6 and I went to drag a URL into my e-mail and instead of
>> being entered into my text document it becomes an attachment, same thing
>> happens with clippings.
>
>I can confirm that text clippings get added as attachments (not sure it
>worked before). URLs dragged from Safari, Firefox, or a text editor, on
>the other hand, are inserted as text enclosed within "<>" into the body
>text, just as it should be.
>
>> Also, I used to be able to select text and drag and drop it from Subject
>> lines, and now that isn't do-able anymore either.
>
>I have no idea whether it used to work before (I prefer copy&paste to
>drag&drop myself), but indeed it doesn't work with the current version.
----------------------------------------------------------------------
Subject: Re: PM6 clippings and URL behaviors changed?
From: "Michael J. Hußmann" <[email protected]>
Date: Fri, 9 Jan 2009 17:46:09 +0100
Tom Bulat ([email protected]) wrote:
> I tried again to drag a safari URL from the Finder desktop into my e-
> mail and it comes in as an attachment!
Ah, but then it's a clipping, not a URL per se! Try to drag from the
browser itself, i.e. a URL from a link on a web page, or from the
browser's URL field, and it will work as expected.
In other words, this issue amounts to the fact that clippings (of URLs,
text, or whatever) get treated as documents now and thus end up in the
attachments section, rather than in the body text. Arguably, this is a
bug, as clippings should be treated just like their contents if
possible, rather than as files (which, of course, they are).
- Michael
Michael J. Hußmann
E-mail: [email protected]
WWW (personal): http://michael-hussmann.de
WWW (professional): http://digicam-experts.de
----------------------------------------------------------------------
Subject: Re: Long delay after clicking "send message"
From: "PowerMail Engineering" <[email protected]>
Date: Fri, 9 Jan 2009 17:52:03 +0100
Stéphane Terreaux wrote:
>I notice a small problem with PM6, which I have never seen before.
>When a new mail is ready and I click on the "Send" stamp button, I have
>to wait a long time before the new msg window closes and I can work with
>PM. A "long time" means, more or less, 2 minutes.
Maybe you have an outgoing mail filter that executes an AppleScript that
tells another process to send an AppleEvent to PowerMail. Such situation
hangs PowerMail for exactly 2 minutes. Can you describe what your
AppleScript is doing?
Jérôme - CTM Engineering
---------------------------------------------------------------------
"I've been using Powermail for around 3 years now and find that it's
extremely stable. The interface is clear and intuitive and not cluttered
like other programs (Apple Mail and Eudora, e.g.). Filters work well,
and it does all that one would expect from an email client. The program
is robust and straightforward. It's a great application."
PowerMail user comment on www.versiontracker.com
Download a demo version from www.ctmdev.com
---------------------------------------------------------------------
----------------------------------------------------------------------
Subject: Re(2): PM6 clippings and URL behaviors changed?
From: "Tom Bulat" <[email protected]>
Date: Fri, 9 Jan 2009 11:54:32 -0500
>Arguably, this is a
>bug, as clippings should be treated just like their contents if
>possible, rather than as files (which, of course, they are).
Hi Michael,
I hope it is a bug that gets squashed soon!
I sent a report to CTM.
So long for now, TOM
----------------------------------------------------------------------
Subject: Re: Long delay after clicking "send message"
From: "PowerMail Engineering" <[email protected]>
Date: Fri, 9 Jan 2009 18:00:12 +0100
Stéphane Terreaux wrote:
>Rebuild the search index (through the menu), no
>change (it looks like the command did nothing).
The "File / Database / Update Search Index" menu does not rebuilds the
search index, it updates it, in case background indexing is disabled in
the preferences. To rebuild it, use the appropriate checkbox in the
First Aid dialog (by pressing the command and option keys while
PowerMail is launching).
>When I try to compact
>the search index (through the menu), PM crashes.
If compacting the search index crashes, you need to rebuild it (see above).
>I have compacted again and rebuilt the indexes through the maintenance
>dialog, no change. I have not tried the low level database rebuild.
No change for the hang when sending a message, which is not related to
the search index; but can you now compact the search index successfully
(from the "File / Database / Compact Search Index" menu)?
Jérôme - CTM Engineering
---------------------------------------------------------------------
"I would like to comment that FoxTrot is so far superior to Spotlight
in every way that without it, I would probably have to go back to
Windows (shudder) since the ability to search my own files is mission
critical."
Steven Merley, FoxTrot Personal Search user
Download a demo version from www.foxtrot.ch
---------------------------------------------------------------------
----------------------------------------------------------------------
End of powermail-discuss Digest
