Any thoughts?
I have the same result when ticking or unticking " When replying or forwarding, use the format of the original message"
Im running Outlook for Mac 2011.
I have outlook connected to Gmail (using IMAP), but suddenly just started to download the messages (as usual) but with all messages set as "read". (I think I have not changed anything, but not sure)
Any Clue?
Hi,
This is my first post. I dont have much experience with Macs. I've had a look through the settings but cant find what I need to use SSLV3. Recently we had our TMG gateway security increased to block SSLV2 as per this http://www.isaserver.org/articles-tutorials/configuration-security/improving-ssl-security-forefront-threat-management-gateway-tmg-2010-published-web-sites.html since then the mac users cannot access the our exchange when working from an external connection. The mac users are able to work ok when on the corp network as they arent hitting the TMG. Other users running Win7/8 with Outlook are working ok on and off the corp network. Webmail works ok externally as well.
I am trying to find out if there is a way to force Outlook 2011 to use SSLV3
I've checked the certificates and they are for Lync.
Thanks in advance.
Dave
Whenever I receive digitally signed emails from anyone I get an error message that reads, "The e-mail address "*** Email address is removed for privacy ***" in the signing certificate does not match the sender's address."
I've determined that this happens probably because of a case mismatch with the email that is listed in the certificate and the actual email address that appears in the header of the mail message. For example, I will see an email address like *** Email address is removed for privacy *** in the certificate. But, his Exchange server translates the email address to *** Email address is removed for privacy ***.
Based on the RFC description for handling email, the Outlook 2011 client should accept mixed case. But it doesn't seem to.
Is there a legitimate workaround to this? I've looked for a setting to see if I can switch this behavior to match the RFC but I don't see one.
<grasping at straws> Can Microsoft put an item into the backlog to fix this please. </grasping at straws>
Thanks for your time.
John
Recent Comments