Skip to main content

Microsoft Exchange 2007 Rollup 5 is out

On 26th of October 2007 Microsoft released Update Rollup 5 for Exchange 2007. There are 11 issues fixed in this update:

  • The recipient information in an e-mail message incorrectly contains the character string "%40" in the address instead of the at sign (@) in Exchange Server 2007
  • Non-English characters in the meeting description field are replaced by question marks when an Exchange Server 2007 user opens a meeting invitation that was sent by a Lotus Notes user
  • You receive a NDR message after you send an e-mail message that contains a .zip file attachment by using an Exchange 2007 Edge server
  • The Conversation view is broken when the public folder is replicated between Exchange 2007 servers
  • An e-mail message recipient cannot use a Web-based e-mail client to access an attachment when the message is sent by using Exchange 2007
  • The last instance of a recurring meeting request is missing when a mailbox is migrated from Lotus Notes to Exchange 2007
  • The Exchange Management Console crashes when you redraw a mailbox in the Recipient Configuration node in Exchange 2007
  • Certain IMAP commands may cause the CPU usage to increase to 100 percent on an Exchange 2007 server that is running the Client Access Server (CAS) role
  • You cannot recover e-mail items after you use Outlook Web Access for Exchange 2007 to delete e-mail items in the Deleted Items folder
  • You receive a read receipt that contains incorrect time information from Exchange 2007
  • The Set-Mailbox cmdlet fails when you run the cmdlet together with the EmailAddressPolicyEnabled parameter in Exchange 2007

You can find description of the update here.

Comments

Popular posts from this blog

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.