Winmail.dat Received by Non-Exchange Mail Server Without Attachment Included from Exchange 2007 Server

August 7, 2008

Situation: Exchange 2007 has a contact (not a mailbox) within the GAL that end-user use to email instead of using the actual non-exchange email address. The non-exchange (network solutions) user does not get attachment sent (Word, Excel, etc.), but does get a winmail.dat file attached.

Fix: Launch Exchange Management Console, goto Recipient Configuration/Mail Contact container, open up contact you’re having the issue with, on the ‘general’ tab change the ‘Use MAPI rich text format’ drop-down to ‘Never’ and test.


You do not have permission to send to this recipient. For assistance, contact your system administrator.

August 17, 2007

From: http://blogs.technet.com/sbs/archive/2006/06/30/439685.aspx

When you try to send an e-mail message in Microsoft Exchange 2000 Server or in Microsoft Exchange Server 2003, you cannot send the e-mail message. Additionally, you may receive one of the following error messages or one of the following Non Delivery Reports (NDRs):

• Access denied 

• You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator. 

• Unlisted Message Error 

• MAPI_E_NO_ACCESS -2147024891 

• Failed to submit mail message for user USERNAME (HRESULT:-2147024891) Pausing user USERNAME. (Security error – Cannot access the users mailbox.)

NDRs

• You do not have permission to send to this recipient. For assistance, contact your system administrator. 

• The message could not be sent using your mailbox. You do not have the permission to send the message on behalf of the specified user. 

This issue is known to affect the following third-party products:

• Research In Motion (RIM) Blackberry Enterprise Server (BES) 

• Good Technology GoodLink Wireless Messaging 

 

CAUSE

This issue may occur when one of the following conditions is true:

     You do not have permissions to send e-mail messages as the mailbox owner in the account that you are using to send the e-mail message.

     You are running Microsoft Exchange 2000 Server Service Pack 3 (SP3) with a Store.exe file version that is equal to or later than version 6619.4. Version 6619.4 was first made available in the following Microsoft Knowledge Base article:

915358 A hotfix is available to change the behavior of the Full Mailbox Access permission in Exchange 2000 Server

     You are running Microsoft Exchange Server 2003 Service Pack 1 (SP1) with a Store.exe file version that is equal to or later than version 7233.51. Version 7233.51 was first made available in the following Microsoft Knowledge Base article:

895949 “Send As” permission behavior change in Exchange 2003

Note that this fix is not included with Microsoft Exchange 2003 Service Pack 2 (SP2). If you have installed the Exchange Server 2003 SP1 version of this hotfix, you must install the Service Pack 2 version after you upgrade to Service Pack 2.

     You are running Exchange Server 2003 SP2 with a Store.exe file version that is equal to or later than version 7650.23. Version 7650.23 was first made available in the following Microsoft Knowledge Base article:

895949 “Send As” permission behavior change in Exchange 2003

Note This change was not included in Exchange 2000 Server SP3, in Exchange Server 2003 SP1, or in Exchange Server 2003 SP2. The change was implemented after release of all of these service packs. However, the change is supported in each of them. The change will be included in future service packs for these products.

 

If you install Exchange Server 2003 SP2, you must install the additional update to retain the new behavior. You must do this even if you already installed the version of the update for Exchange Server 2003 SP1.

 

RESOLUTION

 

Grant the Blackberry or other application’s service account the Send As permission on every user in a container or domain.

To grant Send As for the service account on a single user account, follow these steps:

1. Start the Active Directory Users and Computers management console.

2. On the View menu, make sure that the Advanced Features option is selected. If this option is not selected, the Security page will not be visible for domain and container objects.

3. View the properties of the user account and click the Security tab.

4. The service account (BESAdmin, for instance) is not listed.

5. Add the service account (BESAdmin, for instance). It will default to having Read permissions, but not Send As.

6. Note: This step is optional. The only permission the service account needs is Send As, so you can remove the Read permissions if you wish.  To do so, uncheck the following checkboxes in the Allow column for the service account (BESAdmin, for instance):

Read

Read Account Restrictions

Read General Information

Read Group Membership

Read Logon Information

Read Personal Information

Read Phone and Mail Options

Read Public Information

Read Remote Access Information

Read Web Information

 

7. With the service account (BESAdmin, for instance) still selected, check the following box in the Allow column:

Send As

8. Click OK until you have exited and saved all changes. 

9. Restart the Microsoft Exchange Information Store service.


Attachment file types restricted by Outlook 2007

June 12, 2007

Attachment file types restricted by Outlook 2007


Live Local add-in for Microsoft Office Outlook

June 11, 2007

The Windows Live Local Add-in for Outlook, available at http://outlook.local.live.com/minisites/local/outlook/default.aspx  , adds the ability to have maps and directions in meeting requests, via a new Location tab. The add-in also can give directions based on your current location and the location of the meeting, as well as add travel time to the meeting. This functionality is available for Microsoft Office Outlook 2007, 2003, and 2000. You can also save frequent start and end points with a friendly name for easy direction generation in the future. You can right-click the map and set certain locations such as Home and Business.


Business Contact Manager Team Blog : Database Tool Released

April 25, 2007

Business Contact Manager Team Blog : Database Tool Released


Restore an Outlook BCM Database

April 25, 2007

Restore a BCM Database

Rule #1 – Back up your data often! BCM includes a backup utility that makes it easy – use it.

If you don’t have a recent backup, you may be able to recover the data, if you have a copy of the two database files, ending with the extension LDF and MDF.

  1. Create a new database in BCM, naming it the same as your old database.
  2. Exit Outlook and stop the BCM service in Admin Tools, Services.
  3. Replace the new database files with your old ones, making sure the file names are identical.
  4. Restart the BCM service and Outlook.

Get rid of annoying security alerts in Microsoft Outlook!

April 24, 2007

Makes it possible for the user to specify what status this program should have: allow access, block access or run the default Outlook handler. Later on you can change or delete the decision taken.

http://www.mapilab.com/outlook/security/