showing posts tagged with 'exchange'
by lunarg on January 8th 2014, at 14:34

To allow an Exchange user to send from an external e-mail address, perform the following steps:

  1. Create a Mail Contact with the correct external e-mail address in AD and in Exchange.
  2. Open Exchange Management Shell and set up the permissions:
    Get-MailContact | Add-ADPermission -User MyUser@MyLocalDomain -AccessRights ExtendedRight -ExtendedRights "Send As"
    Replace the first e-mail address with the external one, the second part contains the user you wish to assign the permission to.
by lunarg on February 23rd 2013, at 11:13
Windows SBS has a nasty habbit of taking forever to shutdown/restart. This is because there's a built-in waiting mechanism to allow enough time for the Exchange-services to shutdown. Unfortunately this delay is usually a whole lot longer than it normally would take if you were to stop the Exchange-services yourself. Because the delay does no longer occur when the Exchange-services are already stopped manually, I usually tend to stop Exchange first, then do the shutdown/restart.

Because Exchange consists of many services, at work, we wrote some helper scripts to stop all Exchange-services with only a mouse click, allowing for a quicker shutdown/restart of a server. I've decided to share thes  ...
by lunarg on August 24th 2012, at 10:34

Currently, Exchange/Outlook only supports client-side rules if you want to move messages to a specific folder, depending on which alias it's sent to. This means that the rule only works when Outlook is running, which is not always possible.

You can workaround the issue by creating a rule that checks for the content of the message headers. This type of rule can be created server-side and will always run when messages arrive on the Exchange server. By checking whether the alias is present in the message headers, you can easily create a rule that moves those messages to another folder.

by lunarg on June 22nd 2012, at 16:04

A note of warning I read on the Avast Forums: if your Avast subscription runs out, the Exchange Information Store no longer starts and bails out with an error "failed to start virus scan". Very annoying indeed...


by lunarg on June 22nd 2012, at 16:00
We updated Avast to the latest version on a client's server running SBS 2011. The update apparently included antispam. All of a sudden, the Transport service kept failing, and all messages (in both directions) landed in the Poison Queue. Restarting the Transport service did not fix the issue, and there was nothing we could do.

Googling around, we found that the trouble was indeed related with Avast. Disabling the Antispam Shield did not resolve the issue, but disabling the transport agent in Exchange, via Powershell was the fix:

disable-transportagent "avast antispam for exchange"

After disabling the agent, everything came to life again.

@ Avast: you should really start  ...
by lunarg on June 20th 2012, at 12:49
Unlike SP2, there's no installation tool for installing SP3 on an SBS 2008. Fortunately, the installation is pretty straight-forward. The steps to perform depend largely on whether or not your SBS 2008 server is running Forefront Security or not. If it's not, simply install SP3 like you normally would. The installation will succeed without additional tasks. If you are running Forefront Security, you will have to disable it before installing SP3, then re-enable it when installation has completed.

Download SP3:

Run the software, it will extract its contents to a directory of your choosing. I recommend creating an empty directory as the  ...
by lunarg on September 2nd 2011, at 12:49
If you are not able to configure Outlook using the Microsoft Online Sign-in Tool for some reason, there's a way to do it manually.

For this to work, you need the following:

a working internet connection (duh);

your username and password;

your storage location (usually closest to your HQ).

First off, we need the mailbox store server. To find this, you have to log in to Outlook Web Access. Your ICT department should already have given you information on how to do this. If not, use one of the following urls, depending on your location:

Asia Pacific (APAC):

Europe, the Middle East, and Africa (EMEA): https://red002.mail.emea.microsoftonline  ...
by lunarg on May 6th 2011, at 15:17
Had a problem with a client who is running Outlook 2007 with Exchange 2010 on a 2008R2 terminal server: each message sent from Outlook (composed by Outlook) had a blank message body. The recipient side would see it like this, and the empty message would be stored in the Sent Items folder of Outlook. This behaviour was system-wide, meaning that each user was experiencing this problem.

After some digging around, I found this link on the internet stating it could be related to the virus scanner. My eye was particularly caught by a post of someone who was running Avast 4.8 on TS (which was identical to what the client was running). After disabling scan outbound mail the problem was fixed.

I   ...
by lunarg on September 15th 2010, at 11:31
Installing Exchange 2007 Service pack 2 on a Windows 2008 SBS generates an error, as detailed here:

To resolve, you can either follow the instructions outlined in the KB, or you can download the installation tool, especially designed for SBS 2008.

First, download these: Exchange 2007 SP2 (64-bit edition):

Exchange 2007 SP2 installation tool for SBS 2008:

Run the first file to extract its contents to a folder of your c  ...
by lunarg on January 28th 2010, at 17:28
I've written an article before on how to change the outgoing SMTP port for SmartHost in Exchange 2003. Now, I have to do this again for Exchange 2007 as they've changed this procedure.

When you're unable to send e-mail directly to the internet (using MX), you probably have to set up a SmartHost to relay the e-mail for you. This is basically your ISP's SMTP server, but can be another server as well.
In certain cases, the default SMTP port (port 25) cannot be used to connect to the SmartHost, so you have to change this to something else. Gmail for instance, uses port 587 for SMTP. Other 3rd party mail services use this (or another port) as well to circumvent spam protection initiated by a lot  ...
by lunarg on January 18th 2010, at 13:30
When you are running an Exchange server, and have your users access the server from outside the company network, you usually have to open up access to OWA. This enables users to access their mail, contacts and appointments by using an internet browser. Occassionally, someone also has a ActiveSync enabled phone that they would like to use. This protocol also uses OWA for syncing data. And very rarely, there's also a guy (usually the CEO) who simply wants to use its Outlook to connect - this is possible through web as well using RPC-over-HTTP(S), but that's information for another blog post (on another day in the far far future...) .

One of the hassles when configuring this, is the fact that   ...
by lunarg on May 17th 2007, at 15:24
Because of (Belgian) providers limiting SMTP (port 25) traffic to their own servers, makes it necessary for us (as an 3rd party ISP) to allow our customers to use our own mailserver for all outgoing mail. To circumvent this limitation, we've configured the mailserver to listen on port 26 as well.

For our customers with only a few mail clients (so no local mailserver), this is usually not a problem. A quick change of the SMTP port, solves their issues. For people that have a catch-all mailbox (and a local mailserver), the mailserver itself usually allows the change.

Of course, some of our clients have Exchange servers, and there, the change was not that obvious.
After a bit of a search, we'  ...
showing posts tagged with 'exchange'
« October 2017»
« You only find out who is swimming naked when the tide goes out. »
Warren Buffett