Most of Outlook’s Exchange specific functionalities such as Automatic Replies (also known as “Out of Office Assistant” or “OOF”) only work for the main mailbox and not for delegate or Shared Mailboxes.
If you have been assigned Full Access permissions to this mailbox by your Exchange administrator (verify this with him/her if you do not know; delegate permissions are not enough!)or know the credentials of the other mailbox, then there are 3 ways in which you can enable the Automatic Replies for a shared or additional mailbox.
Exchange Administrators can also enable Automatic Replies for another user without logging on to the mailbox by using an Exchange PowerShell command, the Exchange Admin Center or a 3rd party management tool.
User Method 1: Outlook Web App
Probably the easiest way to go is to use Outlook Web App. You can ask your mail administrator for the URL if you don’t know it. In Outlook 2010, Outlook 2013 and Outlook 2016, you may find the URL in the Info section when pressing on the File menu tab.
When you have been granted Full Access permissions, then you can logon with your own username and password and click on your own picture or name in the top-right corner to get to the option to open another mailbox.
Open another mailbox… command in OWA 2013.
If you haven’t been granted Full Access permissions but do have separate logon credentials for the additional mailbox, you can use that to logon instead.
Once logged in, you can enable Automatic Replies in the following way:
Outlook on the Web (Office 365 for Business – Exchange Online) Gear icon (left side of your picture in the top right corner)-> Automatic Replies
OWA 2016 Gear icon (left side of your picture in the top right corner)-> Automatic Replies
OWA 2013 Gear icon (right side of your name)-> Set automatic replies
OWA 2010 Options (below your name)-> Set Automatic Replies…
OWA 2007 Options (left side of your name)-> Out of Office Assistant
Extra Tip! You can use the “In Private” or “Incognito” mode of your Internet browser to prevent automatic logon or to be able to stay logged on to your own mailbox as well.
User Method 2: Additional Exchange account
If you are using Outlook 2010, Outlook 2013 or Outlook 2016 and either have been granted Full Access permissions to the mailbox or have been provided separate credentials for it, then you can also configure this shared mailbox as an additional Exchange account rather than to add it as a secondary mailbox of your own.
To do this, click on the File tab and choose Add Account. When setting up the account, Auto Account Setup may recognize your main mailbox linked to your user account. When this happens, specify the email address of the shared mailbox instead.
For more details and screenshots of this process see Adding an additional or shared mailbox from the same Exchange organization to Outlook.
Once the mailbox has been added, select its Inbox folder and enable Automatic Replies as you would normally do for your own mailbox.
Note: You should not do this if you have been assigned as a delegate as well for this mailbox. In that case, it is recommended to use a separate Mail Profile instead.
User Method 3: Separate Mail Profile
If you want to enable Automatic Replies for the shared mailbox in Outlook but are still using Outlook 2007 or previous, then you’ll have to use the Mail applet in Control Panel to create an additional Mail Profile.
You’d then set up this Mail Profile with the shared mailbox as the main mail account rather than your own. This also requires you that you either have been granted Full Access permissions to this shared mailbox or have been provided credentials for it.
Just like the “Additional Exchange account” method above, Auto Account Setup might try to configure it automatically with your own mailbox. You’d then have to specify a different address or configure the account manually as well.
Admin Method 1: Exchange PowerShell
If you are an Exchange administrator, then using the Set-MailboxAutoReplyConfiguration Exchange PowerShell command is the supported and native way to go to enable Automatic Replies without logging on to the mailbox itself.
A web server is a system that manipulates requests via HTTP protocol, you request a file from the server and it responds with the requested file, which might give you an idea that web servers are only used for the web.
Actually, web servers can also be found embedded in devices such as printers, routers, when you open your router configuration page, there is a web server behind it.
When you open the printer configuration page, there is also a web server behind it serving your requests, so web servers are important today because they are used everywhere.
How Webserver Works
First, your browser sends a request to the server.
The server takes the requested file or page from you and maps it to the corresponding file from the server. The server sends the file back to the browser with some information such as its MIME type, the length of the content and some other useful information.
Sometimes the requested file is a static page like HTML pages or dynamic pages like PHP, Java, Perl or any other server side language.
For example, when you type www.yourDomain.com, the browser queries the DNS server about the IP address of the computer: www.yourDomain.com. Once the browser gets the response from the DNS, it starts a TCP connection on port 80 and asks for the default web page, then this page is sent to you and that’s all.
Linux Webserver Implementations
There are many Linux web server implementations available for you to use:
Apache server
Nginx
Lighttpd
Apache Tomcat
Monkey HTTP Daemon (used especially for embedded systems)
There are more Linux web servers, but this list is the most used web servers.
The most used web servers are Apache and Nginx.
In this post, we will use Apache server for several reasons:
It is stable.
It is flexible.
It is secure.
We’ll install and configure Apache server on Linux, but at first, let’s review some of the basics of HTTP protocol basics.
Understanding HTTP
When you request a file or a page from a web server, the client at first connects to the server on port 80. After successful connection, the client then sends HTTP commands (also methods) to the server. This command includes a request header which includes information about the client.
To view these request headers in chrome, open chrome devtools, then open network panel and visit google.com and check the request headers, you should see something like this:
The request header also includes information about the client, like the user agent and the accepted formats.
Additional information may be sent with the request header. For example, if you click on a link that will open another website, the header will include the referral site.
After receiving the request header completely, the server responds with the requested file or page along with a response header.
The response header includes information about the received content, its type, and other information.
You can check the response headers from the browser network panel.
Install Apache Webserver
You can install Apache server on Red Hat based distros using the following command: $dnf-yhttpd
Or if you are using a Debian-based distro, you can install it like this: $apt-get-yinstall apache2
The Apache web server service is called httpd on Red Hat based distros like CentOS, while it is called apache2 in Debian based distros.
If you are using a firewall like iptables, you should add a rule for port 80. $iptables-IINPUT1-mstate--state NEW-mtcp-ptcp--dport80-jACCEPT
Or if you are using firewalld, you can use the following command: $firewall-cmd--add-port=80/tcp
To start your service and enable it on boot:
$systemctl start httpd
$systemctl enablehttpd
You can check if your service is running or not, using the following command:
$systemctl status httpd
Now open your browser and visit http://localhost orhttp://[::1]/ if you are using IP v6 and if your installation goes well, you should see your HTML homepage.
Configuring Apache Webserver
You can add files to Apache in the /var/www/html directory for top-level pages.
Just remember to make sure that any files or directories placed in that directory are world-readable.
The default index page is index.html.
The Apache configuration files are in /etc/httpd/conf/ directory.
On Debian based systems like Ubuntu, you may find it at /etc/apache2/apache2.conf file.
We can’t discuss every option for Apache on a single post, but we will discuss the most important options.
You call them options or directives.
ServerRoot Option
This option specifies the configuration folder for Apache web server. On Red Hat based distros, the ServerRoot option is /etc/httpd/ directory. On Debian distros the ServerRoot option is /etc/apache2/. ServerRoot/etc/httpd
Listen Option
This is the port that Apache web server will use to wait for incoming connections.
The default value for this option is 80 for nonsecure connections and 443 for secured connections.
If you have multiple IP addresses on your server, you can assign which IP should listen for connection using Listen option.
You can specify a different port other than 80, just make sure that it’s not in use.
You can run many HTTP servers on the same hardware every one on a unique port.
When a server runs on a non-standard port such as port 8080, it will require the port number to be explicitly stated like this: www.example.com:8080 Listen80
ServerName Option
This option specifies the hostname of the web server that appears to the visitors. ServerName FQDN
DocumentRoot Option
This defines the path that will contain your files that will be served.
The default path is /var/www/html . DocumentRoot/var/www/html
MaxRequestWorkers Option
This option sets the maximum number of concurrent connections that the server will receive.
LoadModule Option
This option is used to load modules into Apache web server.
There are a lot of Apache modules like these: mod_cgid: This module is used to run CGI scripts using Apache web server. mod_ssl: Provides secure connections via SSL and TLS protocols. mod_userdir: This module allows you to serve content from users specific directories.
If you want to disable loading a specific module, you can comment the Load module line that contains that module.
Or if you use Debian based distros like Ubuntu, you can use these commands:
$a2enmod modulename
This command to enable the module.
$a2dismod modulename
This command to disable the module.
All these commands do is create a symlink under /etc/apache2/mods-enabled directory with the file that contains the module you want to enable. All files under this directory are included in Apache configuration by default, so any file will exist in this directory will be included.
And if you use a2dismod, the symlink will be removed.
If you enable or disable a module, you have to reload or restart apache web server.
LoadModule mod_cgid.so
Include Option
This option allows you to include other configuration files.
You can store all the configuration for different virtual domains, and Apache will include them at runtime. Include filePath
UserDir option
This option specifies the directory that will contain the files that will be accessible via the web server. This directory is usually named public_html and its location in user’s home directory.
For example, if you have a user adam who wants to make his web content available via Apache web server.
First, we make a public_html folder under his home directory.
Then set the permission for the public_html folder:
$chmod644public_html
Now if we put an index.html file, it will be accessible via the browser like this: http://YOURHOSTNAME/~adam UserDir public_html
Alias Option
This option specifies the location of the files that are outside the DocumentRoot location and need to be served by the Apache web server.
Like you have files outside DocumentRoot and you want them to be available to the visitors. Alias URL_Path Actual_Path
ErrorLog Option
This option specifies the error log file for Apache web server.
ErrorLog/var/log/httpd/error_log
VirtualHost Option
This option allows you to host multiple websites on the same server.
The idea is that the content is served based on the requested hostname.
To setup a virtual host for the host www.example.com. First, create a VirtualHost option in /etc/httpd/conf/httpd.conf file.
And specify the DocumentRoot and ServerName like this:
1
2
3
4
5
6
7
8
9
10
11
<VirtualHost www.example.com>
ServerAdmin admin@example.com
DocumentRoot/home/adam/public_html
ServerName www.example.com
ErrorLog/var/log/users/adam/error_log
</VirtualHost>
Keep in mind that the ServerName option must be resolvable via DNS.
These are the most used Apache options.
Virtual Host Types
There are two types of virtual hosts that you can define in Apache web server:
Name-based virtual hosts
IP-based virtual hosts
The NameVirtualHost directive defines which addresses can be virtual hosts; the asterisk (*) means any name or address on this server. You can write them like this:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
NameVirtualHost *
<VirtualHost *>
ServerName www.example.com
DocumentRoot"/home/user1/public_html/"
</VirtualHost>
<VirtualHost *>
ServerName www.example2.com
DocumentRoot"/ home/user2/public_html/"
</VirtualHost>
If you have more than one IP address and you want to use SSL certificate, the website must be on a dedicated IP address. You can write IP-based virtual hosts like this:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
<VirtualHost192.168.1.2>
ServerName www.example.com
DocumentRoot"/home/user1/public_html/"
</VirtualHost>
<VirtualHost192.168.1.3>
ServerName www.example2.com
DocumentRoot"/ home/user2/public_html/"
</VirtualHost>
Apache Process Ownership
We know from the Linux process management that each process inherits its permissions of its parent process.
This fact is true for all processes except for applications with the SETUID bit set, they inherit permissions from the owner, not the parent process. A good example is the /bin/su.
If a normal user runs /bin/su program, it does not inherit the permission from adam, but it acts as a root user running it.
Since Apache web server needs to bind port 80, and this needs root privileges.
After binding to port 80, Apache can run as a normal user and read only files that have permissions to read them.
Based on the Linux distro you use, the user could be one of the following:
nobody, www, apache, www-data, or daemon.
I delayed introducing two more options for apache till reaching that point.
User Option
This specifies the user ID which the web server will use to answer requests.
User www-data
Group Option
This specifies the group that Apache web server will use to read files.
Group www-data
Security is very important for sites that use executable scripts such as CGI or PHP scripts.
The use that you will use will have permission to read and write the content of all sites on the server. But we want to ensure that only the members of a particular site can read their own site only.
This is very important because if a site got compromised, the attacker will be able to read all files since the apache user has permission to do that.
So how to solve this problem?
suEXEC Support
A popular method is to use suEXEC. suEXEC is a program that runs with root permissions and makes CGI programs run as the user and group IDs of a specific user, not the Apache server user.
You can specify the user on each virtual host like this:
1
2
3
4
5
<VirtualHost www.example.com>
SuExecUserGroup adam adamGroup
</VirtualHost>
Just that simple.
Apache Authentication
You may want to restrict some parts to specific visitors. It’s like a password protected directory.
In Apache, you can store authentication information file called .htpasswd file.
You can use the htpasswd command to do that.
First, create the .htpasswd file using the htpasswd command:
$htpasswd-c/home/adam/.htpassswd myuser
The -c option is needed the first time you run htpasswd, but when you need to add more users you shouldn’t use -c because it will overwrite the file.
Then create a .htaccess file in the public_html folder and write the following:
1
2
3
4
5
6
7
8
9
10
11
12
13
<Location/vip>
AuthName"test"
AuthType Basic
AuthUserFile/home/adam/.htpasswd
Order deny,allow
require valid-user
</Location>
AuthName is required, you can use any string you want. AuthType Basic says that you’re using htpasswd style user file. AuthUserFile points to the file that contains the generated password from htpasswd command.
The Order line indicates that Apache must deny access by default, and only allow access for users specified in the htpasswd file.
The require directive means any user in the .htpasswd file is allowed.
Troubleshooting Apache Webserver
If you modify the httpd.conf file and restart or reload Apache web server and it did not work, then you have typed a wrong configuration, however, this is not the only case that you need to troubleshoot Apache, you may look at the apache logs to see how the service works so you can diagnose the problem and solve it.
The two main log files for apache areerror_log and access_log files.
You can find these files in /var/log/httpd/directory in Red Hat based distros, or in /var/log/apache2/ directory if you are using Debian based distros.
The access_log file contains every request to Apache web server with the details about client requested that resource.
The error_log file contains errors of Apache web server.
You can use tail command to watch the log file:
$tail-f/var/log/httpd/error_log
I recommend you to review the Linux syslog server to know more about logging.
Most of Outlook’s Exchange specific functionalities such as Automatic Replies (also known as “Out of Office Assistant” or “OOF”) only work for the main mailbox and not for delegate or Shared Mailboxes.
Probably the easiest way to go is to use Outlook Web App. You can ask your mail administrator for the URL if you don’t know it. In Outlook 2010, Outlook 2013 and Outlook 2016, you may find the URL in the Info section when pressing on the File menu tab.
If you are using Outlook 2010, Outlook 2013 or Outlook 2016 and either have been granted Full Access permissions to the mailbox or have been provided separate credentials for it, then you can also configure this shared mailbox as an additional Exchange account rather than to add it as a secondary mailbox of your own.
If you want to enable Automatic Replies for the shared mailbox in Outlook but are still using Outlook 2007 or previous, then you’ll have to use the Mail applet in Control Panel to create an additional Mail Profile.
If you are an Exchange administrator, then using the Set-MailboxAutoReplyConfiguration Exchange PowerShell command is the supported and native way to go to enable Automatic Replies without logging on to the mailbox itself.
Another way to do this as an Exchange Administrator is via the Exchange Admin Center (also known as ECP).
If you regularly need to manage the Automatic Replies setting for your users, then both admin methods mentioned above can become quite cumbersome.
