Guide – How To Start – NginX (IMAP, SMTP, POP3) Mail Server on Ubuntu

NginX Mail Server can be used for web serving, reverse proxying, caching, load balancing, media streaming & can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers.

This is a quick deployment and ready-to-run image.
Simple and rapid installation. Easy to maintain.

The guide how to work with the NginX (IMAP, SMTP, POP3) Mail Server on Ubuntu

  1. After purchasing and starting the VM you should know its IP address. You can find it in the personal account of Azure. (It is necessary to select the virtual machine from the list. By clicking the item “Overview”, your IP is displayed in the line of “Public IP Address”).
  1. To work, you must open port 80 (TCP) and 443(TCP) in the network properties in the azure firewall.
  2. To connect to a VM, you need the PuTTy application to connect via ssh. You can download it at the following link – Download
  3. Run Putty, enter the VM address in the “Host” field, and click “Open” to connect.
  1. In the opened console you should enter a username and password that were specified when creating the virtual machine.
  2. After entering the command nginx -V you can see that nginx is built with support for modules –with-mail –with-mail_ssl_module.
  3. To check the status of nginx, you can enter the command sudo systemctl status nginx.
  4. Also you can see that in the configuration file /etc/nginx/nginx.conf basic directives for mail are added.

If you have any questions, you can refer to the official documentation:

See sample authentication script at

Disclaimer: This solution is built using Nginx, Inc. and its contributors, an opensource software. This solution is Licensed under the 2-clause BSD license. This software is provided by the author and contributors “as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the author or contributors be liable.
For any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.

Website Built with

Up ↑

%d bloggers like this: