Unable to Relay mail from Zimbra to Proxmox Mail Gateway using internal port 26

Uzzal

New Member
Jul 28, 2023
9
0
1
I have two azure virtual machine.. one is Zimbra Mail Server and Another one is Proxmox mail gateway.

I have installed and configured properly as per my knowledge,

PROXMOX mail gateway server is refusing connection to port 26, external port 25 is ok !

i am trying to relay my mails from zimbra mail server which is in the same LAN, i.e. local/internal network. i am trying to telnet or send mail from zimbra to Proxmox mail gateway but proxmox is actively refusing connection on port 26. Please suggest what actually i am missing.

FYI, i have already deployed test environment on my local machine using hyper v , that test was successful..

the difference is that time i had installed proxmox mail gateway from the ISO file .. now i have proxmox VM on azure which is installed Above Debian Linux 12 using proxmox repositories.

I have attached some screens please have a look and suggest !
 

Attachments

  • esg1.png
    esg1.png
    61.5 KB · Views: 10
  • esg2.png
    esg2.png
    32.1 KB · Views: 10
  • esg3.png
    esg3.png
    32.6 KB · Views: 9
  • esg4.png
    esg4.png
    65.3 KB · Views: 9
  • esg5.png
    esg5.png
    39.4 KB · Views: 9
a) pmg-smtp-filter service is failed - so processing won't work
b) there is nothing listening on port 26 - how did you install the PMG - did you reboot at any point after the installation?
 
a) pmg-smtp-filter service is failed - so processing won't work
b) there is nothing listening on port 26 - how did you install the PMG - did you reboot at any point after the installation?
i have installed simply using debian repositories, previously i was able to get it work while installing from ISO.. but this time i am using Azure VM .. there i cant use ISO for installation, so just created Debian 12 VM and installed over it using apt repositories.

yes i have rebooted multiple times.. for service to run or apply my some settings.
 
check the journal after a reboot - share it if you don't find the problem...
 
please post the complete journal for the boot as text file:
* journalctl -b > journal-$(uname -n).txt

from the screenshot I see that you need to run sa-update at least (which ist still strange)

also post:
`pmgversion -v`
 
please post the complete journal for the boot as text file:
* journalctl -b > journal-$(uname -n).txt

from the screenshot I see that you need to run sa-update at least (which ist still strange)

also post:
`pmgversion -v`

Hi i have attached files please have a look .
 

Attachments

  • journal-ESG.txt
    145.6 KB · Views: 2
  • sa-update.png
    sa-update.png
    33.7 KB · Views: 4
  • versioninfo.png
    versioninfo.png
    22.1 KB · Views: 3

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!