mailcow / mailcow-dockerized-app

Clone of the mailcow-dockerized repo which contains extra services for CowUI.

⚠️ATTENTION⚠️

This repo is using for development purposes of CowUI. So do not use it instead of original mailcow-dockerized!

mailcow: dockerized - 🐮 + 🐋 = 💕

How can you run it?

• First you need to init submodules:

# Get the repo
git clone https://github.com/mailcow/mailcow-dockerized-app.git && cd mailcow-dockerized-app/

# Init submodules
git submodule init

# Get the latest commits
git submodule update --remote --recursive

• After that you need the create mailcow config and build CowUI services:

# Generate the config
./generate_config.sh

# Build necessary services images locally
docker-compose build cowui-backend-mailcow cowui-frontend-mailcow sync-engine-mailcow

• Last, pull remaining images and up the compose:

docker-compose pull 
docker-compose up -d

Want to support mailcow?

Please consider a support contract with Servercow to support further development. We support you while you support us. :)

You can also get a SAL which is a one-time payment with no liabilities or returning fees.

Or just spread the word: moo.

Info, documentation and support

Please see the official documentation for installation and support instructions. 🐄

🐛 If you found a critical security issue, please mail us to info at servercow.de.

Cowmunity

mailcow community

Telegram mailcow channel

Telegram mailcow Off-Topic channel

Telegram desktop clients are available for multiple platforms. You can search the groups history for keywords.

Misc

Important: mailcow makes use of various open-source software. Please assure you agree with their license before using mailcow. Any part of mailcow itself is released under GNU General Public License, Version 3.

mailcow-dockerized-app's Issues

sender dependent transport fails for individual email if domain is pointed to a different transport.

Prior to placing the issue, please check following: (fill out each checkbox with an X once done)

• [ x] I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue.
• [ x] I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
• [ x] I have understood that answers are voluntary and community-driven, and not commercial support.
• [ x] I have verified that my issue has not been already answered in the past. I also checked previous issues.

Summary

Logs

Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: match_string: smtp_sasl_mechanism_filter: plain ~? plain
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: match_string: smtp_sasl_mechanism_filter: login ~? plain
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: match_string: smtp_sasl_mechanism_filter: login ~? login
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: server features: 0x902f size 52428800
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: Using ESMTP PIPELINING, TCP send buffer size is 87040, PIPELINING buffer size is 4096
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: event_request_timer: reset 0x7f60c8ff1c80 0x5588fc9661f0 5
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: send attr request = lookup
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: send attr table = mysql:/opt/postfix/conf/sql/mysql_sasl_passwd_maps_sender_dependent.cf
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: send attr flags = 540736
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: send attr key = [email protected]
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: vstream_fflush_some: fd 14 flush 130
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: vstream_buf_get_ready: fd 14 got 82
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: private/proxymap socket: wanted attribute: status
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: input attribute name: status
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: input attribute value: 0
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: private/proxymap socket: wanted attribute: value
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: input attribute name: value
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: input attribute value: AWSUSER:AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: private/proxymap socket: wanted attribute: (list terminator)
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: input attribute name: (end)
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: dict_proxy_lookup: table=mysql:/opt/postfix/conf/sql/mysql_sasl_passwd_maps_sender_dependent.cf flags=lock|fold_fix|utf8_request key=[email protected] -> status=0 result=AWSUSER:AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: maps_find: smtp_sasl_password_maps: proxy:mysql:/opt/postfix/conf/sql/mysql_sasl_passwd_maps_sender_dependent.cf(0,lock|fold_fix|utf8_request): [email protected] = AWSUSER:AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: mail_addr_find: [email protected] -> AWSUSER:AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: smtp_sasl_passwd_lookup: host mail.smtp2go.com' user AWSUSER' pass `AWSPASS'
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: starting new SASL client
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: smtp_sasl_authenticate: mail.smtp2go.com[194.195.251.121]:2525: SASL mechanisms PLAIN LOGIN
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: xsasl_cyrus_client_get_user: AWSUSER
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: xsasl_cyrus_client_get_passwd: AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: xsasl_cyrus_client_first: uncoded initial reply: \000AWSUSER\000AWSPASS
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: > mail.smtp2go.com[194.195.251.121]:2525: AUTH PLAIN ASDFDGDSHDSHSDHSDJSJSDGAGSDHJHSDGADHDJFJFJDSHDSGSDJSJSFKFKGKDKDFKFDHFHSDH
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: vstream_fflush_some: fd 15 flush 101
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: vstream_buf_get_ready: fd 15 got 35
Dec 23 17:32:36 79df21555fa2 postfix/smtp[787]: < mail.smtp2go.com[194.195.251.121]:2525: 535 Incorrect authentication data

Reproduction

Set the domain to sender dependent transport of an SMTP provider with username and password.
Set an individual email in that domain to another sender dependent transport without a username and password.
Sending any email from that individual email will return SASL Authentication Failed.

Possible Fix

mysql_sasl_passwd_maps_sender_dependent.cf seems to have the SQL query's COALESCE parameters in the wrong order. flipping the parameters around seems to fix this, but I am not sure if that has any unintended consequences at other places.

System information

Question	Answer
My operating system	debian
Is Apparmor, SELinux or similar active?	no
Virtualization technlogy (KVM, VMware, Xen, etc - LXC and OpenVZ are not supported	VMware
Server/VM specifications (Memory, CPU Cores)	8GB,16
Docker Version (docker version)	20.10.22
Docker-Compose Version (docker-compose version)	2.14.1
Reverse proxy (custom solution)	NO

• Output of git diff origin/master, any other changes to the code? If so, please post them.
• All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat.
• DNS problems? Please run docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and post the output.