Proxmox Mail Gateway with MailCow

[std]

Hi, i configured today mailcow Email with Proxmox, i can recive email with proxmox mailgateway but how i can config to send outgoing emails with proxmox mailgateway?

 

[mac.linux.free]

Hi really simple. But MailCow has a more efficient Spamfilter. So it is better to just use MailCow.

 

[std]

When i do this with port 26 then i can not send emails anymore?
What i do whrong?

 

[mac.linux.free]

You have to whitelist the cows ip in pmg

 

[std]

admin@domain.com (connect to smtpin.rzone.de[2a01:238:20a:202:50f0::1097]:26: Connection refused)

This fehler i have in queue manager, i cant send and i put my ip in white list on pmg?

 

[mac.linux.free]

why ipv6?

 

[std]

That's from ip from provider, from strato, I host my domain on strato, ip is sometimes ipv6 sometimes ipv4

 

[std]

This are my options in pmg, i changed only domain and ip

 

[std]

 

[std]

in MailCow i put pmg.domain.de:26 und now i cant sent any more emails?

 

[hata_ph]

is your mailcow email server running on port 26?

 

[hansgruber]

I have several domains that I service on my Mailcow server, of which 2 are aliased to the master (domain1 is the master; domain2 and domain3 are aliases).

My INTERNET-facing IP is 1.1.1.137 mail.junk.us is for PROXMOX; normally used junk.us for Mailcow.
My INTRANET-facing IP is 10.1.1.137
My PROXMOX IP is 10.1.1.136

I have a valid DKIM on domain1, domain2, and domain3. I already exchange emails via 10.1.1.137 out going through 1.1.1.137 - that works just OK.
However, I cannot seem to get INTO from 1.1.1.137 to 10.1.1.137 on port 26.

Mailcow has been setup to receive on port 26 via /opt/mailcow-dockerized/docker-compose.yml

root@srvr2017:/opt/mailcow-dockerized# docker ps | grep ":25"
2ca48b3d09f6 mailcow/postfix:1.66 "/docker-entrypoint.…" 13 minutes ago Up 13 minutes 0.0.0.0:465->465/tcp, :::465->465/tcp, 0.0.0.0:587->587/tcp, :::587->587/tcp, 588/tcp, 0.0.0.0:25->26/tcp, :::25->26/tcp

And within /opt/mailcow-dockerized/mailcow.conf

# You should leave that alone
# Format: 11.22.33.44:25 or 0.0.0.0:465 etc.
# Do _not_ use IPORT in HTTP(S)_BIND or HTTP(S)_PORT

SMTP_PORT=26
SMTPS_PORT=465
SUBMISSION_PORT=587
IMAP_PORT=143
IMAPS_PORT=993
POP_PORT=110
POPS_PORT=995
SIEVE_PORT=4190
DOVEADM_PORT=127.0.0.1:19991
SQL_PORT=127.0.0.1:13306


I have port 25 NAT'd from 1.1.1.137 to 10.1.1.137.
PROXMOX suggestings using port 26.

None of the above recommendations seem to work.

Help me Obi-Wan Kenobi.

 

[hata_ph]

I have several domains that I service on my Mailcow server, of which 2 are aliased to the master (domain1 is the master; domain2 and domain3 are aliases).

My INTERNET-facing IP is 1.1.1.137 mail.junk.us is for PROXMOX; normally used junk.us for Mailcow.
My INTRANET-facing IP is 10.1.1.137
My PROXMOX IP is 10.1.1.136

I have a valid DKIM on domain1, domain2, and domain3. I already exchange emails via 10.1.1.137 out going through 1.1.1.137 - that works just OK.
However, I cannot seem to get INTO from 1.1.1.137 to 10.1.1.137 on port 26.

Mailcow has been setup to receive on port 26 via /opt/mailcow-dockerized/docker-compose.yml

root@srvr2017:/opt/mailcow-dockerized# docker ps | grep ":25"
2ca48b3d09f6 mailcow/postfix:1.66 "/docker-entrypoint.…" 13 minutes ago Up 13 minutes 0.0.0.0:465->465/tcp, :::465->465/tcp, 0.0.0.0:587->587/tcp, :::587->587/tcp, 588/tcp, 0.0.0.0:25->26/tcp, :::25->26/tcp

And within /opt/mailcow-dockerized/mailcow.conf

# You should leave that alone
# Format: 11.22.33.44:25 or 0.0.0.0:465 etc.
# Do _not_ use IPORT in HTTP(S)_BIND or HTTP(S)_PORT

SMTP_PORT=26
SMTPS_PORT=465
SUBMISSION_PORT=587
IMAP_PORT=143
IMAPS_PORT=993
POP_PORT=110
POPS_PORT=995
SIEVE_PORT=4190
DOVEADM_PORT=127.0.0.1:19991
SQL_PORT=127.0.0.1:13306


I have port 25 NAT'd from 1.1.1.137 to 10.1.1.137.
PROXMOX suggestings using port 26.

None of the above recommendations seem to work.

Help me Obi-Wan Kenobi.

Pls open a new thread for your issue.