|
Greetings! Welcome to Vol. 9, No. 19, Nov 24, 2004, of Exchange
Messaging Outlook, a biweekly newsletter about Microsoft Exchange
and Microsoft Outlook.
Today's highlights:
Regular features:
- New utilities
- Updated utilities
- Other Resources
USING AFTER SENDING RULES
Outlook's Rules Wizard has a neat but often overlooked option you
can use to act on messages after they are sent - the ability to
create a 'check message after sending' rule. These rules run as the
message leaves your Outbox and provide a variety of options.
Do you have a small mailbox and don't want to save large
messages? Create a rule that copies all messages to a folder (it can
be the sent folder) and create an exception for 'except with a size
in a specific range' then disable saving copies of messages in the
Sent Items folder in Tools, Options, Preferences,
Email Options.
Do you want to save sent messages to different folders based on the
recipient, the account, or the subject? Create a different rule for
each folder. Note that if you use a 'when they arrive rule' to
filter messages to folders, Outlook has the ability to save replies
in the folder with the original, except when the message is in the
Inbox. Enable this option in Tools, Options, Preferences,
Email
Options, Advanced Email options.
Because the after sending rules copy, not move, the messages, you
either need to disable saving copies of sent items (Tools, Options,
Preferences, Email Options and remove the checkmark from
Save copies
of messages in Sent Items folder) or delete the contents of the sent
folder on a regular basis. Open the Sent Items folder and select all
messages (Ctrl+A) then press Del or set up AutoArchive to delete
older sent messages regularly. To delete messages based on specific
criteria, create a 'when they arrive' rule and use "Run Now" to run
it on the Sent Items folder to delete the messages meeting your
criteria.
STORING SENT ITEMS ON AN IMAP SERVER
As anyone who has ever used Outlook with an IMAP account knows,
Outlook doesn't handle IMAP accounts well. The most irritating issue
for most people is how it saves sent messages in the local message
store instead of in the Sent folder on the IMAP server. You can use
Rules to copy the sent message to the IMAP Sent folder, but you'll
still have a copy of the item in the local folder unless you turn
off the option to Save copies of messages in Sent Items folder. Keep
in mind that if Outlook is unable to connect to the IMAP server for
whatever reason, a copy of the sent message isn't saved at all. If
you have two or more email accounts and disable saving sent items,
you'll need to create rules for each of the accounts if you want to
save the messages sent on each account.
To set up the rule:
- Go to Tools, Rules and Alerts (or Rules Wizard)
- Create a new blank rule
- Select Check messages after sending
- Select a condition if you want to only copy certain items to the IMAP folder or leave it blank to copy every item you send. Click
Next.
- Choose Move a copy the selected folder as the action and select
the Sent folder on your IMAP server. Click Next.
- Set up any exceptions and click Finish.
Now all messages (or those meeting the conditions you selected) you
send are copied to the IMAP server.
If you don't want a copy of the sent messages stored locally, open
Tools, Options, Preferences, Email Options and remove the check from
Save copies of messages in Sent Items folder. If you have more than
one account, you can create a rule for each account.
A KB article details this method using the condition of 'messages
using the Message form' so that it applies only to messages, not
task or meeting requests. Although it's written for Outlook 98
Internet Mail only mode, it works will all versions of Outlook.
OL98: (IMO) How to Save Sent Items on an IMAP Server (198852)
TECH TIP: MOVE TRANSACTION LOGS THE RIGHT WAY IN EXCHANGE
Contributed by
TechRepublicIn a perfect world, your systems perform a great backup every night,
and you've sized your transaction log drive space adequately so you
never run low on space. In the real world, however, things are
rarely perfect.
Tape backups fail, and server requirements can change faster than
your hardware budget allows. In the real world, you might find that
you need to move your transaction logs--and fast.
You could free up disk space temporarily by copying some of the
older logs to a separate drive. This could work, at least for a
while, and you don't have to shut down the information store to do
it.
However, the problem with this approach becomes apparent if you need
to do a restore. The log files are no longer where the system
expects them to be, and therefore the system can't perform the
restore.
You can hopefully move all of the transaction logs to a drive with
enough space to complete the restore. Otherwise, you're stuck with a
point-in-time restore, and your transaction logs are useless anyway.
Whenever possible, we recommend moving your transaction logs using
the tools provided by Exchange. It's the safest, surest way to move
the logs.
You can move Exchange 5.5 transaction logs (and databases) using the
Performance Wizard; Exchange 2000 and Exchange 2003 use the Exchange
System Manager to change the paths of files. While using these tools
may take a little longer and cause a brief amount of downtime up
front, the alternative--possible data loss--is far less desirable.
For more Exchange configuration and troubleshooting tips,
check out TechRepublic's proven line of books, CDs and laminated
charts. You'll find Exchange-specific solutions in
TechRepublic's Tech Tips for Exchange Administrators, Second Edition
TELL US ABOUT YOUR FAVORITE OUTLOOK OR EXCHANGE UTILITYWould you like to share your opinion of an Outlook or Exchange
utility with other users? We're looking for short reviews of
approximately 50 - 100 words to publish on slipstick.com. Send the
review by email to
favoritetools@slipstick.comm, with 'My favorite
Outlook or Exchange tool' in the subject line. NEW EXCHANGE KB ARTICLES 16 NOV 2004
The conferencing
server stops responding to client requests, and event ID 12288 is
logged on an Exchange 2000 Conferencing Server computer
(885467)
The Microsoft
EDK 5.5 is not supported with versions of Microsoft Exchange Server
later than 5.5
(8153655)
The Microsoft
Exchange Information Store service quits after a version conflict is
detected in a public folder post in Exchange Server 2003
(884547)
How to
re-create the Exchange-related virtual directories in Internet
Information Services 6
(888033)
How to
troubleshoot the Recipient Update Service by using the Application
log in Exchange 2000 Server or in Exchange Server 2003
(822794)
Redirection
history is not included with the original recipient name on ORAR
rerouting in Exchange Server 2003
(883938)
Message
originator may receive an NDR when a message is forwarded to a valid
alternative recipient in Exchange Server 2003
(8839499)
Description
of updates for problems with forwarded messages in DMS-enabled
Exchange Server 2003 organizations
(8894633)
HTML e-mail
messages lose their formatting when you use the Exchange Mailbox
Merge program to migrate .pst files to Exchange Server 2003
mailboxes
(8848499)
You receive a
"5.2.1" non-delivery report when you send an e-mail message to a
public folder on Exchange Server 2003 or on Exchange 2000 Server
(870585)
When you use
the Outlook Web Access client to open a compressed (.zip) file
attachment that you downloaded from an Exchange Server 2003
computer, the file is corrupted
(875525)
The message class of a freedoc that is forwarded by a public folder rule changes from IPM.Document to IPM.Note in Exchange Server 2003
(8868066) You cannot modify an embedded e-mail message that was forwarded as an attachment by a server-side rule in Exchange 2000 Server (885903)
The Message Transfer Agent service continues to accept messages after the hard disk that contains the MTADATA folder fails in Exchange Server 5.5 (8391388)
How to run multiple instances of the Migration Wizard in Microsoft Exchange Server 2003
(883408) "OxC007007e, drviis.dll won't register" error message when you install Exchange 2000 Server
(888177) An Exchange Server 2003 recipient may receive a non-delivery report or an e-mail message that is not formatted correctly
(885419)
NEW OUTLOOK KB ARTICLES - NOV 16, 2004
Your changes to the registry values for the Safe Senders list do not appear in the Safe Senders list in Outlook 2002 and in Outlook 2003 (889692)
The primary store changes when you add an Exchange account to an e-mail profile with a Hotmail or an MSN account as the primary store
(889693) The location of the Outlook Connector for MSN status bar changes when you restart Outlook (889699)
Description of the Outlook 2003 Junk E-mail Filter update: November 9, 2004 (873362)
How to deploy customized Outlook 2003 security settings to client computers by using the "Outlook virus security settings" Group Policy setting (885682)
You cannot rename default folders by using the Outlook 2003 object model (831363) |