惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
博客园 - 司徒正美
Last Week in AI
Last Week in AI
Recent Announcements
Recent Announcements
Y
Y Combinator Blog
博客园 - 聂微东
M
MIT News - Artificial intelligence
博客园_首页
Jina AI
Jina AI
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
F
Fortinet All Blogs
aimingoo的专栏
aimingoo的专栏
小众软件
小众软件
Vercel News
Vercel News
The Cloudflare Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
云风的 BLOG
云风的 BLOG
N
Netflix TechBlog - Medium
B
Blog
Google DeepMind News
Google DeepMind News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
PMG sending emails out directly (not through Exchange ser...
invalid@exam · 2026-06-17 · via Proxmox Support Forum

Hi all. Rather new to PMG, and just set it up the other day and have begun testing and playing around with it in our environment. We have an on-prem Exchange server and the PMG sits in our DMZ/Perimeter network, and is used only for incoming email at the moment.

Put simply, any notifications (under Action Objects) where it notifies the sender (ie: for a blocked or rejected messages), PMG sends this notification out directly from itself; not through the downstream Exchange server.

This is a concern/issue, for many reasons.... many. But, I have to believe there is a configurable component somewhere to have PMG use the actual mail server (perhaps as a smart host) and not send out directly from itself? I cannot find anything in the GUI to accomplish this. Is there a way via the CLI to do so?

Thank you in advance.

I found it. You can in fact edit the pmg.conf file and add a smart host. One love.

This is a concern/issue, for many reasons.... many. But, I have to believe there is a configurable component somewhere to have PMG use the actual mail server (perhaps as a smart host) and not send out directly from itself? I cannot find anything in the GUI to accomplish this. Is there a way via the CLI to do so?

GUI->Configuration->Mail Proxy->Relaying->Smarthost

That being said - PMG is usually installed between the internet and the downstream server (Exchange in your case) - so relaying outbound through that Exchange sounds strange - Make sure you don't create a mail-loop

I hope this helps!

I also need the possibility to configure a output smart host to be able to also send outbound mails from the internal mail server via PMG. Currently outbound mail is the from the internal mail server directly via the providers smart host, so the virus filtering possibilities from PMG is lost.
Actually there are even several smart hosts for different domains, which should be supported by PMG. It is already possible for inbound mail, to configure different destinations according to the domain and the same should be possible for outbound mail.

Currently outbound mail is the from the internal mail server directly via the providers smart host, so the virus filtering possibilities from PMG is lost.

Not sure I understand that - for mails _from_ your mail-servers you need to configure those mail-servers to relay through PMG (then virus scanning/etc. are available) - from PMG to the internet you can either send directly (if your provider allows that) or configure a smarthost (the smarthost of your provider)...

Actually there are even several smart hosts for different domains, which should be supported by PMG. It is already possible for inbound mail, to configure different destinations according to the domain and the same should be possible for outbound mail.

Yes this is also possible for inbound mails - just add the domains to 'Relay Domains', and configure the appropriate 'Transport' entry (where the mail _for_ this domain should be sent to) ?

Not sure I understand that - for mails _from_ your mail-servers you need to configure those mail-servers to relay through PMG (then virus scanning/etc. are available) - from PMG to the internet you can either send directly (if your provider allows that) or configure a smarthost (the smarthost of your provider)...

Yes this is also possible for inbound mails - just add the domains to 'Relay Domains', and configure the appropriate 'Transport' entry (where the mail _for_ this domain should be sent to) ?

There is inbound routing per domain but still no outbound routing. Especially not route to different output smart hosts (depending on sending domain).