Column 1
Skip to content
Column 1

How To Configure Windows Server 2022 VM To Use Proxmox Mail Gateway

Proxmox VE hosting administration checklist

2026 PMG relay update

This tutorial stays focused on Windows Server mail relay through Proxmox Mail Gateway. For current PMG stacks, confirm relay allowlists, TLS, connector/auth behavior, message tracking, and DNS records before putting production mail through it. Use this with the official PMG docs and our PMG 9.0 upgrade guide.

Introduction

If you're looking to secure your Windows 2022 VM's email traffic, Proxmox Mail Gateway is an excellent solution. This powerful email filtering and antivirus tool can help you prevent spam and malware from entering your network. In this guide, we'll walk you through the steps required to configure your Windows 2022 VM to use Proxmox Mail Gateway.

Step 1: Install Proxmox Mail Gateway

The first step in configuring Proxmox Mail Gateway for your Windows 2022 VM is to install the software. You can download the latest version of Proxmox Mail Gateway from the official website. Once the download is complete, follow the installation wizard to install the software on your server.

Download Proxmox Mail Gateway

Step 2: Configure Proxmox Mail Gateway

After installing Proxmox Mail Gateway, you'll need to configure it to work with your Windows 2022 VM. To do this, open the Proxmox Mail Gateway web interface and navigate to the "Configuration" tab. Here, you can configure various settings, including email filters, antivirus scanning, and spam detection.


Proxmox Mail Gateway Configuration:
https://your-proxmox-mail-gateway-ip-address:8006/

Step 3: Create an Email Route

To send email traffic from your Windows 2022 VM through Proxmox Mail Gateway, you'll need to create an email route. To do this, navigate to the "Email Routes" tab and click the "Add" button. In the "From" field, enter the IP address of your Windows 2022 VM. In the "To" field, enter the IP address of your Proxmox Mail Gateway server.


  Create an Email Route:

    From: your-windows-2022-vm-ip-address
    To: your-proxmox-mail-gateway-ip-address

Step 4: Configure Your Email Client

After configuring Proxmox Mail Gateway and creating an email route, you'll need to configure your email client to use the gateway. This will depend on the email client you're using, but most email clients allow you to specify an SMTP server. Enter the IP address of your Proxmox Mail Gateway server as the SMTP server, and your email client should be configured to use the gateway.


  SMTP Server Configuration:
  your-proxmox-mail-gateway-ip-address

Step 5: Test Your Configuration

Finally, it's important to test your configuration to ensure everything is working correctly. Send a test email from your Windows 2022 VM to an external email address, and check the Proxmox Mail Gateway logs to ensure the email was processed correctly. If everything looks good, you've successfully configured your Windows 2022 VM to use Proxmox Mail Gateway!


  Test Your Configuration:
  Send a test email from your Windows 2022 VM and check the Proxmox Mail Gateway logs.

Conclusion

In conclusion, configuring Proxmox Mail Gateway for your Windows 2022 VM can help you secure your email traffic and prevent spam and malware from entering your network.

Current PMG Version Note

The Windows Server relay steps still depend on a healthy Proxmox Mail Gateway. If your PMG server is still on 8.2, review the PMG 9.0 upgrade path before changing production mail flow.

2026 Support Update: Windows Server VM to Proxmox Mail Gateway Checklist

Current action path: Windows mail relay through PMG needs connector settings, relay permissions, TLS, DNS, queue evidence, and delivery tests after the change.

What to verify before production changes

  • Confirm mail routing, relay permissions, DNS, TLS, and quarantine behavior.
  • Back up mail-gateway or VM configuration before changing connectors or routes.
  • Verify inbound delivery, outbound delivery, queues, logs, and spam handling after the change.

Source-backed references and next reads

For support tickets, keep the exact system touched, backup timestamp, changed setting, public URL, and post-change verification result in the notes. That is the difference between a tutorial and an operational recovery path.