Situation: Exchange 2007 has a contact (not a mailbox) within the GAL that end-user uses to email instead of using the actual non-exchange email address. The non-exchange (network solutions) user does not get attachment sent (Word, Excel, etc.), but does get a winmail.dat file attached.
Fix: Launch Exchange Management Console, goto Recipient Configuration/Mail Contact container, open up contact you’re having the issue with, on the ‘general’ tab change the ‘Use MAPI rich text format’ drop-down to ‘Never’ and test.
I recently came across a client’s backup that was completing successfully daily but not flushing the transaction logs for Exchange as it should. In the job properties of Backup Exec, the Exchange section declares that it will perform a full backup and flush the comitted logs but it simply never happens.
After some research, Veritas article 280659 had the answer…and it was a simple one. In the job properties, review the options under Advanced Open File and make sure the option “Process Logical Volumes for backup one at a time” is not checked. As its explained in the article, if this is unchecked, Backup Exec will use a different open file option (VSS) for the Exchange logs to allow it to flush them afterwards.
Microsoft Forefront Security for Exchange Server is the cause of this messsage:
The original contents of this file have been replaced with
this message because of its characteristics.
File name: ‘winmail.dat’
Virus name: ‘CorruptedCompressedFile’
Goto Forefront Server Security Administrator > Settings> General Options > Scanning
Goto checkbox name “Delete Corrupted Compressed File”
Uncheck the box and test
To find the product version in Exchange 2007, execute the following command in PowerShell:
Get-ExchangeServer | fl name,edition,admindisplayversion
Refer to the article below to find out how the build number corresponds to a product version:
This microsoft article details the various Exchange Server versions, including service packs.
Some recent ones:
Microsoft Exchange Server 2003 6.5.6944 October 2003
Microsoft Exchange Server 2003 SP1 6.5.7226 May 2004
Microsoft Exchange Server 2003 SP2 6.5.7638 October 2005
Microsoft Exchange Server 2007 8.0.685.24 or 8.0.685.25 December 2006
Microsoft Exchange Server 2007 SP1 8.1.0240.006 November 2007
I came across a situation where an organization had been setup to use RPC/HTTPs “Outlook Anywhere” for some time and all the Outlook 2003 clients seemed to work fine. One user had Outlook 2007 and was unable to connect using this method. In the LAN and through OWA everything worked fine. I tried tons of different solutions online but in the end, the problem was with the configuration in Exchange. I looked over the suggested configuration here:
and I discovered that the RPC ports hadn’t been configured as the article suggests. I used the recommended “RPCnofrontend” tool: http://www.petri.co.il/software/rpcnofrontend.zip and everything worked fine after that.
There is no specific SMTP service like you saw with Exchange 2003 and IIS. However, if you’re just trying to stop the listening port 25 for Inbound/Outbound mail, stop the ‘Microsoft Exchange Transport’ service.
In Active Directory when you have an Exchange server a user or group, even a public folder can have multiple smtp email addresses associated with the entity (user/group/public folder etc.), but finding the non-default email address can be tedious. A great way to search for it is:
Go to Active Directory Users and Computers –> right click on the domain and click find –> in the find field, change the criteria to ‘custom search’ –> click the advanced tab where you can type in a LDAP query. If you are trying to find out who has email@example.com, type proxyAddresses=smtp:firstname.lastname@example.org.
Wildcards can be added to the email address portion, and you can also type a wildcard ie. *.yourdomain.com and then change the view to add the proxyaddress column to see all of the entities with their proxyAddresses (email addresses)
These days many mailservers are requiring reverse DNS (rDNS) and SPF records to validate the sender from this domain.
How does SPF work:
SPF is easy to understand. The “Internet” uses DNS (Domain Name System) to resolve Domain Names (as an example www.msexchange.org) into IP addresses. DNS is also used to direct requests for different services like e-mail and Web Servers. For every Domain around the world an MX (Mail Exchanger) record must exist. An MX record tells the e-mail sender where the target server for receiving mail is located.
SPF is publishing “reverse MX” records in DNS which tells the mail sender which machines send mail from the domain.
The recipient of the e-mail can now check these records to ensure that e-mail is coming from a “trusted” sender from this domain.
These “reverse MX” records can be easily published in DNS. It takes only one line in DNS to fullfil all requirements.
Microsoft has come up with a good and easy wizard (webpage not downloadable tool) that asks a few questions and spits out the correct SPF.
How to add SPF file to Windows Server DNS – link