Yesterday I was being very frustrated by Outlook blocking access to attachments. So, I thought that this would be a good post for the new month. How to unblock attachments in Outlook 2007!
Allowing executable extensions give you more freedom but less security (I've seen viruses pass AVs before). I would recommend allowing unsafe attachments just for a specific email, and undoing it after downloading the attachments. Of course make sure the email is from a trusted source and still treat it as if it's a virus by default (i.e. scan it, look for patterns in the email body, etc).
I'm sure you've seen before "Outlook blocked access to the following potentially unsafe attachments: xxx.exe". I found there's very little documentation out there on how to lower the security level or allow a file a know source sent you. You'll find below the registry hack to allow specific file types Outlook blocks by default. There's also a kb article about it and as the article mentions make sure you backup your registry before you start editing it.
Run -> regedit and go to :
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security
1. Backup your registry first. Right click and select Export.
2. Add a new String Value called: Level1Remove
Level1Remove
1. Edit it and save the value data to the extension you wish to allow (add a semi-colon delimiter for multiple extensions).
Ex: .bat or .bat;.exe;.scr
1. Restart outlook (no need to restart your computer) !
Here is the KB for some further reading. http://support.microsoft.com/kb/829982
Enjoy your new freedom.
Showing posts with label Exchange - Outlook. Show all posts
Showing posts with label Exchange - Outlook. Show all posts
Friday, February 01, 2008
Tuesday, September 11, 2007
Directions on Exporting and Importing from Excel to Outlook
Importing an Excel List into Outlook Contacts
You only need to do this if you already have the email typed into an Excel Spreadsheet. If you have the addresses written down but haven't already typed them into something, go to my directions on how to add Contacts in Outlook and start there. If you have an Excel Spreadsheet set up, then read on.
- Right click on the Import Spreadsheet Template and choose Save Target As and save it somewhere on your hard drive.
- Open the spreadsheet that you have already created.
- Open the Import Spreadsheet Template that you just saved.
- Copy the column of names from your spreadsheet and paste them into the Import Spreadsheet Template. If you didn't separate the names in your spreadsheet into first and last columns, then just copy the one column and paste it into the LastName column.
- Copy the email addresses from your spreadsheet
- Paste them into the template in column BE (that's way over there!) If you have two email addresses for some students, the second address can be pasted into column BG on the template.
- Save the template spreadsheet.
- Then save it again following these directions.
- File
- Save as
- Click on Save as Type and choose Text (Tab delimited) (*.txt0
- Name it and save.
- Say yes to the message that pops up asking you about format
- Then close the spreadsheets. (It will ask you about saving again. You can say no.)
- Now you are ready to bring it into Outlook
- Open Outlook and click on Contacts. (You can set up a separate folder to keep the parent email from getting mixed in with the other.)
- Choose File
- Then Import and Export
- In the new window that opens, choose Import from another program or file
- Click Next
- Scroll all the way down to Tab Separated Values (Windows)
- Click Next
- Browse to find the .txt file where you saved it in step 8
- Click Next
- Select Contacts (or the folder in Contacts that you set up if you used a folder)
- Click Next
- Click the Map Custom Fields button
- When you see the new window scroll down to find EmailAddress under Value and scroll down the Field side to find E-mail and click on the + to expand
- If you don't see EmailAddress under Mapped from next to E-mail Address then drag it from the Value window to the Field window where it is in the window. Do this for E-mail, E-mail 2, and E-mail 3.
- Click OK
- Click Finish
- Now you should be able to go into your Contacts and find the new addresses.
Exporting a Contact List from Outlook
Once you have all the email addresses in your Contacts, you may want to share those with the other teachers on your team. Here is how you would do that.
- Open Outlook and go to Contacts
- Click File
- Select Import and Export
- Select Export to a file
- Click Next
- Scroll down to the bottom and choose Tab Separated Values (Windows)
- Click Next
- Select Contacts (or the contacts folder you want to export)
- Click Next
- Browse to find where you want to save the file and name it with a .txt extension
- Click Next
- Follow steps 21, 22, and 23 above.
- Click Finish
- Now you are ready to follow the Importing directions above on your team teacher's computer.
Monday, September 03, 2007
Putting a signature on your email
If you would like to add an autosignature to all of your email messages (like the one I have below) follow these simple steps:
· Open Outlook
· Choose Tools
· Then Options
· Select the Mail Format tab at the top of the window.
· Click the Signature Picker button at the bottom
· Choose New
· Next
· Type in the signature that you want to show up in your email
· Then Finish, OK and OK again.
You might want to send yourself an email as a practice run to see if it shows up and looks the way you want it to. You can always go back in and edit it.
· Open Outlook
· Choose Tools
· Then Options
· Select the Mail Format tab at the top of the window.
· Click the Signature Picker button at the bottom
· Choose New
· Next
· Type in the signature that you want to show up in your email
· Then Finish, OK and OK again.
You might want to send yourself an email as a practice run to see if it shows up and looks the way you want it to. You can always go back in and edit it.
Tuesday, August 28, 2007
Auto Accept Agent for Exchange
Here is a neat thing that you can implement for your resource mailboxes. This service will create an Auto Accept Agent on your Exchange Server. This service can send an email to your end user as a confirmation of the acceptance or denial of the booking of the resource.
Once you setup the Auto Except Service on your Exchange Server, here is the script that you will need to use in order to register your resource.
cscript RegisterMailbox.vbs {/m:mailbox@domain.com | /f:file.txt} [/t:domain\AgentAccountName] [/u] [/DEBUG]
Where:
/m
The primary SMTP address of the mailbox that you want to register. Use this switch when registering or unregistering a single mailbox.
/f
The name of the text file that contains the primary SMTP addresses of the mailboxes that you want to register. Use this switch when registering or unregistering multiple mailboxes. You must create the text file before using this script. This switch cannot be used with the /m switch.
Note
If the text file is not located in the same folder as the RegisterMailbox.vbs script, you must provide the full path to the location of your text file.
/t
Specifies the account that will be granted full mailbox access. This is typically the domain account that the Auto Accept Agent is running as on the local server. The account must be provided as domain\accountname. If Auto Accept Agent is running as Local System, you do not need to specify this switch unless you want to grant permissions to a domain account that you can use to monitor the resource mailboxes, which is necessary for the MailboxStatus.vbs script described later in this chapter.
/u
Attempts to remove the mailbox binding. Additionally, this switch also attempts to remove full mailbox access for the Auto Accept Agent account specified in the /t switch.
/DEBUG
Outputs verbose debug information you can use to diagnose issues.
For example, if you were using a file named Mailboxes.txt to register multiple mailboxes, where the Agent's security context is example\AgentAccount, you might type the following at the command prompt:
C:\>cscript RegisterMailbox.vbs /f:Mailboxes.txt /t:example\AgentAccount
For more information see: http://technet.microsoft.com/en-us/library/bb124104.aspx
Once you setup the Auto Except Service on your Exchange Server, here is the script that you will need to use in order to register your resource.
cscript RegisterMailbox.vbs {/m:mailbox@domain.com | /f:file.txt} [/t:domain\AgentAccountName] [/u] [/DEBUG]
Where:
/m
The primary SMTP address of the mailbox that you want to register. Use this switch when registering or unregistering a single mailbox.
/f
The name of the text file that contains the primary SMTP addresses of the mailboxes that you want to register. Use this switch when registering or unregistering multiple mailboxes. You must create the text file before using this script. This switch cannot be used with the /m switch.
Note
If the text file is not located in the same folder as the RegisterMailbox.vbs script, you must provide the full path to the location of your text file.
/t
Specifies the account that will be granted full mailbox access. This is typically the domain account that the Auto Accept Agent is running as on the local server. The account must be provided as domain\accountname. If Auto Accept Agent is running as Local System, you do not need to specify this switch unless you want to grant permissions to a domain account that you can use to monitor the resource mailboxes, which is necessary for the MailboxStatus.vbs script described later in this chapter.
/u
Attempts to remove the mailbox binding. Additionally, this switch also attempts to remove full mailbox access for the Auto Accept Agent account specified in the /t switch.
/DEBUG
Outputs verbose debug information you can use to diagnose issues.
For example, if you were using a file named Mailboxes.txt to register multiple mailboxes, where the Agent's security context is example\AgentAccount, you might type the following at the command prompt:
C:\>cscript RegisterMailbox.vbs /f:Mailboxes.txt /t:example\AgentAccount
For more information see: http://technet.microsoft.com/en-us/library/bb124104.aspx
Monday, June 11, 2007
Managing Your Email
I was talking with a friend this weekend about email and how people use it. Yes, I was bitching… So, here are a few tips that he and I came up with for people to manage their email.
Touch Each Message Only Once
Begin by instantly turning every message into an action. Drag the message either to the To-Do Bar or to the Calendar to make it part of your work. Dragging messages to either place creates a new item containing the text of the e-mail.
Second, delete it! Remove processed items from your Inbox after they're in the To-Do Bar or the Calendar. The best choice is to delete items. If you can't give up your attachment to past messages, move them to an archive folder where they won't distract you.
Need More Than 2 Minutes? Drag The Message To The To-Do Bar
If you have a group or various groups of people who may need to see and act on messages, keep track of them using contact categories. When you need to delegate tasks, you can address a single e-mail to all of the contacts in a single category by dragging that category to the Inbox
Automate Repetitive Tasks
In striving to touch each message only once, you may become aware that you send the same message repeatedly to many different people. The Quick Parts feature can help in that quest. Just select the text you want to use as a Quick Part, click the Quick Parts button under the Insert tab and choose Save Selection to Quick Part Gallery. To use a Quick Part, simply choose Quick Part and pick your message from the Gallery.
Don't Repeat Yourself; Address Everyone At Once
Organize your actions each day by dragging items from the To-Do Bar to the bottom of your daily calendar. This allows you to achieve balance between scheduled appointments and ongoing work. If you can do what a message requires in less than 2 minutes, just do it.
Try not to use BCC
If you are going to blind carbon copy someone, Don’t! After you send the original email to the person, use Forward to send the information to the other individual. This will also allow you to put in additional comments.
Do you really need to Reply to All
I don’t know how many times I have seen this. A message goes out to everyone one in the company or building about something important, like “your lights are on”. And someone hits the “reply to all”… Then the flood gates are open. So, ask yourself this question, Does all these people care about what I am about to send?
Touch Each Message Only Once
Begin by instantly turning every message into an action. Drag the message either to the To-Do Bar or to the Calendar to make it part of your work. Dragging messages to either place creates a new item containing the text of the e-mail.
Second, delete it! Remove processed items from your Inbox after they're in the To-Do Bar or the Calendar. The best choice is to delete items. If you can't give up your attachment to past messages, move them to an archive folder where they won't distract you.
Need More Than 2 Minutes? Drag The Message To The To-Do Bar
If you have a group or various groups of people who may need to see and act on messages, keep track of them using contact categories. When you need to delegate tasks, you can address a single e-mail to all of the contacts in a single category by dragging that category to the Inbox
Automate Repetitive Tasks
In striving to touch each message only once, you may become aware that you send the same message repeatedly to many different people. The Quick Parts feature can help in that quest. Just select the text you want to use as a Quick Part, click the Quick Parts button under the Insert tab and choose Save Selection to Quick Part Gallery. To use a Quick Part, simply choose Quick Part and pick your message from the Gallery.
Don't Repeat Yourself; Address Everyone At Once
Organize your actions each day by dragging items from the To-Do Bar to the bottom of your daily calendar. This allows you to achieve balance between scheduled appointments and ongoing work. If you can do what a message requires in less than 2 minutes, just do it.
Try not to use BCC
If you are going to blind carbon copy someone, Don’t! After you send the original email to the person, use Forward to send the information to the other individual. This will also allow you to put in additional comments.
Do you really need to Reply to All
I don’t know how many times I have seen this. A message goes out to everyone one in the company or building about something important, like “your lights are on”. And someone hits the “reply to all”… Then the flood gates are open. So, ask yourself this question, Does all these people care about what I am about to send?
Tuesday, April 17, 2007
Outlook 2007 patch addresses performance issues
Post from Greg Hughes Blog:
Microsoft on Friday released a patch for Outlook 2007 that addressed a number of performance issues (described in KB933493). Complaints of sluggishness have been circulating since before the product was formally released, typically where large OST (offline folders used for synchronization) and PST (personal folders typically used for archiving) files are involved.
From Computerworld:
The 8.3 MB update should accelerate the download of messages from the Exchange e-mail server and reduce temporary freezes resulting from deleting messages or copying them from one folder to another, according to Jessica Arnold, Outlook’s program manager.
The update should also let Outlook 2007 users switch between messages faster and enable faster program startup, she said.
I have installed it and I have not noticed anything, but I also run with a delay and caching enabled on my laptop...
Microsoft on Friday released a patch for Outlook 2007 that addressed a number of performance issues (described in KB933493). Complaints of sluggishness have been circulating since before the product was formally released, typically where large OST (offline folders used for synchronization) and PST (personal folders typically used for archiving) files are involved.
From Computerworld:
The 8.3 MB update should accelerate the download of messages from the Exchange e-mail server and reduce temporary freezes resulting from deleting messages or copying them from one folder to another, according to Jessica Arnold, Outlook’s program manager.
The update should also let Outlook 2007 users switch between messages faster and enable faster program startup, she said.
I have installed it and I have not noticed anything, but I also run with a delay and caching enabled on my laptop...
Sunday, November 12, 2006
Exchange Cache Mode - Good and Bad
Outlook 2003 has a great feature called Exchange Cache Mode. According to Microsoft,When Cached Exchange Mode is enabled, Outlook 2003 uses a local copy of your mailbox. At the same time, Outlook 2003 maintains an online connection to a remote copy of your mailbox in Exchange Server.
Putting the Outlook email client into cached-mode enables several functions designed to lessen the dependence of a connection between the Outlook client and the Exchange server. Such as creating a local copy of the GAL and a local copy of the users INBOX all allow more of the users interaction with their mail client to take place on their workstation (even if the connection to the mail server is unavailable.) This means a reduced amount of interactive network traffic back to the mail server.
In many situations, this is a very good thing. Laptop users are a wonderful example of users who need to be able to work with their email even when they are not connected to the network. Another would be users whose mail box is not local but is accessed over a WAN, VPN or dial-up link where the user experience when interacting with the mail server over a slow link would not be a good one.
There can be a down side to using cached-mode, however. Situations where users need to interact with another users mail information such as sharing of calendar information. Or where there is interaction with another application like ActiveSync or Blackberry. These and other problems are documented by Microsoft and others so the problems are well known technically.
Instead of a blanket Outlook cache-mode for everyone, a better and more supportable recommendation would be the following:
Good candidates for Outlook cache-mode:
*Portable devices (tablets, laptops, etc.) where the user typically is accessing Exchange services at less than LAN speeds (WAN, VPN, dial-in)
*Users in locations without a local Exchange server and access a mailbox over a WAN link.
Bad candidates for Outlook cache-mode:
*Blackberry users
*ActiveSync users
*Users who have given delegate control to other users over their mailbox/calendar
*Users whose mailbox is located on an Exchange 2000 server
*Users who have client-side rules to be run
*Users who are about to have their mailbox moved to another mail server
The Microsoft article http://support.microsoft.com/kb/870926/ can be used as a reference as this has both instructions for enabling Outlook cached-mode but there is also a section labeled "Practices to avoid when you use Outlook 2003 with Cached Exchange Mode" that should be reviewed.
Putting the Outlook email client into cached-mode enables several functions designed to lessen the dependence of a connection between the Outlook client and the Exchange server. Such as creating a local copy of the GAL and a local copy of the users INBOX all allow more of the users interaction with their mail client to take place on their workstation (even if the connection to the mail server is unavailable.) This means a reduced amount of interactive network traffic back to the mail server.
In many situations, this is a very good thing. Laptop users are a wonderful example of users who need to be able to work with their email even when they are not connected to the network. Another would be users whose mail box is not local but is accessed over a WAN, VPN or dial-up link where the user experience when interacting with the mail server over a slow link would not be a good one.
There can be a down side to using cached-mode, however. Situations where users need to interact with another users mail information such as sharing of calendar information. Or where there is interaction with another application like ActiveSync or Blackberry. These and other problems are documented by Microsoft and others so the problems are well known technically.
Instead of a blanket Outlook cache-mode for everyone, a better and more supportable recommendation would be the following:
Good candidates for Outlook cache-mode:
*Portable devices (tablets, laptops, etc.) where the user typically is accessing Exchange services at less than LAN speeds (WAN, VPN, dial-in)
*Users in locations without a local Exchange server and access a mailbox over a WAN link.
Bad candidates for Outlook cache-mode:
*Blackberry users
*ActiveSync users
*Users who have given delegate control to other users over their mailbox/calendar
*Users whose mailbox is located on an Exchange 2000 server
*Users who have client-side rules to be run
*Users who are about to have their mailbox moved to another mail server
The Microsoft article http://support.microsoft.com/kb/870926/ can be used as a reference as this has both instructions for enabling Outlook cached-mode but there is also a section labeled "Practices to avoid when you use Outlook 2003 with Cached Exchange Mode" that should be reviewed.
Thursday, October 26, 2006
NDR List of Codes and their meanings
The key to any troubleshooting is to isolate the problem. In the case of an NDR, discover if the fault lies with the sender, the recipient or the Exchange 2003 server. To gather more clues, send more emails to the same recipient but from different accounts. In addition, send emails to different accounts from the original sender.
Expand the search area by sending email to different sites, or to internet users. Does this tactic narrow the problem to a particular Server, Mailstore or Routing Group Connector?
If it's just one email address that produces the Non-Delivery report, do you type in the SMTP address manually, or do you click the user account in the GAL?
NDR List of Codes and their meanings
NDR
Code Explanation of Non-Delivery Report error codes for Exchange Server
4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit. (Default 22 MB)
4.3.1 Not enough disk space on the delivery server. Microsoft say this NDR maybe reported as out-of-memory error.
4.3.2 Classic temporary problem, the Administrator has frozen the queue.
4.4.1 Intermittent network connection. The server has not yet responded. Classic temporary problem. If it persists, you will also a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was broken.
4.4.6 Too many hops. Most likely, the message is looping.
4.4.7 Problem with a timeout. Check receiving server connectors.
4.4.9 A DNS problem. Check your smart host setting on the SMTP connector. For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4] You can get this same NDR error if you have been deleting routing groups.
4.6.5 Multi-language situation. Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognized command. You get this NDR when you make a typing mistake when you manually try to send email via telnet.
More likely, a routing group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space)
This status code is a general error message in Exchange 2000. In fact Microsoft introduced a service pack to make sure now get a more specific code.
5.1.x Problem with email address.
5.1.0 Often seen with contacts. Check the recipient address.
5.1.1 Another problem with the recipient address. Possibly the user was moved to another server in Active Directory. Maybe an Outlook client replied to a message while offline.
5.1.2 SMTP; 550 Host unknown. An error is triggered when the host name can’t be found. For example, when trying to send an email to bob@ nonexistantdomain.com.
[Example kindly sent in by Paul T.]
5.1.3 Another problem with contacts. Address field maybe empty. Check the address information.
5.1.4 Two objects have the same address, which confuses the categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName - check how many users are affected. Sometimes running RUS (Recipient Update Service) cures this problem. Mailbox may have moved.
5.1.7 Problem with senders mail attribute, check properties sheet in ADUC.
5.2.x NDR caused by a problem with the large size of the email.
5.2.1 The message is too large. Else it could be a permissions problem. Check the recipient's mailbox.
5.2.2 Sadly, the recipient has exceeded their mailbox limit.
5.2.3 Recipient cannot receive messages this big. Server or connector limit exceeded.
5.2.4 Most likely, a distribution list or group is trying to send an email. Check where the expansion server is situated.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit.
5.3.2 System not accepting network messages. Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email. Check SMTP log.
5.3.4 Message too big. Check limits, System Policy, connector, virtual server.
5.3.5 Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP. Email probably looping.
5.4.0 DNS Problem. Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address. Could be Virtual Server SMTP address.
5.4.1 No answer from host. Not Exchange's fault check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure. No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector. Perhaps you have Exchange servers in different Routing Groups, but no connector.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user. One user is probably using an Alternate Recipient with the same email address as a contact.
5.4.7 Delivery time-out. Message is taking too long to be delivered.
5.4.8 Microsoft advise, check your recipient policy. SMTP address should be cp.com.
NOT server.cp.com.
5.5.0 Underlying SMTP 500 error. Our server tried ehlo, the recipient's server did not understand and returned a 550 or 500 error. Set up SMTP logging.
5.5.2 Possibly the disk holding the operating system is full. Or could be a syntax error if you are executing SMTP from a telnet shell.
5.5.3 More than 5,000 recipients. Check the Global Settings, Message Delivery properties.
5.5.5 Wrong protocol version
5.6.3 More than 250 attachments.
5.7.1 Permissions problem. For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list.
Check SMTP Virtual Server Access Tab. Try checking this box: Allow computers which successfully authenticate to relay
User may have a manually created email address that does not match a System Policy.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported. Check delivery server settings
5.7.5 Cryptographic failure. Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.
Expand the search area by sending email to different sites, or to internet users. Does this tactic narrow the problem to a particular Server, Mailstore or Routing Group Connector?
If it's just one email address that produces the Non-Delivery report, do you type in the SMTP address manually, or do you click the user account in the GAL?
NDR List of Codes and their meanings
NDR
Code Explanation of Non-Delivery Report error codes for Exchange Server
4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit. (Default 22 MB)
4.3.1 Not enough disk space on the delivery server. Microsoft say this NDR maybe reported as out-of-memory error.
4.3.2 Classic temporary problem, the Administrator has frozen the queue.
4.4.1 Intermittent network connection. The server has not yet responded. Classic temporary problem. If it persists, you will also a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was broken.
4.4.6 Too many hops. Most likely, the message is looping.
4.4.7 Problem with a timeout. Check receiving server connectors.
4.4.9 A DNS problem. Check your smart host setting on the SMTP connector. For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4] You can get this same NDR error if you have been deleting routing groups.
4.6.5 Multi-language situation. Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognized command. You get this NDR when you make a typing mistake when you manually try to send email via telnet.
More likely, a routing group error, no routing connector, or no suitable address space in the connector. (Try adding * in the address space)
This status code is a general error message in Exchange 2000. In fact Microsoft introduced a service pack to make sure now get a more specific code.
5.1.x Problem with email address.
5.1.0 Often seen with contacts. Check the recipient address.
5.1.1 Another problem with the recipient address. Possibly the user was moved to another server in Active Directory. Maybe an Outlook client replied to a message while offline.
5.1.2 SMTP; 550 Host unknown. An error is triggered when the host name can’t be found. For example, when trying to send an email to bob@ nonexistantdomain.com.
[Example kindly sent in by Paul T.]
5.1.3 Another problem with contacts. Address field maybe empty. Check the address information.
5.1.4 Two objects have the same address, which confuses the categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName - check how many users are affected. Sometimes running RUS (Recipient Update Service) cures this problem. Mailbox may have moved.
5.1.7 Problem with senders mail attribute, check properties sheet in ADUC.
5.2.x NDR caused by a problem with the large size of the email.
5.2.1 The message is too large. Else it could be a permissions problem. Check the recipient's mailbox.
5.2.2 Sadly, the recipient has exceeded their mailbox limit.
5.2.3 Recipient cannot receive messages this big. Server or connector limit exceeded.
5.2.4 Most likely, a distribution list or group is trying to send an email. Check where the expansion server is situated.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
5.3.1 Mail system full. Possibly a Standard edition of Exchange reached the 16 GB limit.
5.3.2 System not accepting network messages. Look outside Exchange for a connectivity problem.
5.3.3 Remote server has insufficient disk space to hold email. Check SMTP log.
5.3.4 Message too big. Check limits, System Policy, connector, virtual server.
5.3.5 Multiple Virtual Servers are using the same IP address and port. See Microsoft TechNet article: 321721 Sharing SMTP. Email probably looping.
5.4.0 DNS Problem. Check the Smart host, or check your DNS. It means that there is no DNS server that can resolve this email address. Could be Virtual Server SMTP address.
5.4.1 No answer from host. Not Exchange's fault check connections.
5.4.2 Bad connection.
5.4.3 Routing server failure. No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector. Perhaps you have Exchange servers in different Routing Groups, but no connector.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user. One user is probably using an Alternate Recipient with the same email address as a contact.
5.4.7 Delivery time-out. Message is taking too long to be delivered.
5.4.8 Microsoft advise, check your recipient policy. SMTP address should be cp.com.
NOT server.cp.com.
5.5.0 Underlying SMTP 500 error. Our server tried ehlo, the recipient's server did not understand and returned a 550 or 500 error. Set up SMTP logging.
5.5.2 Possibly the disk holding the operating system is full. Or could be a syntax error if you are executing SMTP from a telnet shell.
5.5.3 More than 5,000 recipients. Check the Global Settings, Message Delivery properties.
5.5.5 Wrong protocol version
5.6.3 More than 250 attachments.
5.7.1 Permissions problem. For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list.
Check SMTP Virtual Server Access Tab. Try checking this box: Allow computers which successfully authenticate to relay
User may have a manually created email address that does not match a System Policy.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported. Check delivery server settings
5.7.5 Cryptographic failure. Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.
Monday, October 23, 2006
Delegate issue -
When someone sends a meeting request to a user, they receive an NDR from another user. The unknown user was at one time a delegate for the user the meeting request was sent to and has had their user account deleted. This happens when the delegate’s user account is removed from Active Directory before being removed from the delegates list.
To resolve the issue, please follow the steps below:
1. Take note of any delegates you currently have, and remove them.
2. Take note of any rules you currently have, please note that the rules will be removed and you will need to recreate them when you are done.
3. Go to Start > Run and type in “outlook.exe /cleanrules” without the quotes and click OK.
4. This will open Outlook and remove all rules, including the invisible rule that is forwarding the message to the old delegate.
5. Go back in and re-assign delegates as needed.
6. Go back in and recreate rules as needed.
To resolve the issue, please follow the steps below:
1. Take note of any delegates you currently have, and remove them.
2. Take note of any rules you currently have, please note that the rules will be removed and you will need to recreate them when you are done.
3. Go to Start > Run and type in “outlook.exe /cleanrules” without the quotes and click OK.
4. This will open Outlook and remove all rules, including the invisible rule that is forwarding the message to the old delegate.
5. Go back in and re-assign delegates as needed.
6. Go back in and recreate rules as needed.
Create Auto Responder for Group Mailbox
To configure Outlook to open the GROUP mailbox as if you are that user follow these steps:
Click the Add… button.
- Go to Start > Control Panel and open Mail.
- Click the Show Profiles… button.
Click the Add… button.
- Give the profile the same name as the shared mailbox and click OK.
- This is going to be an Exchange account.
- The server should be Exchange Mailbox Server and the name should be the username of the shared mailbox.
- Click the Check Name button, it should resolve and become underlined.
- Click through the rest of the process to create the new profile.
- In the bottom half of the window you can select Prompt for a profile to be used and click OK.
- Once you have this setup Outlook will always prompt you for the profile, you can change this back to stop prompting you after you create the rule.
To create the rule follow these steps, please not that you are using Outlook XP so some of the items may be named slightly differently.
- Login to Outlook as the mailbox you want the rule for.
- Go to Tools > Rules Wizard.
- Click the New Rule button.
- Follow the steps in the wizard, use the following settings as a guide.
- Select Check messages when they arrive and click Next.
- Check the "where my name is in the To box" option and click Next.
- Check "have the server reply using a specific message" and then click the "a specific message" link.
- Only enter the subject and body that you want and click Save and Close.
- Click the Finish button.
- Close Outlook.
Friday, October 13, 2006
wireless calendar does not synchronize properly for multiple users
Problem Description:
- The wireless calendar does not synchronize properly for multiple users.
- A configuration error between Microsoft® Outlook® and the handheld is disrupting wireless calendar synchronization.
Instructions:
- Go to Start > Run.
- Type regsvr32 CDO.DLL in the field.
- Click OK.
- Restart the BlackBerry Enterprise Server.
- Create a new Messaging Application Programming Interface (MAPI) profile.
For instructions on how to create a new MAPI profile, see Microsoft Knowledge Base article 195718. For instructions on how to configure BlackBerry Desktop Manager to use the new MAPI profile, see Support Knowledge Base article KB-03650. Note: If you are using Microsoft® Outlook® 2003, disable Cached Exchange Mode.
- Create a contact entry in Outlook and verify that it synchronizes with Outlook
- On the handheld home screen, open the Calendar.
- Click the trackwheel and select Options > Wireless Synchronization > Change Option > No.
- Connect the handheld to your desktop and open BlackBerry Desktop Manager.
- Go to Backup and Restore > Advanced, select the calendar database, and choose Clear.
- Go to Intellisync > Configure PIM > Calendar > Choose > MS Outlook > OK.
- On the main Intellisync page, select Synchronize now.
- On the handheld, open the Calendar again.
- Click the trackwheel and select Options > Wireless Synchronization > Change Option > Yes.
- If the user still encounters errors when performing a wireless synchronization, verify the CDO.DLL and MAPI32.DLL files.
Thursday, October 05, 2006
Common Problems: User receives NDR (Non Delivery Report)
I noticed that I have not posted anything regarding mail or messaging for a while now. SO.. Here is a common issue that plagues most people.
What is an NDR and why am I getting it….!!!
Overview:
When a user sends an e-mail to an individual, a NDR’s (Non Delivery Report) can sometimes be received. NDR’s occur automatically when the e-mail system cannot locate the intended recipient. This can happen internally and externally. Each scenario requires it’s own resolution.
Symptoms of Problem:
UserA will receive an NDR when sending e-mail to a recipient. This can occur when selecting the recipient from the customers personal Contacts list, when issuing a “reply” to an existing e-mail, when sending e-mail through the internet, or having Outlook put in the email address from the cache.
Issue and Resolution:
Internal recipient:
If the user receives an NDR and it is an internal recipient, the problem is likely the internal recipient has been moved to another server or routing group within the same organization. If this occurs, have the user “forward”, not “reply”, and re-select the recipient from the GAL to send. By selecting the name from the GAL, this will also replace the name in the cache.
If it continues to happen, it is possible the recipients new address has not replicated to the global catalog server that the user is using. If this is the case, the user will have to “forward” and re-select the recipient from the GAL at a later time. A couple hours should be sufficient. (Depending on the size of your organization)
If the user has receive this from a distribution list or contact in his/her Contacts container, then the customer will have to recreate the entry in the distribution list or contact.
External recipient:
If the user receives an NDR and it is to an external address, then it is possible the user has a typo in the recipients “Send” address or the cache is wrong. Have the customer verify with the recipient the correct external address and delete the entry from the Outlook cache.
Cause of Problem:
If the recipient is an internal mailbox, (within the same organization), this generally happens when the recipient’s mailbox has moved.
If the recipient is an external mailbox, (a mailbox in a different organization), this generally happens when the recipient’s mailbox is disabled, deleted, or moved.
What is an NDR and why am I getting it….!!!
Overview:
When a user sends an e-mail to an individual, a NDR’s (Non Delivery Report) can sometimes be received. NDR’s occur automatically when the e-mail system cannot locate the intended recipient. This can happen internally and externally. Each scenario requires it’s own resolution.
Symptoms of Problem:
UserA will receive an NDR when sending e-mail to a recipient. This can occur when selecting the recipient from the customers personal Contacts list, when issuing a “reply” to an existing e-mail, when sending e-mail through the internet, or having Outlook put in the email address from the cache.
Issue and Resolution:
Internal recipient:
If the user receives an NDR and it is an internal recipient, the problem is likely the internal recipient has been moved to another server or routing group within the same organization. If this occurs, have the user “forward”, not “reply”, and re-select the recipient from the GAL to send. By selecting the name from the GAL, this will also replace the name in the cache.
If it continues to happen, it is possible the recipients new address has not replicated to the global catalog server that the user is using. If this is the case, the user will have to “forward” and re-select the recipient from the GAL at a later time. A couple hours should be sufficient. (Depending on the size of your organization)
If the user has receive this from a distribution list or contact in his/her Contacts container, then the customer will have to recreate the entry in the distribution list or contact.
External recipient:
If the user receives an NDR and it is to an external address, then it is possible the user has a typo in the recipients “Send” address or the cache is wrong. Have the customer verify with the recipient the correct external address and delete the entry from the Outlook cache.
Cause of Problem:
If the recipient is an internal mailbox, (within the same organization), this generally happens when the recipient’s mailbox has moved.
If the recipient is an external mailbox, (a mailbox in a different organization), this generally happens when the recipient’s mailbox is disabled, deleted, or moved.
Tuesday, August 15, 2006
How to: Access Gmail using Outlook
Here is a quick way to be able to get your gmail email using your outlook client. I, personally, like the web interface of their site. But, for those who want everything in your outlook, here is a step-by-step way to do that.
Make sure that POP access is turned on for your Gmail account
Select Tools E-mail Accounts... from the menu in Outlook.
Make sure Add a new e-mail account is selected.
Click Next >
Choose POP3 as the Server Type.
Click Next >
Enter your Gmail account details in the Internet E-mail Settings (POP3) dialog:
- Type your full name under Your Name:.
- Type your Gmail email address under E-mail Address:.
- Type your full Gmail address under User Name: as well.
- Type your Gmail password under Password:.
- Type pop.gmail.com under Incoming mail server (POP3):.
- Type smtp.gmail.com under Outgoing mail server (SMTP):.
Click More Settings....
Go to the Outgoing Server tab.
Make sure My outgoing server (SMTP) requires authentication is checked.
Leave Use same settings as my incoming mail server selected.
Go to the Advanced tab.
Make sure This server requires an encrypted connection (SSL) is checked under both Incoming server (POP3): and Outgoing server (SMTP):
Type 465 under Outgoing server (SMTP):
- If the number under Incoming server (POP3): has not been changed to 995 automatically, enter 995 there.
Click OK
Click Next >
Click Finish.
Friday, August 11, 2006
Exchange Troubleshooting Assistant
Microsoft Exchange Troubleshooting Assistant v1.0
Here is a cool little tool that will programmatically executes a set of troubleshooting steps to identify the root cause of performance, mail flow, and database mounting issues. The tool automatically determines what set of data is required to troubleshoot the identified symptoms and collects configuration data, performance counters, event logs and live tracing information from an Exchange server and other appropriate sources. The tool analyzes each subsystem to determine individual bottlenecks and component failures, then aggregates the information to provide root cause analysis.
Here is a cool little tool that will programmatically executes a set of troubleshooting steps to identify the root cause of performance, mail flow, and database mounting issues. The tool automatically determines what set of data is required to troubleshoot the identified symptoms and collects configuration data, performance counters, event logs and live tracing information from an Exchange server and other appropriate sources. The tool analyzes each subsystem to determine individual bottlenecks and component failures, then aggregates the information to provide root cause analysis.
Thursday, August 10, 2006
Exchange: SA will not start on a Exchange 2003 Server
Problem:
Came across this issue where after installing Exchange 2003 on a Windows 2003 SP1 Server, the System Attendant would not start. This was a new build and did not have Exchange loaded on it before. When attempting to start the SA Service, it would fail almost immediately. The event log would throw an event ID: 1005, Unexpected error Access is denied. Facility: Win32 ID no: c0070005 Microsoft Exchange System Attendant occurred. There was also an error in the ESM under the server properties where the log file directory states the location of the message tracking logs. The error was “An error occurred during a call to Windows Management Instrumentation” - ID no: 80041013 - Exchange System Manager.
Solution:
After spending a lot of time with Microsoft – The solution was painfully simple. On the Domain Controller there was a registry setting to restrict anonymous access. It was set to 2, the most restrictive. The Microsoft recommended setting for this is 1. Reboot the DC and...
This resolved the issue.
Why:
The registry settings on Authenticating DC, caused access denied up on anonymous SMB connection to IPC$
Came across this issue where after installing Exchange 2003 on a Windows 2003 SP1 Server, the System Attendant would not start. This was a new build and did not have Exchange loaded on it before. When attempting to start the SA Service, it would fail almost immediately. The event log would throw an event ID: 1005, Unexpected error Access is denied. Facility: Win32 ID no: c0070005 Microsoft Exchange System Attendant occurred. There was also an error in the ESM under the server properties where the log file directory states the location of the message tracking logs. The error was “An error occurred during a call to Windows Management Instrumentation” - ID no: 80041013 - Exchange System Manager.
Solution:
After spending a lot of time with Microsoft – The solution was painfully simple. On the Domain Controller there was a registry setting to restrict anonymous access. It was set to 2, the most restrictive. The Microsoft recommended setting for this is 1. Reboot the DC and...
This resolved the issue.
Why:
The registry settings on Authenticating DC, caused access denied up on anonymous SMB connection to IPC$
Subscribe to:
Posts (Atom)
Posts
