Recently one of my customer updated that they get an different issue with their ASP application. This application running on their Web server that uses MAPI to read the Contacts folder in the Public Folders from Exchange Server 2003 SP2 machine. The user can retrieve his email in outlook and browse the public folders as he is used to, but when this user want to use the ASP page that reads the public folder he fails. Customer receives the following error: bstrPublicRootID = objInfoStore.Fields.Item(&H66310102).Value

There are new enhancements to SMTP support for .NET 4.0 - in the area of Unicode support and increased standards compliance, which is an important aspect in ensuring that legitimate emails do not get flagged as spam, as well as a few other useful features. + Decreased likelihood of being accidentally flagged as spam + Increased Unicode support + Clarification on setting header values + Multiple Reply-To addresses with the new property ReplyToList + Content Disposition time zones + Mail Address formats

Tried finding the list of information about ports, authentication and encryption by Exchange Server 2007? Your search ends here. Please refer the TechNet article . You can find the list of information about ports, authentication, and encryption for all data paths used by Microsoft Exchange Server 2007. The Notes sections following each table clarify or define non-standard authentication or encryption methods.

You need to configure the user permissions to relay e-mail messages through the SMTP service. Do the following steps: Click Start , click Run , type inetmgr or open Internet Information Manager from Control Panel > Administrative Tools, and then click OK . Expand ComputerName , and then right-click a valid SMTP virtual server. Note The placeholder ComputerName represents the name of the local computer. Click Properties . On the Security tab, add the user account as an Operator, which you want

Assume that the computer on which this example will run has neither a SMTP service nor Microsoft Outlook® Express installed. In this case, you need to send the message through some SMTP service on the network and must configure the Message object completely. Further assume that the SMTP service through which you intend to send messages requires that you authenticate yourself using basic (clear-text) authentication. An instance of the Configuration Component Object Model (COM) class is created and

Have you tried programmatically combining the two powerful enterprise tools: SQL Server 2005 (table-valued user-defined functions) with Exchange Server 2007(Exchange Web Services)? I followed the Microsoft article written by Jim Kleewein and Ray Dixon, which talks about how we can combine the SQL Server tables and Exchange Web Services to provide data from both Microsoft Exchange and SQL Server to client applications so that the data appears as if it were stored in SQL Server. SQL Server tables:

Here is some basic information on how FBA authentication is done with WebDAV. To provide some insight into how this works, you should look at the sample code of KB891748 and review it with the explanation below. Note that if you are going against Exchange 2007, you should reconsider using FBA authentication since FBA authentication is really for OWA and the settings for OWA and WebDAV are separate under 2007 – please refer to the links below for further information. 891748 How to programmatically

With any login issue, it’s important to know which authentication protocols are valid. You have to code to an authentication protocol which can be used. The authentication settings for OWA and WebDAV are tied together under Exchange 2000 and 2003. Because of this, developers run into issues with WebDAV not being able to authenticate if FBA is enabled for OWA. A developer could work around the issue so they don’t have to code for FBA authentication. However, it’s common for developers to use custom

I've seen a lot of issues with using the MSXML DOM when trying to get credentials from the owaauth.dll for FBA authentication. The managed classes seem to work all the time and in all versions. However, the MSXML DOM wont always reuturn cookies and sometimes just plain fails in the calls. Each version of MSXML has an http method at the version of the MSXML component and versions of that method which are for each prior verion of MSXML. You will find that you will get varrying mixed results per each

Sending mail using System.Net.Mail with SSL will fail: System.Net. NetworkCredential aCred = new System.Net. NetworkCredential ( "myacct" , "mypassword" ); SmtpClient smtp = new SmtpClient ( "smtp.mail.myserver.com" , 465); smtp.EnableSsl = true ; smtp.UseDefaultCredentials = false ; smtp.Credentials = aCred; System.Net.Mail only supports “Explicit SSL”. Explicit SSL System.Net.Mail only supports “Explicit SSL”. Explicit SSL starts as unencrypted on port 25, then issues a STARTTLS and switches to