exchange-server-2007

Problem at hand Our C# Windows application uses EWS Managed API 2.0 to create appointments in a user's calendar. Each appointment has an extended property with a unique value. It later locates an appointment using FindItems and an ItemView . Users experience significant delays the first time this search is performed. Subsequent response times are entirely acceptable. ("first time" is a little vague here, because users may experience the delay again later in the day) // locate ID of appointment where extended property value equals 1234: var filter = new Ews.SearchFilter.IsEqualTo

I am able to send emails using the typical C# SMTP code across Exchange 2007 as long as both the from and to addresses are within my domain. As soon as I try to send emails outside the domain I get: Exception Details: System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: 5.7.1 Unable to relay How can I get exchange to accept my email and send it out to the internet? Try #2... How about using a Exchange Pickup Folder instead? They are a faster way to send emails through Exchange because it just creates the email and drops it in the folder, no waiting to

Does anyone know of an open source PHP class (preferably BSD or MIT license) that will interface with the MS Exchange Server 2007 Web Services via. SOAP? I am looking for a higher level class that has functionality for sending messages via. the web service. I had this same problem, so I started building something, here: https://github.com/rileydutton/Exchange-Web-Services-for-PHP It doesn't do much yet (basically just lets you get a list of email messages from the server, and send email), but it would be good enough to use as a basic starting point for doing some more complicated things. I

The article here: http://msdn.microsoft.com/en-us/library/exchange/bb738399(v=exchg.80).aspx in the section "Use Registry Key Names for TimeZoneNames", tells me that when I can create a calendar item in Exchange, I can pass it the name of a timezone. This is sort-of working, but how do I name "Eastern Daylight Time"? Only 'US Eastern Standard Time' is accepted as valid. In works in that I schedule something for say 14:00, when it displays in my Google calendar I see it is displaying at 15:00 EDT, so it used the EST timezone I passed in. Problem is that it sends out reminder emails with the

As far as I am now, I know how to fetch appointments from exchange server, BUT as soon as I want to see the required and optional attendees, these fields are empty ... I checked the appointment trice and there is an attendee, except me. Do I have to config Outlook differently or do I miss something? List<Appointment> listOfAppointments = new List<Appointment>(); CalendarFolder cfolder = CalendarFolder.Bind(MyService, WellKnownFolderName.Calendar); CalendarView cview = new CalendarView(from.ToUniversalTime(), to.ToUniversalTime()); cview.PropertySet = new PropertySet(ItemSchema.Subject); cview

I am about to write a ews-application to connect exchange with another calendar programm. What occured to me, how do I get to know, which appointments get deleted on exchange? Is there a way to tell? I couldn't find it in the API and documentation. Thanks in advance. Depending on how a user deletes an appointment (or any item), different things are done: Soft-Delete: The item is moved to the recycle bin of the mailbox. Hard-Delete: The item is instantly removed. You have multiple ways to get information about deleted items: Query the folder using a FindItems call and select ItemTraversal

I'm having a problem getting emails to bounce to a specific email address, different to the From address. A particular client requires that we send emails from a specific email address (call it contact@clientcompany.com ). Our Exchange admins have created an account on the Exchange box so that we can log in and send from that address. Our Exchange server is spoofing that address / domain. This works fine. Unfortunately the emails sent from contact@clientcompany.com are not bouncing back to us. They are presumably bouncing back to the contact account at clientcompany.com (which may or may not