• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Can Mailcow Dockerized be made the main Mailserver on Plesk Obsidian + Debian 12 platform

bosse1

New Pleskian
Server operating system version Debian 12 Plesk version and microupdate number Plesk Obsidian 18.0.66


I have Plesk Obsidian 18.0.XX installed on a Debian 12 VPS with 32GB RAM and 240GB drive.
I would like Mailcow to take over all mail functions ( and remain closely tied to Plesk if possible). My installation so far gives me this error and indicates that I should disable the SMTP setting in Postfix.


Code:

Error response from daemon: driver failed programming external connectivity on endpoint mailcowdockerized-dovecot-mailcow-1 (4c6cf44559614df67738c64de0b91814342e5c562e836b8a11be82eccd8ca23c): failed to bind port 0.0.0.0:110/tcp: Error starting userland proxy: listen tcp4 0.0.0.0:110: bind: address already in use

Quoting from Mailcow Dockerized documentation:
@ Local MTA on Docker host - mailcow: dockerized documentation

The easiest option would be to disable the listener on port 25/tcp.


Postfix users disable the listener by commenting the following line (starting with smtp or 25) in /etc/postfix/master.cf:


#smtp inet n - - - - smtpd


Furthermore, to relay over a dockerized mailcow, you may want to add 172.22.1.1 as relayhost and remove the Docker interface from "inet_interfaces":


postconf -e 'relayhost = 172.22.1.1'
postconf -e "mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128"
postconf -e "inet_interfaces = loopback-only"
postconf -e "relay_transport = relay"
postconf -e "default_transport = smtp"


Now it is important to not have the same FQDN in myhostname as you use for your dockerized mailcow. Check your local (non-Docker) Postfix' main.cf for myhostname and set it to something different, for example local.my.fqdn.tld.


"172.22.1.1" is the mailcow created network gateway in Docker.Relaying over this interface is necessary (instead of - for example - relaying directly over ${MAILCOW_HOSTNAME}) to relay over a known internal network.


Restart Postfix after applying your changes.

2022-01-29 23:04:38

Click to expand...
I'm new to Plesk so;
  1. Can someone simplify the steps to achieve this in a step1, step2.. format?
  2. Would doing this remove all Plesk ability to set email accounts or would it work in tandem with Mailcow?
  3. What other Plesk services or utilities would be potentially impacted if taking this course?
  4. Is there a Plesk/Mailcow integration Howto/tutorial?
Thanks for any assistance.
 
Back
Top