Mail.app and Exchange 2007

I'm trying to interface the Mac OS X Mail application to an Exchange 2007 server. I've configured Mail to use IMAP, and I've verified that IMAP is enabled on the server because I can receive mail just fine.
I cannot send mail, however.
What kind of authentication does Exchange 2007 require for relaying outgoing SMTP mail? The Mac OS X Mail application has a number of settings for this, but none of the combinations I've tried seem to work.

What kind of authentication does Exchange 2007 require for relaying outgoing SMTP mail?
What authentication method used is based on how the server is setup. Nobody here can anwer that. You'll need to ask your mail server admins.

Similar Messages

  • Mail.app and Exchange 2007 with Rollup 3 ... anyone get it to work?

    Spent way too much time on this...
    After finding our our Exchange 2007 server didn't have the legacy components installed to ensure WebDav would work, we can now connect to our Exchange 2007 mail server from Microsoft Entourage for all Windows Active Directory accounts.
    For Apple Mail however, this is not the case. Opening mail, the account information does default in accurately (email, userID, exchange 2007 server) when I enter a users password, it says that it is unable to connect to mail server user/password failed.
    If I manually create the account, the same thing occurs, a pop-up appears prompting for a password, which I enter and it comes back saying it isn't valid.
    The password is valid because on the same Mac I open up Entourage and log in.
    Keychain is NOT used and none of the passwords are held because of the headaches this causes.
    Looking for ideas, thinking this is more of an Apple Mail.app bug not working with Exchange than a Microsoft issue.

    Just want to add to this...it was resolved the Advanced tab is very important on mail.app.
    The Advance tab authentication must match what the Exchange server/Active Directory is using.
    For us NTLM is what we need to use.
    Also we found that one exchange server had a bad installation while another had no problem connecting via mail.app.
    Thus the installation is going to be looked at.

  • Cannot sort emails sent from Mail App and Exchange

    When trying to sort emails on Outlook in Windows, lets say by "Flag", emails coming from a mac using mail app and exchange get placed at the top of the list.
    Have tried sending emails from the same account via webmail and iphone and they get sorted correctly.
    Anyone has had this problem?

    So, Here's what happens:
    1) Send email from Laptop (Snow Leopard) with Exchange Integration
    2) Send email from iPhone (3.1) with Exchange Integration
    In Outlook 2003 sort by flag (neither of these messages are flagged). Any email sent from the Snow Leopard is sorted first in the Unflagged category in Outlook. Any of the email sent from the iPhone is sorted normally.
    There's no differences in the headers to cause these to sort differently. The only headers that differ are the Date, Subject/Thread-Topic, Thread-Index, Message-ID, x-ems-stamp. But, in the Message-ID it has the same domain.
    Both Snow Leopard and iPhone are configured to use the same Exchange OWA/OWS.
    Message was edited by: GaryRudolph

  • Assertion Failures using Mail.app with Exchange 2007...

    We have been implementing and migrating our end-users to Exchange 2007. In doing so we found that Mail.app end-users were experiencing Assertion failures in Console.app. They used to cause Mail.app to crash and lose connectivity frequently to the Exchange 2007 server. We made a change to the firewall to allow communication to happen between domain controllers, but haven't been able to determine if this in fact resolved or helped hide the root cause. We seem to be no longer crashing Mail.app or losing connectivity, but the same logs when we would crash/lose connectivity are still happening when you look in Console.app.
    *Here is an example of an Assertion failure where "The Operation couldn't be completed":*
    +11/12/10 1:19:36 PM Mail[3201] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSConnection.m:374+
    +Received an unexpected error: Error Domain=NSXMLParserErrorDomain Code=5 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.)", response: (null)+
    + 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
    + 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
    + 2 Message 0x00007fff8036301b -[EWSConnection sendMessage:forRequest:] + 1117+
    + 3 Message 0x00007fff8036e5b9 -[EWSGateway sendMessage:forRequest:] + 79+
    + 4 Message 0x00007fff80381a63 -[EWSRequestOperation executeOperation] + 104+
    + 5 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
    + 6 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
    + 7 Foundation 0x00007fff8662abeb __doStart2 + 97+
    + 8 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
    + 9 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
    + 10 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
    + 11 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
    *I also get this Assertion failure every time I re-open Mail.app that shows up in Console.app that says "Mail did something wrong: The specified folder could not be found in the store.":*
    +11/12/10 12:44:22 PM Mail[3201] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
    +Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x1012f1830> (EXECUTING)+
    + 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
    + 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
    + 2 Message 0x00007fff80382956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295+
    + 3 Message 0x00007fff80377aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88+
    + 4 CoreFoundation 0x00007fff879c26d7 __NSArrayEnumerate + 1399+
    + 5 Message 0x00007fff80377d86 -[EWSGetFolderResponseOperation executeOperation] + 445+
    + 6 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
    + 7 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
    + 8 Foundation 0x00007fff8662abeb __doStart2 + 97+
    + 9 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
    + 10 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
    + 11 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
    + 12 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
    +11/12/10 12:44:22 PM Mail[3201] Recieved EWS error: Error Domain=MFEWSErrorDomain Code=79 UserInfo=0x1148c1d10 "The specified folder could not be found in the store."+
    We are getting these Assertion Failures for other end-users as well that are using Mail.app and connecting to Exchange 2007 Server. I have wiped my mail.app account and started from fresh and that didn't help. I did it manually as well ensuring that preference files, caches, and passwords related to mail.app, ical.app, and Address Book.app were removed. That did not work. I just went from 10.6.4 to 10.6.5 hoping that would correct the issue, it did not. I even set up on another Mac a baseline Snow Leopard and patched it and then configured my mail account and still got the same errors.
    What I am hoping for is not a miracle (Fixing the problem), but being told what these errors mean and if there is any risks to be concerned with. In other words, can I ignore these error messages or should I be concerned? Like I said it was causing us to get the sideways thunderbolt or triangle with an exclamation point and even crashing Mail.app at times. That hasn't happened since we let the all of the domain controllers talk to each other, even though they shouldn't have to.

    I echo your hope for someone shedding a light on this. I too am geting Assertion failures, every few days, though without much in the way of crashes.
    Here is an example of a log entry describing one recent such failure:
    +5.12.2010 11:04:40 Mail[17075] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
    +Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x11d80ec70> (EXECUTING)+
    0 Message 0x00007fff81f7d6e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
    1 Message 0x00007fff81f7d649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
    2 Message 0x00007fff81ede956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295
    3 Message 0x00007fff81ed3aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88
    4 CoreFoundation 0x00007fff8448c6d7 __NSArrayEnumerate + 1399
    5 Message 0x00007fff81ed3d86 -[EWSGetFolderResponseOperation executeOperation] + 445
    6 Message 0x00007fff81f8bab9 -[MonitoredOperation main] + 229
    7 Foundation 0x00007fff847b4de4 -[__NSOperationInternal start] + 681
    8 Foundation 0x00007fff84893beb __doStart2 + 97
    9 libSystem.B.dylib 0x00007fff85f6b2c4 dispatch_call_block_andrelease + 15
    10 libSystem.B.dylib 0x00007fff85f49831 dispatch_workerthread2 + 239
    11 libSystem.B.dylib 0x00007fff85f49168 pthreadwqthread + 353
    12 libSystem.B.dylib 0x00007fff85f49005 start_wqthread + 13
    Perhaps coincidentally, I am having trouble with syncing iCal with my Exchange account. Ii have only found this thread on the subject, and am in the process of trying to find there the solution to that problem:
    http://discussions.apple.com/thread.jspa?threadID=2138051
    Any and all insight would be greatly appreciated.

  • Mail.app and Exchange issue

    Hello. I have 7 exchange accounts (45,000 letters in them) in my mail.app and every day i have a problem that mail.app delete all messages and start downloading it form server. Can any one help me with this problem.
    p.s. on the other macbook i have 1 exchage account with 18.000 messages and it works fine.
    Is this problem because to many exchange accounts or to many messages or because i use VPN for take mail from this accounts? Help me please.

    I can't even get the Exchange Mailbox to appear in Mail.app. The same account works for Calendar and Reminders (Tasks). Configuring as an "Other" type account also does not work. Instead I end up with an IMAP style account that can't be deleted from mail.app.

  • Windows 8.1 Mail app and Exchange Autodiscover

    An organisation Im currently supporting has exchange 2010 and autodiscover setup. I've used nslookup to verify autodiscover settings and everything seems ok. When I launch the Windows 8.1 Mail metro app, autodiscover is not working. I have to enter all the
    required fields to get email working.
    Is this anything additionally for Windows Mail autodiscover to work that is different from autodiscover for the Outlook client that needs to be in place?
    Is it a requirement for Exchange Active sync to be enabled? I've been told they are using a 3rd party tool, possibly Sophos,
    thanks
    glen_cni

    Hi,
    As far as I know, Mail APP doesn't have autodiscover ability to identify the confirguation of Exchange. While, in my opinion, it would be better to contact the Mail APP support for further assistance:
    http://answers.microsoft.com/en-us/windows/forum/windows8_1_pr-ecoms
    Roger Lu
    TechNet Community Support

  • Mail.app and Exchange Server Problems?

    I am an Apple Mail user and my university just switched to an Exchange Server 2003 for student e-mail. The university is only supporting Entourage, but I have configured Mail to work with Exchange without any major problem. This week, I have noticed that I have a problem where Mail.app will say that I have four new e-mails in my Exchange in-box. When I click on my Exchange in-box, no new e-mail appears. After experiencing this problem for about a week, I finally logged onto our Exchange web access site for the university. I discovered that I did indeed have four new e-mails in my in-box, but these e-mails were not showing up in Mail.app. Interestingly, all of the e-mails were undeliverable e-mails that had popped back because I had the wrong address. I am wondering why these e-mails would show up in on web access, but not show up in Mail.app.
    I have spoken with our university tech. support numerous times and they have been unable to figure out the problem. It seems this may be a Mail.app isse as opposed to an Exchange problem.
    Thanks,
    Joe Biedlingmaier

    I use Exchange at work and have 5 Macs working with it w/o problems. The trick is to correctly specify SMPT and Outlook Web Access Server.
    Do the following:
    When you create a new mail account, choose IMAP or Exchange (if it shows on the list)
    for Email Address specify your exchange email address
    continue
    for Incoming Mail Server: use name of the server without any prefixes such as mail. (The example shown under the box is wrong. It took me forever to figure it out)
    for username and password use the same one you use when log in into exchange webmail
    continue
    for outgoing email server use the name of the server, again without smtp.
    you may need to use authentification in order to send mail. In that case use the same user and password as when you log into your exchange
    I was doing it as I was writing this to make sure it workes. It does.

  • Mavericks mail.app and exchange online - crash

    Hello everyone!
    I want to setup my exchange online account within mavericks 10.9.2. Everytime i try this the mail.app crashes with the following errorreport:
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** setObjectForKey: object cannot be nil (key: serverName)'
    abort() called
    terminating with uncaught exception of type NSException
    With OS X 10.8 (Parallels Desktop installation) and Outlook for Mac 2011 on Mavericks the setup of the exchange online account works as expected wihtout any crash.
    The Mavericks installation was a clean install (no upgrade)
    Have someone else the same problem and maybe a solution for this? The problem exists since 10.9.0 and my hope was 10.9.2... still the same shi...!
    - Cyberspace

    I don't know if you found a solution yet but this is what I found, tested and verified to work for me. (Osx Mavericks with all latest updates).
    1) Disconnect from Internet first (unplug network cable or turn off wifi)
    2) setup the Exchange account
    3) the lack of Internet connection will force the wizard to ask for server name
    4) input the server name (outlook.office365.com if you are using exchange online)
    5) connect to the internet THEN click OK or CONTINUE
    6) then it will work like a charm...
    here is the link to the thread that I foudn the solution from
    https://discussions.apple.com/message/25166000#25166000

  • Mail.app and Exchange

    Goin a bit crazy here.
    My workmail is running on a exchange server, no big suprise there.
    But here goes my ratehr enoying problem!
    As my windows (yepp, it's sad) workstation get's email instantly so does my Iphone.
    My my mac - nope. I have a macbook air and i'm running mavericks.
    And not only this - as I sometimes try ty send emails it cand send with the slected server, exchange.
    But I can send from my Iphone at those moments.
    When I open my air i instantly get all my emails from my private linux server,
    but I have to wait 3-5 minutes before the exchange mail arrives, and then I ge a bunch of them
    Any one have a clue?

    Already in discussion
    https://discussions.apple.com/thread/5470507?start=0&tstart=0

  • Windows 8.1 Mail app and Exchange 2010 EAS partnership - "Make Windows user account an Administrator" to meet security requirements?

    As the title says,  I have a new Windows 8.1 based device which I'm trying to connect to my Exchange 2010 box (SP3 Update Rollup 2).  I currently have my iphone set up as an EAS client with no problems.  I have an EAS policy on my mailbox
    with the following settings surrounding passwords :
    Require Password, Require Encryption, Allow Simple Password, Time without user input - 10 minutes.  Allow non-provisional devices is also checked.
    The Windows 8.1 device has Bitlocker enabled, which meets the encryption requirement - I know this because the 1st time I tried this it moaned about Bitlocker needing to be enabled to meet requirements, though at that time the local user account on the Windows
    8.1 device was an admin level account so it never mentioned this issue, it worked normally.
    Now, while using a std user account on the Windows 8.1 device and trying to connect up via EAS, it complains that my local windows user account must be an ADMIN level account to meet the security requirements...?
    Anyone encountered this?

    Did anyone solve this problem? I'm also struggling with this issue.
    this is still a problem. I'm just hitting it now and it's not doing much for management's love of Microsoft devices.
    Evidently, it has to be an admin to set the policies on the device to match the policies on the EAS. And once set, a user can be changed back.
    But this is seriously not cool. Don't the "app" folks and the enterprise folks talk to each other?

  • Duplicate Notes in Mail.app w/Exchange server

    Latest version of Mail.app and Exchange 2007 server.
    What we are experiencing is that a users NOTES will not replace when edited but leave new versions over and over and over again. Mail is not cleaning out the old versions correctly.
    If you go back later and open the most "recent" version sometime the old ones will disappear sometime not.
    This is a mirror of the "drafts" duplication issue which was corrected in 10.6.3
    Anyone has seen this issue please contact me through this thread.
    Thanks
    Robert

    I'm having the same issue with an Exchange account. I cannot create non-Exchange Notes, and every note I work on drops a new one not just with ever save, but every few seconds as I edit the note. After a few minutes working on a long note, I have a dozen older "revisions" that it plonked down as I was working. I have to delete them when I'm "done", and sometimes if I delete all but the last one... the last ("real/current") edit also disappears.
    On top of that mess, I have it set not to display notes in the inbox, and yet it does. What a mess.

  • Mail and Exchange 2007 Assertion Failure

    I have been using Mail with Exchange 2007 on SL since it came out without issue, until last week. Once I start Mail I experience the following issues:
    1. Mail folders sometimes show as empty. Occasionally synchronizing the account corrects the issue, but often I need to restart Mail.
    2. Messages are duplicated in my Inbox. The only way to correct this is to delete and readd my account.
    3. Sent mail creates a draft message after the message has been sent. This usually goes away in 5-10 minutes of normal use.
    4. I get the following error message around 5 times per second in the system log while Mail is open and connected to Exchange:
    Mail[718]: * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1077/MessageStores.subproj/EWSConnection.m:374\nRe ceived an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 UserInfo=0x118be9740 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)", response: (null)\n(\n 0 Message 0x00007fff86b70119 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137\n 1 Message 0x00007fff86b7007e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220\n 2 Message 0x00007fff86ab2fbe -[EWSConnection sendMessage:forRequest:] + 1117\n 3 Message 0x00007fff86abe0ec -[EWSGateway sendMessage:forRequest:] + 79\n 4 Message 0x00007fff86ad0fbf -[EWSRequestOperation executeOperation] + 104\n 5 Message 0x00007fff86b7e347 -[MonitoredOperation main] + 229\n 6 Foundation 0x00007fff8270f06d -[__NSOperationInternal start] + 681\n 7 Foundation 0x00007fff8270ed23 ___startOperations_block_invoke2 + 99\n 8 libSystem.B.dylib 0x00007fff84e0fce8 dispatch_call_block_andrelease + 15\n 9 libSystem.B.dylib 0x00007fff84dee279 dispatch_workerthread2 + 231\n 10 libSystem.B.dylib 0x00007fff84dedbb8 pthreadwqthread + 353\n 11 libSystem.B.dylib 0x00007fff84deda55 start_wqthread + 13\n)
    I have only seen one person report this issue so far and the fix was to remove /Library/Preferences/com.apple.mail.plist. I tried that, but the issue was not resolved.
    I am running Mail 4.2 on Snow Leopard 10.6.2 on a MBP 15" unibody. Any help is appreciated.

    I too have been using Mail.app x Exchange 2007 since SL came out without issue. Very similar issues started exhibiting themselves last week for me, as well:
    1. Mail folders sometimes show as empty (including the inbox). A restart of Mail fixes this.
    2. New messages occasionally only show headers. A restart of Mail fixes this.
    3. Mail will occasionally hang forever retrieving new messages.
    4. Sending a message will occasionally return a failure message, when it was, in fact, delivered. If I choose to "Send Later", a duplicate message is immediately sent.
    #1-3 are annoyances, #4's caused me to switch away from Mail.app--comes across as incredibly unprofessional to my user base and associates.
    Here's just one of the hundreds of messages that appears in Console (these literally pop up every 2-5 seconds I have Mail.app open..):
    3/11/10 3:25:05 PM Mail[30150] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1077/MessageStores.subproj/EWSConnection.m:374
    Received an unexpected error: Error Domain=EWSExchangeWebServicesErrorDomain Code=277 UserInfo=0x143a245c0 "The operation couldn’t be completed. (EWSExchangeWebServicesErrorDomain error 277.)", response: (null)
    0 Message 0x00007fff828eb119 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
    1 Message 0x00007fff828eb07e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
    2 Message 0x00007fff8282dfbe -[EWSConnection sendMessage:forRequest:] + 1117
    3 Message 0x00007fff828390ec -[EWSGateway sendMessage:forRequest:] + 79
    4 Message 0x00007fff8284bfbf -[EWSRequestOperation executeOperation] + 104
    5 Message 0x00007fff828f9347 -[MonitoredOperation main] + 229
    6 Foundation 0x00007fff878ab06d -[__NSOperationInternal start] + 681
    7 Foundation 0x00007fff878aad23 ___startOperations_block_invoke2 + 99
    8 libSystem.B.dylib 0x00007fff87dabce8 dispatch_call_block_andrelease + 15
    9 libSystem.B.dylib 0x00007fff87d8a279 dispatch_workerthread2 + 231
    10 libSystem.B.dylib 0x00007fff87d89bb8 pthreadwqthread + 353
    11 libSystem.B.dylib 0x00007fff87d89a55 start_wqthread + 13
    I'll try deleting and reinstalling the Developer Tools as hinted at in the above post, but I'm not so sure it'll make a difference for me, as my Mac Pro was immediately loaded with SL.

  • Mail and Exchange 2007 won't allow customizable "From" Header

    I use Mac Mail with an Exchange 2007 server. In Preferences > Accounts, under "Account Information," I have two different e-mail addresses (e.g., the address for that exchange server and a gmail address) listed in the "Email address" field. When I create a new message, there is a pull-down menu next to "From:" that is supposed to allow me to choose which of those two e-mail addresses should appear in that field.
    However, regardless of which e-mail address I choose, the e-mail message always has the "From:" address for the exchange server. In other words, it won't allow me to customize the "From:" field. This worked properly in the past and I've been using it for awhile, but it quit working when I re-installed Mail. Everything else works perfectly.
    Anyone else experiencing this? Any recommendations?
    Thanks!

    Thanks for your message.
    Actually, changing "Reply-To" isn't what I need. I need the proper e-mail address to show in the "from" field; for example, because I need to send messages to a server and those messages need to come from a specific e-mail address.
    And, the pull-down message is definitely next to the "From" field whenever a new message is generated.
    I actually don't receive messages in Mail for the other two accounts (e.g., I use Gmail's web interface for Gmail messages). I'm simply needing to modify the "From:" field in OUTGOING messages, something that used to work but quit working recently.

  • ICal and exchange 2007 in 10.6

    Mail.app and Addressbook.app work perfectly fine. I set up all my exchange information in the Mail.app preferences just like i was told to. iCal comes back with an error message saying that my email address isn't valid. It is. I am using exchange 07 with auto discovery on.
    here is my server info.
    Mailbox owner: Bradley Maskell [[email protected]]
    User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
    Outlook Web Access experience: Basic
    User language: English (United States)
    User time zone: (GMT-05:00) Eastern Time (US & Canada)
    Exchange mailbox address: /o=ALOL/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=B.Maskell
    Outlook Web Access host address: http://win.alol.net.br/owa
    Outlook Web Access version: 8.1.393.1
    Outlook Web Access host name: win.alol.net.br
    Client Access server name: WIN.alol.net.br
    Exchange Client Access server .NET Framework version: 2.0.50727.4016
    Client Access server operating system version: Microsoft Windows NT 6.0.6002 Service Pack 2
    Client Access server operating system language: en-US
    Microsoft Exchange Client Access server version: 8.1.240.0
    Client Access server language: en-US
    Client Access server time zone: E. South America Standard Time
    Microsoft Exchange Client Access server platform: 64bit
    Mailbox server name: WIN.alol.net.br
    Mailbox server Microsoft Exchange version: 8.1.240.0
    Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
    Authentication type associated with this Outlook Web Access session: Basic
    Public logon: Yes

    I'm seeing pretty much the same thing...
    Mail.app and Contacts are working perfectly. iCal, on the other hand, is only half working. I can accept invitations from my Exchange account no problem, but cannot send invites once created.
    The error messages are random (like n748 is seeing)... sometimes it says the user/pass are wrong, other times it says "iCal cant save the event to the Exchange server".
    Exchange server is 2007 with auto discovery.
    I hope someone can help shed some light on this. I'd like to completely remove the train wreck that is Entourage from my system

  • Establish mail flow from Exchange 2007 to Exchange 2013

    I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
    Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

    Was this question answered.  We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped.   Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
    using "Custom Settings" - manually entered IPs for DNS in the Exchange  Admin Center "DNS Lookups".
    Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.  
    Any assistance will be greatly appreciated.  

Maybe you are looking for