Microsoft Knowledge Base Email Alertz

(823569) - If you send an e-mail message that contains an attachment to the public folder server after you create an e-mail enabled document library in your Microsoft Windows SharePoint Services virtual server, the e-mail message attachment is not uploaded to...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 823569 - Last Review: November 6, 2007 - Revision: 2.0

E-mail message attachments are not uploaded to the document library in your Windows SharePoint Services 2.0 virtual server

SYMPTOMS

If you send an e-mail message that contains an attachment to the public folder server after you create an e-mail enabled document library in your Microsoft Windows SharePoint Services 2.0 virtual server, the e-mail message attachment is not uploaded to the document library.

CAUSE

This behavior occurs if the Microsoft Exchange Server 2003 virtual server is configured to use forms-based authentication. Microsoft Windows SharePoint Services 2.0 requires Integrated Windows Authentication (NTLM) to access the Microsoft Exchange server to accept e-mail attachments from public folders.

WORKAROUND

To work around this behavior, create a new Exchange HTTP virtual server to handle the public folders. To do this, follow these steps:
  1. On the Exchange server, start the Microsoft Exchange System Manager utility.
  2. If administrative groups are enabled, expand Administrative Groups, and then expand the administrative group that contains the Exchange server where you want to create the new Exchange HTTP virtual server.
  3. Expand Servers, expand your Exchange server, and then expand Protocols.
  4. Right-click HTTP, point to New, and then click HTTP Virtual Server.
  5. In the Name box, type a descriptive name for the Exchange HTTP virtual server, and then click Advanced.
  6. Click the identity, click Modify, change the TCP port value to 81, and then click OK two times.
  7. Under Exchange path, click Public folder, and then click OK.
  8. Verify that the new Exchange HTTP virtual server is working correctly. To do this, start a Web browser program, and then enter the following URL:
    http://localhost:81
  9. On the server that is running Microsoft Windows SharePoint Services 2.0, start the SharePoint Central Administration utility.
  10. Click the Configure virtual server settings from the Virtual Server List page link.
  11. Click the Windows SharePoint Services virtual server that you want to configure. For example, click Default Web Site.
  12. Under Virtual Server Management, click the Virtual server general settings link.
  13. In the E-Mail Enabled Document Libraries area, enter the new Exchange HTTP virtual server information in the Public folder server and root path box, and then click OK.

MORE INFORMATION

For more information about Windows SharePoint Services 2.0, visit the following Microsoft Web site:
http://office.microsoft.com/en-us/sharepointtechnology/FX101494661033.aspx (http://office.microsoft.com/en-us/sharepointtechnology/FX101494661033.aspx)

APPLIES TO
  • Microsoft Windows SharePoint Services 2.0
  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition
Keywords: 
kbtshoot kbnewfile kbattachments kbemail kbpending kbprb KB823569
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate