Hi, I've tried sending a mail, which came back as followed:

mx postfix/smtp[108]: CF6F54EA: to=[email protected], relay=none, delay=1292, delays=1289/0.1/3/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=brainfarmcinema.com type=MX: Host not found, try again)

The host can easily resolve the domain, but the postfix container cannot, probably through the pdns service.
Dig from Host:

dig mx brainfarmcinema.com
;; ANSWER SECTION:
brainfarmcinema.com. 84849 IN MX 5 ALT2.ASPMX.L.GOOGLE.com.
brainfarmcinema.com. 84849 IN MX 10 ALT3.ASPMX.L.GOOGLE.com.

Dig from PDNS-docker:

dig mx brainfarmcinema.com @172.22.1.254

; <<>> DiG 9.10.3-P4-Ubuntu <<>> mx brainfarmcinema.com @172.22.1.254
;brainfarmcinema.com. IN MX

Can you guys help me get this fixed?

(shortened the dig parts)

There are no shared ciphers for the current Docker builds of Dovecot and SOGo. Thus connection between SOGo and Dovecot fails.

SOGo logs:

9.1.2017 17:04:202017-01-09 17:04:20.510 sogod[49] ERROR(-[NGActiveSSLSocket startTLS]): couldn't setup SSL connection on socket (error:00000001:lib(0):func(0):reason(1))...
9.1.2017 17:04:20Jan 09 17:04:20 sogod [49]: <0x0x5606a7129560[NGImap4Client]> Could not start TLS.
9.1.2017 17:04:20Jan 09 17:04:20 sogod [49]: <0x0x5606a7129560[NGImap4Client]> ERROR(-[NGImap4Client _processUnknownCommandParserException:]): catched non-IMAP4 parsing exception NGStreamWriteErrorException: stream error occured, errno=9 error=Bad file descriptor
9.1.2017 17:04:20Jan 09 17:04:20 sogod [49]: [ERROR] <0x0x5606a7144ed0[NGImap4ConnectionManager]> IMAP4 login failed:

Dovecot logs:

9.1.2017 17:04:202017-01-09 16:04:20 imap-login: Error: SSL: Stacked error: error:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipher
9.1.2017 17:04:202017-01-09 16:04:20 imap-login: Info: Disconnected (no auth attempts in 0 secs): user=<>, rip=10.42.180.182, lip=10.42.99.68, TLS handshaking: SSL_accept() failed: Unknown error

Hi Andre,

As of this moment in the dev branch: mailbox users can't login to their account. It's a consistent Wrong username or password.

We're once again seeing a problem where I'm not sure if it has something to do with our local configuration or is a Mailcow issue. In case it is Mailcow related I'll post it anyways:

The primary domain of a user (mailcow login "[email protected]") has a couple of alias domains. For the alias domains the user now also has some aliases (one of it is "[email protected]"). In the user's mailbox "Do not check sender for domain primary-domain.com" is checked. There are no entries for alias-domain.com which could be checked (as expected as they should behave like the primary domain). Grayed out but checked there also is an entry "[email protected]".
However, when the users tries to send as "[email protected]" postfix won't let him with "Sender address rejected: not owned by user [email protected]".
I'm not sure if there are some entries missing in sender_acl or something but when I try to recreate the user there is the same problem.

Therefore I looked at the SQL in mysql_virtual_sender_acl.cf and that looked to me as it cannot work when the user tries to send with "[email protected]" and only "[email protected]" could work (but again, I'm not sure if there should be some other SQL besides mysql_virtual_sender_acl.cf which should take care of that...).
So the current SQL looks like this

SELECT goto
FROM alias
WHERE address='%s'
  AND active='1'
  AND domain IN
    (SELECT domain
     FROM domain
     WHERE domain='%d'
       AND active='1')
UNION
SELECT logged_in_as
FROM sender_acl
WHERE send_as='@%d'
  OR send_as='%s'
  AND logged_in_as NOT IN
    (SELECT goto
     FROM alias
     WHERE address='%s')
UNION
SELECT goto
FROM alias,
     alias_domain
WHERE alias_domain.alias_domain = '%d'
  AND alias.address = CONCAT('%u', '@', alias_domain.target_domain)
  AND alias.active ='1'
  AND alias_domain.active='1'

When I add two sub selects for the alias domains in the union select from sender_acl everything works for me. Here the now working SQL:

SELECT goto
FROM alias
WHERE address='%s'
  AND active='1'
  AND domain IN
    (SELECT domain
     FROM domain
     WHERE domain='%d'
       AND active='1')
UNION
SELECT logged_in_as
FROM sender_acl
WHERE send_as='@%d'
  OR send_as='%s'
  OR send_as IN
    ( SELECT CONCAT ("@",target_domain)
     FROM alias_domain
     WHERE alias_domain = '%d' )
  OR send_as IN
    ( SELECT CONCAT ("%u", "@",target_domain)
     FROM alias_domain
     WHERE alias_domain = '%d' )
  AND logged_in_as NOT IN
    (SELECT goto
     FROM alias
     WHERE address='%s')
UNION
SELECT goto
FROM alias,
     alias_domain
WHERE alias_domain.alias_domain = '%d'
  AND alias.address = CONCAT('%u', '@', alias_domain.target_domain)
  AND alias.active ='1'
  AND alias_domain.active='1'

The strange thing is the user with the problem is using GMail and was able to setup the problematic alias two or three weeks ago. So I guess this means it was working with the old SQL at some point but I also don't know how the GMail alias configuration is working...

// Edit: looking at the working SQL a second time I think it would ignore inactive aliases currently so I guess it would need a polishment regarding that matter ;-)

fresh mailcow docker install (pulled from git 1/2h ago) gets this log spam:

https://hastebin.com/uxexuqigit.go

any missing ssl flag in rspamd config? (didn't enabled the rspam webui )

Hi,

the initial build of all containers worked well, however when trying to build the sogo container again with

docker build data/Dockerfiles/sogo -t andryyy/mailcow-dockerized:sogo

I get the following error:

Running hooks in /etc/ca-certificates/update.d...
done.
--2017-03-01 20:27:31-- https://github.com/tianon/gosu/releases/download/1.9/gosu-amd64
Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
ERROR: no certificate subject alternative name matches
requested host name 'github.com'.
To connect to github.com insecurely, use `--no-check-certificate'.

Tried to delete sogo container, sogo image, docker pull andryyy/mailcow-dockerized:sogo, all without success.

Also tried the suggested option --no-check-certificate and as well using curl, but then I will get other errors. So I assume, anything has been currupted ... Any ideas?

install mailcow-dockerized without sogo and use roundcube instead?

I get an exception for imap.ro0kie.de:143. Do I need to add smtp and imap to the certbot script aswell? So they are covered by the certificate.

Thanks

Hi, are there any plans for ClamAV integration or some sort of diffrent antivirus?

Hi,

I'm stucked at login screen.
How can change the admin password at Mailcow Docker version?
The old password change methods don't work.

Please let me know.
Thanks.

Great work.

Hello,
I want to remove sogo since i don't use it, how do i remove it completely
Thanks,
Hitogami

How can i disable unnecessary services: imap_143, pop3_110, pop3s_995, smtps_465 ?
I only need the following services: smtp_25, submission_587, imap_993.

From the container startup logs:

9.1.2017 16:10:432017-01-09 15:10:43,377 CRIT Supervisor running as root (no user in config file)
9.1.2017 16:10:432017-01-09 15:10:43,387 INFO supervisord started with pid 1
9.1.2017 16:10:442017-01-09 15:10:44,390 INFO spawned: 'postfix' with pid 13
9.1.2017 16:10:442017-01-09 15:10:44,399 INFO spawned: 'postfix-maillog' with pid 14
9.1.2017 16:10:442017-01-09 15:10:44,403 INFO spawned: 'syslog-ng' with pid 16
9.1.2017 16:10:442017-01-09 15:10:44,417 INFO exited: postfix-maillog (exit status 1; not expected)
9.1.2017 16:10:452017-01-09 15:10:45,418 INFO success: postfix entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
9.1.2017 16:10:452017-01-09 15:10:45,421 INFO spawned: 'postfix-maillog' with pid 97
9.1.2017 16:10:452017-01-09 15:10:45,422 INFO success: syslog-ng entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[85]: warning: group or other writable: /usr/lib/postfix/./libpostfix-dns.so.1
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[86]: warning: group or other writable: /usr/lib/postfix/./sbin/lmtp
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[87]: warning: group or other writable: /usr/lib/postfix/./libpostfix-util.so.1
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[88]: warning: group or other writable: /usr/lib/postfix/./libpostfix-global.so.1
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[89]: warning: group or other writable: /usr/lib/postfix/./libpostfix-master.so.1
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[90]: warning: group or other writable: /usr/lib/postfix/./libpostfix-tls.so.1
9.1.2017 16:10:45Jan  9 15:10:45 mail postfix/postfix-script[91]: warning: group or other writable: /usr/lib/postfix/sbin/./lmtp

You might want look into using another user for postfix via the docker USER command to adhere to the principle of least priviledges.

Hello

I can't receive mail from Gmail and Vimeo :-)

Postfix logs:

postfix-mailcow_1    | Feb 15 22:22:54 mx postfix/smtpd[168]: connect from unknown[74.113.233.227]
postfix-mailcow_1    | Feb 15 22:22:55 mx postfix/smtpd[168]: Anonymous TLS connection established from unknown[74.113.233.227]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
postfix-mailcow_1    | Feb 15 22:22:55 mx postfix/smtpd[168]: NOQUEUE: reject: RCPT from unknown[74.113.233.227]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [74.113.233.227]; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<smtp.vimeo.com>
postfix-mailcow_1    | Feb 15 22:22:56 mx postfix/smtpd[168]: disconnect from unknown[74.113.233.227] ehlo=2 starttls=1 mail=1 rcpt=0/1 data=0/1 rset=1 quit=1 commands=6/8

postfix-mailcow_1    | Feb 15 22:23:01 mx postfix/smtpd[170]: Anonymous TLS connection established from unknown[209.85.220.193]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
postfix-mailcow_1    | Feb 15 22:23:01 mx postfix/smtpd[170]: NOQUEUE: reject: RCPT from unknown[209.85.220.193]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [209.85.220.193]; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mail-qk0-f193.google.com>
postfix-mailcow_1    | Feb 15 22:23:01 mx postfix/smtpd[170]: disconnect from unknown[209.85.220.193] ehlo=2 starttls=1 mail=1 rcpt=0/1 data=0/1 quit=1 commands=5/

Since one of the more recent updates (probably somewhen between 22. Dec till now) SOGo authentication isn't possible anymore. I'm not sure what the problem is. This is are the warnings and errors from the sogo.log:

sogo-mailcow_1       | ==> /var/log/sogo/sogo.log <==
sogo-mailcow_1       | Dec 28 15:58:38 sogod [53]: [ERROR] |SOGo| No value specified for 'SOGoProfileURL'
sogo-mailcow_1       | Dec 28 15:58:38 sogod [53]: <0x0x562923661910[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow_1       | Dec 28 15:58:38 sogod [60]: [ERROR] |SOGo| No value specified for 'SOGoProfileURL'
sogo-mailcow_1       | Dec 28 15:58:38 sogod [60]: <0x0x562923661910[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow_1       | Dec 28 15:58:38 sogod [55]: [ERROR] |SOGo| No value specified for 'SOGoProfileURL'
sogo-mailcow_1       | Dec 28 15:58:38 sogod [55]: <0x0x562923661910[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow_1       | Dec 28 15:58:38 sogod [56]: [ERROR] |SOGo| No value specified for 'SOGoProfileURL'
sogo-mailcow_1       | Dec 28 15:58:38 sogod [54]: [ERROR] |SOGo| No value specified for 'SOGoProfileURL'
sogo-mailcow_1       | Dec 28 15:58:38 sogod [56]: <0x0x562923661910[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow_1       | Dec 28 15:58:38 sogod [54]: <0x0x562923661910[WOHttpAdaptor]> notified the watchdog that we are ready
sogo-mailcow_1       | 2016-12-28 15:58:40,542 INFO success: sogo-syslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

sogo-mailcow_1       | ==> /var/log/sogo/sogo.log <==
sogo-mailcow_1       | 2016-12-28 15:59:09.791 sogod[47] Warning ... someone broke our lock (/var/lib/sogo/GNUstep/Defaults/.lck/.GNUstepDefaults.lck) ... and may have interfered with updating defaults data in file.

sogo-mailcow_1       | ==> /var/log/sogo/sogo.log <==
sogo-mailcow_1       | Dec 28 16:01:27 sogod [54]: <0x0x562923734780[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
sogo-mailcow_1       | Dec 28 16:01:27 sogod [54]: <0x0x562923734780[SOGoCache]> Using host(s) 'memcached' as server(s)
sogo-mailcow_1       | Dec 28 16:01:27 sogod [54]: [WARN] <0x0x7f6945e26820[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder
sogo-mailcow_1       | Dec 28 16:01:27 sogod [54]: [ERROR] <0x0x562923a5c990[SOGoUserManager]> No authentication sources defined - nobody will be able to login. Check your defaults.
sogo-mailcow_1       | Dec 28 16:01:27 sogod [54]: [ERROR] <0x0x562923a4ec40[SOGoSQLUserProfile]> failed to acquire channel for URL: (null)

There is a /var/lib/sogo/GNUstep/Defaults/sogod.plist file in the container which seems to have the correct entries but I'm not sure if they have the correct format/are used correctly:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//GNUstep//DTD plist 0.9//EN" "http://www.gnustep.org/plist-0_9.xml">
<plist version="0.9">
<dict>
    <key>OCSAclURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_acl</string>
    <key>OCSCacheFolderURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_cache_folder</string>
    <key>OCSEMailAlarmsFolderURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_alarms_folder</string>
    <key>OCSFolderInfoURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_folder_info</string>
    <key>OCSSessionsFolderURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_sessions_folder</string>
    <key>OCSStoreURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_store</string>
    <key>SOGoProfileURL</key>
    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_user_profile</string>
    <key>SOGoTimeZone</key>
    <string>"Europe/Berlin"</string>
    <key>domains</key>
    <dict>
        <key>testdomain.de</key>
        <dict>
            <key>SOGoMailDomain</key>
            <string>testdomainpde</string>
            <key>SOGoUserSources</key>
            <array>
                <dict>
                    <key>MailFieldNames</key>
                    <array>
                        <string>aliases</string>
                        <string>ad_aliases</string>
                        <string>senderacl</string>
                    </array>
                    <key>KindFieldName</key>
                    <string>kind</string>
                    <key>MultipleBookingsFieldName</key>
                    <string>multiple_bookings</string>
                    <key>IMAPLoginFieldName</key>
                    <string>c_uid</string>
                    <key>canAuthenticate</key>
                    <string>YES</string>
                    <key>displayName</key>
                    <string>GAL</string>
                    <key>id</key>
                    <string>testdomain.de</string>
                    <key>isAddressBook</key>
                    <string>YES</string>
                    <key>type</key>
                    <string>sql</string>
                    <key>userPasswordAlgorithm</key>
                    <string>ssha256</string>
                    <key>viewURL</key>
                    <string>mysql://mailcow:myTestPw@mysql:3306/mailcow/sogo_view_testdomainpde</string>
                </dict>
            </array>
        </dict>
    </dict>
</dict>
</plist>

The file /var/lib/sogo/GNUstep/Defaults/.lck/.GNUstepDefaults.lck doesn't seem to exist in the container.

Any ideas?

PS: I thought packing stuff like that in issues here is meanwhile probably better then using https://github.com/andryyy/mailcow/issues/68 ;-)

I'm having the issue that local mail delivery is failing from the SOGO web interface. That is:
Sending an email from [email protected] to [email protected] fails.
Postfix logs:

23.1.2017 17:42:50Jan 23 16:42:50 mail postfix/smtpd[108]: connect from unknown[10.42.180.182]
23.1.2017 17:42:51Jan 23 16:42:50 mail postfix/smtpd[108]: NOQUEUE: reject: RCPT from unknown[10.42.180.182]: 550 5.7.1 Session encryption is required; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<b52e11ec773f>
23.1.2017 17:42:51Jan 23 16:42:50 mail postfix/smtpd[108]: disconnect from unknown[10.42.180.182] ehlo=1 auth=1 mail=1 rcpt=0/1 quit=1 commands=4/5

Sogo logs:

Jan 23 17:55:58 sogod [50]: <0x0x563fcedfc130[SOGoMailer]> error with recipient '[email protected]'

It is possible to send and receive any kind of email using an external email client such as Thunderbird and it is also possible to send any kind of email to external domains using the Sogo client.

I am relatively certain that the issue is that Sogo is using smtp authentication only for external domains and is trying to deliver local messages without authentication. Hopefully it is possible to enable authentication for local delivery in the Sogo options. Otherwise postfix could be configured to allow relaying from "my_networks" without authentication.

Logs:

`sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: |SOGo| starting method 'POST' on uri '/SOGo/connect'
sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: <0x0x56176e01bae0[SOGoCache]> Cache cleanup interval set every 300.000000 seconds
sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: <0x0x56176e01bae0[SOGoCache]> Using host(s) 'memcached' as server(s)

sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: [WARN] <0x0x7ff6533ed820[WOxElemBuilder]> could not locate builders: WOxExtElemBuilder,WOxExtElemBuilder

sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: [ERROR] <0x0x56176e334250[SOGoUserManager]> No authentication sources defined - nobody will be able to login. Check your defaults.

sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: SOGoRootPage Login from '37.201.192.192' for user 'admin' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0

sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: |SOGo| request took 0.027754 seconds to execute

sogo-mailcow_1 | Dec 26 12:42:45 sogod [30]: 37.201.192.192 "POST /SOGo/connect HTTP/1.0" 403 34/58 0.032 - - 8M
`

default config files for sogo used.

followed instruction except had to install docker-compose via pip due to the github links not working. ... after running: docker-compose up -d from within the mailcow-dockerized folder with a dock-compose.yml file it returns blank and does nothing ...

Hi,

I've added a domain via the admin panel. Everything looked good. Then I wanted to increase the quota for this domain and I received the following error message:

MySQL: PDOException: SQLSTAE[HY093]: Invalid parameter number in /web/inc/functions.inc.php:3452 Stack trace: #0 /web/inc/functions.inc.php(3452): PDOStatement->execute(Array) #1 /web/inc/triggers.inc.php(143): mailbox_edit_domain(Array) #2 /web/inc/prerequisites.inc.php(95): require_once('/web/inc/trigge...') #3 /web/mailbox.php(2): require_once('web/inc/prereq...') #4 {main}

If I now want to change any Domain, a white page appears with only the number 3072.

Thanks for your help.

Hey @andryyy

Nice to see you working on a Docker version!
Just a few questions as I'm not that familiar with Docker;

• I saw you aren't using a data container for the website nor the ssl-certs, is there a reason for this?
  (https://github.com/miclnl/mailcow-dockerized/commit/4b2f522aceee9d5a6771ea34c7ac9b54c0762ef6)
• Would you object to adding the certbot image to also integrate Let's Encrypt in the image?
• Is it possible to add Fail2ban to the docker image, with the docker networking and all?

Regards, Michel

Hi Andre,

first of all I would like to thank you for your work putting mailcow into Docker containers!

I have some trouble configuring postfix to use a SMTP relay service.

In data/conf/postfix/main.cf I put the configuration

relayhost = myrelayhost :wqsmtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/opt/postfix/conf/sasl_passwd smtp_sasl_security_options = noanonymous, noplaintext smtp_sasl_tls_security_options = noanonymous

The credentials are located in the given sasl_password file, I also used postmap postmap /etc/postfix/sasl_passwd and restarted everything.

Unfortunately in the logs is something like
postfix-mailcow_1 | Jan 22 12:47:11 mailcow postfix/smtp[126]: Anonymous TLS connection established to smtp-ovhfr10.mailjet.com[5.196.43.129]:587: TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bit s) postfix-mailcow_1 | Jan 22 12:47:12 mailcow postfix/smtp[126]: warning: SASL authentication failure: No worthy mechs found

I know this post is a copy of https://forum.mailcow.email/t/docker-smtp-relay-postfix-configuration/292 but I really need some guidiance here.

Thank you in advance,
Christoph

Any plans for bringing Roundcube into the dockerized stack?

I'd like to use mc-d in front of an Exchange server. A few issues come to mind.

-) it's great we can already accept mail for * or just define a list of users. Pity we have to create a 'fake' list of mailboxes that will just clutter the interface.

What i'm missing is a way to define the final destination for the mail. ATM you must have it as a lower valor MX, but if it's installed on the internal network, or on a different port, or multihomed mc-d just don't work. Maybe i could try to modify postfix config, but i don't know how, and last time i changed a config I had problems merging changes back when updating mc-d.

What i'd like to see is an easier way to define a list of mailboxes to accept email for, and a list (maybe structured like exim's HUBBED_HOSTS) where it's possible to define multiple destinations and ports. ie:

domain.name: first.destinati.on::25:other.intern.al::3025

after loggin in SOGo i don't see the folder list, but using chrome developer tools i see this error:
/SOGo.woa/WebServerResources/js/vendor/angular.min.js:122
Possibly unhandled rejection: {"data":null,"status":-1,"config":{"method":"POST","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"/SOGo/so/marco@[MUNGED].it/Mail/0/folderINBOX/expunge","headers":{"Accept":"application/json, text/plain, */*","X-XSRF-TOKEN":"7a20992da2bf095c643c39cf5d8c477d077999da"}},"statusText":""}

and the mailbox list is not displayed correctly : http://imgur.com/tuKwQeV

Hi,

I tested the dkmi signature with sending a mail to [email protected]. When doing this via SOGo's webmail, dkim result is passed. When doing this via email client (port 587 smtp), the message is not signed.

What could be the reason?

I'm not sure if we can change the following behavior from the mailcow side or if we need to change SOGo itself. But the following case in a setup with multiple domains and users with aliases from multiple domains is not ideal:

When you have a user with the main address [email protected] and an alias [email protected] his default From field in SOGo will be [email protected] <[email protected]>. When SOGo's configuration allows the user to change his name he can set it to User for example which changes the SOGo From to User <[email protected]>. However SOGo only does this for the main address and leaves all alias addresses with a From field like [email protected] <[email protected]> and the user has no way to change this.
So his username is always revealed when sends from alias domains and most people don't want that. It would be better if the user defined name would be used for all aliases and not only the main domain. And it would be even better if it would be a freely editable field which can be changed for every outgoing mail.

How is this username <alias> list SOGo is using generated? And can we change it in mailcow?

Thanks for looking into it.

What DNS records should be set up to ensure best functionality?

Hi

How to enable "redirect http to https"?

I didn't get attention on forums so I am going to open an issue about this here

I am running a debian 8 server with several services and pulled the most recent mailcow-dockerized. During the setup I encountered the following errors:

ERROR: for postfix-mailcow  Cannot start service postfix-mailcow: driver failed programming external     connectivity on endpoint mailcowdockerized_postfix-mailcow_1: Error starting userland proxy: listen tcp 0.0.0.0:25: bind: address already in use

ERROR: for nginx-mailcow  Cannot start service nginx-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_nginx-mailcow_1: Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use

Obviously exim4 is installed on the server blocking port 25. Easy to fix if I simply remove it (but what to use for internal mails then?)

For 443 nginx is installed on my server which I need as the reverse proxy for my services... I was hoping I could use the dockerized mailcow without having to mess with my existing system. This was one of the reasons I tried to dockerize it with a friend (but we didn't know about docker networks back then)...

Any ideas how to handle the 443 conflict? Thought about using a different port but I don't know if this would mess up something else.

I am looking forward to hearing from you.

Best regards

steps done:

1. fresh pulled docker images. recreated container&volumes
2. added domain & restarted sogo via webui
3. added test mailbox (no sogo restart)
4. logged 1st time into sogo
   log shows:

sogo-mailcow_1 | Dec 29 21:48:17 sogod [85]: [ERROR] <0x0x55fff2699d00[SOGoSQLUserProfile]> could not run SQL 'INSERT INTO sogo_user_profile (c_uid, c_settings) VALUES ('[email protected]', '{"Calendar": {}}')': <MySQL4Exception: 0x55fff28e48a0> NAME:ExecutionFailed REASON:Duplicate entry '[email protected]' for key 'PRIMARY'

sogo restart required after adding a mailbox too ? (instead of "after domain adding " only )

edit: even after "add mailbox & restart sogo" the error is still present in sogo log

Hi Andre,
It would be awesome if administrators can create a mailbox with unlimited quota. 😄

Hello,

I recently installed mail cow on my VPS box and I getting this error message all the time after when I try to send an email to an address under the mailcow system. I have also found perhaps the source of the problem here:

Attaching to mailcowdockerized_pdns-mailcow_1
pdns-mailcow_1 | Mar 03 16:24:00 PowerDNS Recursor 4.0.4 (C) 2001-2016 PowerDNS.COM BV
pdns-mailcow_1 | Mar 03 16:24:00 Using 64-bits mode. Built using gcc 5.4.0 20160609 on Jan 13 2017 09:37:53 by root@2e330ddb85a7.
pdns-mailcow_1 | Mar 03 16:24:00 PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
pdns-mailcow_1 | Mar 03 16:24:00 Reading random entropy from '/dev/urandom'
pdns-mailcow_1 | Mar 03 16:24:00 If using IPv6, please raise sysctl net.ipv6.route.max_size, currently set to 4096 which is < 16384
pdns-mailcow_1 | Mar 03 16:24:00 NOT using IPv6 for outgoing queries - set 'query-local-address6=::' to enable
pdns-mailcow_1 | Mar 03 16:24:00 Only allowing queries from: 127.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8
pdns-mailcow_1 | Mar 03 16:24:00 Will not send queries to: 10.0.0.0/8, 100.64.0.0/10, 169.254.0.0/16, 192.168.0.0/16, 172.16.0.0/12, ::1/128, fc00::/7, fe80::/10, 0.0.0.0/8, 192.0.0.0/24, 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, 240.0.0.0/4, ::/96, ::ffff:0:0/96, 100::/64, 2001:db8::/32, 0.0.0.0, ::
pdns-mailcow_1 | Mar 03 16:24:00 PowerDNS Recursor itself will distribute queries over threads
pdns-mailcow_1 | Mar 03 16:24:00 Redirecting queries for zone 'mailcow-network.' with recursion to: 127.0.0.11:53
pdns-mailcow_1 | Mar 03 16:24:00 Inserting rfc 1918 private space zones
pdns-mailcow_1 | Mar 03 16:24:00 Listening for UDP queries on 0.0.0.0:53
pdns-mailcow_1 | Mar 03 16:24:00 Enabled TCP data-ready filter for (slight) DoS protection
pdns-mailcow_1 | Mar 03 16:24:00 Listening for TCP queries on 0.0.0.0:53
pdns-mailcow_1 | Mar 03 16:24:00 Set effective group id to 106
pdns-mailcow_1 | Mar 03 16:24:00 Set effective user id to 105
pdns-mailcow_1 | Mar 03 16:24:00 Launching 3 threads
pdns-mailcow_1 | Mar 03 16:24:00 Done priming cache with root hints
pdns-mailcow_1 | Mar 03 16:24:00 Done priming cache with root hints
pdns-mailcow_1 | Mar 03 16:24:00 Done priming cache with root hints
pdns-mailcow_1 | Mar 03 16:24:00 Enabled 'epoll' multiplexer
pdns-mailcow_1 | Mar 03 16:24:08 Failed to update . records, got an exception
pdns-mailcow_1 | Mar 03 16:24:08 Failed to update . records, RCODE=-1
pdns-mailcow_1 | Mar 03 16:24:09 Failed to update . records, got an exception

For some reason the pdns-recursor cannot fetch the root DNS zones ?

Any ideas ?

Hi,
I want to update my Docker images.

After docker-compose pull I get the following error message:

Feb 28 18:46:59 example dockerd[545]: time="2017-02-28T18:46:59.326883465+01:00" level=error msg="Not continuing with pull after error: manifest unknown: manifest unknown" Feb 28 18:46:59 example dockerd[545]: time="2017-02-28T18:46:59.327114925+01:00" level=error msg="Handler for POST /v1.24/images/create returned error: manifest unknown: manifest unknown" Feb 28 18:49:42 example dockerd[545]: time="2017-02-28T18:49:42.837110254+01:00" level=error msg="Attempting next endpoint for pull after error: manifest unknown: manifest unknown" Feb 28 18:49:42 example dockerd[545]: time="2017-02-28T18:49:42.837289553+01:00" level=info msg="Translating \"manifest unknown: manifest unknown\" to \"manifest for mariadb:10.1 not found\"" Feb 28 18:49:42 example dockerd[545]: time="2017-02-28T18:49:42.837355184+01:00" level=error msg="Handler for POST /v1.24/images/create returned error: manifest for mariadb:10.1 not found"

Maybe you can help me?

Thanks!

mailcow.conf

MAILCOW_HOSTNAME=mail.finogeeks.club

Jan 23 03:18:42 mail postfix/postscreen[110]: CONNECT from [220.181.15.61]:1201 to [172.22.1.6]:25
Jan 23 03:18:42 mail postfix/dnsblog[114]: addr 220.181.15.61 listed by domain hostkarma.junkemailfilter.com as 127.0.0.3
Jan 23 03:18:42 mail postfix/postscreen[110]: PASS OLD [220.181.15.61]:1201
Jan 23 03:18:42 mail postfix/smtpd[116]: connect from m15-61.126.com[220.181.15.61]
Jan 23 03:18:42 mail postfix/smtpd[116]: 8A05B52C: client=m15-61.126.com[220.181.15.61]
Jan 23 03:18:42 mail postfix/cleanup[107]: 8A05B52C: message-id=[email protected]
Jan 23 03:18:46 mail postfix/qmgr[101]: 8A05B52C: from=[email protected], size=2169, nrcpt=1 (queue active)
Jan 23 03:18:46 mail postfix/local[108]: 8A05B52C: to=[email protected], relay=local, delay=4.4, delays=4.4/0/0/0, dsn=5.1.1, status=bounced (unknown user: "yangtao")
Jan 23 03:18:46 mail postfix/cleanup[107]: D797C52E: message-id=[email protected]
Jan 23 03:18:46 mail postfix/bounce[109]: 8A05B52C: sender non-delivery notification: D797C52E
Jan 23 03:18:46 mail postfix/qmgr[101]: D797C52E: from=<>, size=4526, nrcpt=1 (queue active)
Jan 23 03:18:46 mail postfix/qmgr[101]: 8A05B52C: removed
Jan 23 03:18:46 mail postfix/smtpd[116]: disconnect from m15-61.126.com[220.181.15.61] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 23 03:18:52 mail postfix/smtp[118]: Trusted TLS connection established to 126mx03.mxmail.netease.com[220.181.15.191]:25: TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)
Jan 23 03:18:52 mail postfix/smtp[118]: D797C52E: to=[email protected], relay=126mx03.mxmail.netease.com[220.181.15.191]:25, delay=5.6, delays=0/0.02/5.2/0.37, dsn=2.0.0, status=sent (250 Mail OK queued as mx11,v8mowAAHexUadoVYpByGDA--.39512S3 1485141532)
Jan 23 03:18:52 mail postfix/qmgr[101]: D797C52E: removed

Hi,

when i setup bindings to an specifc ip this works for all containers except nginx-mailcow.

ERROR: The Compose file './docker-compose.yml' is invalid because: services.nginx-mailcow.ports is invalid: Invalid port "10.10.10.10:443:10.10.10.10:443", should be [[remote_ip:]remote_port[-remote_port]:]port[/protocol]

I think line 221 in docker-compose.yml is wrong
- "${HTTPS_PORT:-443}:${HTTPS_PORT:-443}"

i changed it to

- "${HTTPS_PORT:-443}:443"

but now nginx refuces to bind:

nginx: [emerg] bind() to 10.10.10.10:443 failed (99: Cannot assign requested address)

I think part of the problem is my lack of knowledge about docker ;)

(Real ip adress host ist configured to replaced with 10.10.10.10)

Hi,

I can not log in to Sogo anymore, a few days ago it still worked. I get the message "Wrong username or wrong password". Both are definitely correct.

Sogo Log:
Feb 03 14:30:37 sogod [2092]: SOGoRootPage Login from '188.117.155.136' for user '[email protected]' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0

Thanks

Dev Branch

You include the nginx config file /etc/nginx/conf.d/listen.active here https://github.com/andryyy/mailcow-dockerized/blob/master/data/conf/nginx/site.conf#L3 but it is actually not in the repository, leading to errors like

31.1.2017 17:24:052017/01/31 16:24:05 [emerg] 1#1: open() "/etc/nginx/conf.d/listen.active" failed (2: No such file or directory) in /etc/nginx/conf.d/site.conf:3
31.1.2017 17:24:05nginx: [emerg] open() "/etc/nginx/conf.d/listen.active" failed (2: No such file or directory) in /etc/nginx/conf.d/site.conf:3

Hello,

I just tried to install mailcow-dockerized with your tutorial, and When I run command docker-compose up -d

I get this Error:

ERROR: for postfix-mailcow  Cannot start service postfix-mailcow: driver failed programming external connectivity on endpoint mailcowdockerized_postfix-mailcow_1 (ea59ac85710ca5f233424ae0379ff60a4979f4986cf7ffa76f0d3435051e7682): Error starting userland proxy: listen tcp 0.0.0.0:25: bind: address already in use
ERROR: Encountered errors while bringing up the project.
root@MailServer:/home/mailcow-dockerized#

As I said, its just installed Debian 8 on VMware.

Output from netstat -pna | grep 25:

tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      723/exim4
tcp6       0      0 ::1:25                  :::*                    LISTEN      723/exim4
tcp6       0      0 :::995                  :::*                    LISTEN      8825/docker-proxy
unix  3      [ ]         STREAM     SPOJEN        12254    456/rpc.idmapd
unix  3      [ ]         STREAM     SPOJEN        12255    456/rpc.idmapd

I can provide you any other information you need, thanks for your help :)

`

getting the following error in rspamd (normal mail functions are working as expected):

'rspamd-mailcow_1 | 2016-12-31 13:04:37 #8(normal) <35rhob>; map; rspamd_map_file_read_callback: rereading map file /etc/rspamd/local.d/mid.inc
rspamd-mailcow_1 | 2016-12-31 13:04:37 #8(normal) <35rhob>; map; read_map_file: map file is unavailable for reading'

is this missing file required or optional for rspamd ?

Hello,

my host has crashed. Now I get the following error message: 2017-02-23 07:06:28 master: Fatal: Dovecot is already running with PID 31 (read from /var/run/dovecot/master.pid).

Can i delete the pid-file? If so, how do i do this in the container?

Thanks in advance

Not sure where this is stored but the queue folder should be persisted on a data or host volume in order to survive container upgrades.
At the moment anything that has not yet been delivered will silently be lost.

I deleted all images and the git folder and installed it again. Don't ask why ;)

Now I get this error:

Warning: Cannot modify header information - headers already sent by (output started at /web/inc/prerequisites.inc.php:46) in /web/inc/prerequisites.inc.php on line 51

Fatal error: Uncaught Error: Call to a member function prepare() on null in /web/inc/functions.inc.php:68 Stack trace: #0 /web/inc/prerequisites.inc.php(96): init_db_schema() #1 /web/index.php(2): require_once('/web/inc/prereq...') #2 {main} thrown in /web/inc/functions.inc.php on line 68

Does anyone know why I get this?

If i understand it correctly an item on a user's whitelist should get a MAILCOW_MOO symbol with a -999 score. This however doesn't work for us and unfortunately I currently cannot say why.

From the nginx-mailcow log I know that rspamd-mailcow is querying http://nginix:8081/settings.php on (re)start and when I query http://[nginx-container-ip]:8081/settings.php from the host with curl the output looks good. The apparently ignored from line of the user in question looks like this:

from = "/(.*@googlemail.com|.*@gmail.com|.*@googlemail.com.*|.*@gmail.com.*)/";

Still the MAILCOW_MOO symbol for Mails from GMail is 0.00.

Any ideas?

I found in my logs many entries about rejected connections.

Feb 7 07:04:38 mail postfix/smtpd[4113]: NOQUEUE: reject: RCPT from r67.web.sophos.com[207.211.34.67]: 550 5.7.1 Session encryption is required; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<r67.web.sophos.com>

I'm absolutely for encryption! But is it meaningful to prescribe the smtp encryption mandatory, if the mailserver is used productive?

Could I solve this problem by simply changing the following value in smtp_tls_security_level = may?

Thanks!

Hello,

I have a little problem. I switched from mailcow to mailcow-dockerized because I saw it's recommended.
With mailcow Gitlab was automatically sending the emails but with mailcow-dockerized this is not functional. What I have to do?

Thanks,
felixoi

I get error

Warning: include_once(inc/vars.local.inc.php): failed to open stream: No such file or directory in /web/autodiscover.php on line 28

Warning: include_once(): Failed opening 'inc/vars.local.inc.php' for inclusion (include_path='.:/usr/local/lib/php') in /web/autodiscover.php on line 28

Warning: Cannot modify header information - headers already sent by (output started at /web/autodiscover.php:28) in /web/autodiscover.php on line 42

Warning: Cannot modify header information - headers already sent by (output started at /web/autodiscover.php:28) in /web/autodiscover.php on line 43

Hi,

first, thank you for your great work!

Can I always update without hesitation, if I stick to your rules (https://mailcow.email/dockerized/?c=I.%20Installation&p=Update_mailcow_dockerized.md)? Or do I have to pay attention to something?

Thanks!

When I try to save the settings in Sogo. I get an : "Connection error"