Advanced tips & tricks

V Snooze error notifications
V If a scheduled connection produces a connection error (because of a temporary network or server problem), you can be annoyed by an error notification being posted every few minutes. You can "snooze" this notification for a period of one hour:
* Right-click (or control-click) the PowerMail icon in the Dock, and select "Snooze last connection error" in the pop-up menu
* Or click the "Snooze" button in the notification dialog (if "Animate application icon while in the background" is selected in the Notifications preference pane)
* Or command-click (or option-click) the Growl notification popup window (if Growl is installed, and "Use Growl" is selected in the Notifications preference pane)
V Log notifications
V If Growl is installed, and "Use Growl" is selected in the Notifications preference pane, you can configure it to log all the notifications (valid for Growl 1.1.4):
* stop Growl from it's System Preferences pane
V type this command in Terminal.app:
* defaults write com.Growl.GrowlHelperApp GrowlLoggingEnabled -int 1
* start Growl from it's System Preferences pane
V With Mac OS X 10.5, to view Growl logs relative to PowerMail:
* in Console.app, create a new log database query (command-option-N)
* Query name: Growl PowerMail
* [Sender] [contains] GrowlHelperApp
* click "+"
* [Message] [contains] PowerMail: (
(note: there is two spaces between ":" and "(" )
V to stop logging, type this command in Terminal.app:
* defaults write com.Growl.GrowlHelperApp GrowlLoggingEnabled -int 0
V View threads
* The default behavior is to view threads by searching messages with the same subject; if you press the shift key, threads are searched by examining the "references", "in-reply-to" and "message-ID" header fields.
* Note that messages received with a PowerMail version older than 6.0.1b1 won't be found by examining the header fields, unless you have manually rebuilt the search index
* You can toggle the default to search by examining the header fields; see "Advanced hidden preferences"
V Advanced hidden preferences
V SMTP Authentication
* Some mail server have a bug that cause SMTP authentication to fail:
* These SMTP servers pretend to support the CRAM-MD5 authentication method, but they don't implement it correctly
V You can work around this server bug by typing the following command in Terminal.app:
* defaults write com.ctmdev.PowerMail "PreferCRAM-MD5" -bool NO
V To reset the normal behavior, type:
* defaults remove com.ctmdev.PowerMail "PreferCRAM-MD5"
V View threads by subject or by header
V The default behavior is to view threads by searching messages with the same subject (see "Tips and Tricks"). To toggle this behavior (search by default by header, and search by subject if shift key is pressed), type the following command in Terminal.app:
* defaults write com.ctmdev.PowerMail "SearchThreadsBySubject" -bool NO
V To reset the normal behavior, type:
* defaults remove com.ctmdev.PowerMail "SearchThreadsBySubject"
V Troubleshooting
V PowerMail refuses to send outgoing messages
V Your mail server may requires authentication for sending messages
* Verify that "authenticate as user" is checked, and that your username and password are valid, in the "Sending" tab of the "Mail Account" dialog (or in the "Locations" tab of the "Mail Schedulings and Locations" dialog, in case "Always use SMTP server" is checked in this dialog)
* Some mail server have a bug that cause SMTP authentication to fail. You can set PowerMail to work around this server bug, see "SMTP Authentication" in the "Advanced hidden preferences" section

site updated December 4th, 2017 - © 1985-2017 CTM Development SA - all rights reserved - General Terms and Conditions