kvaps
commented
7 years ago Confirmed, this is because guam.service is not properly up. Unfortunately I have no time to find the cause of this bug. I will be glad of any help from the outside :)
Open kevinbader opened 7 years ago
kvaps
commented
7 years ago Confirmed, this is because guam.service is not properly up. Unfortunately I have no time to find the cause of this bug. I will be glad of any help from the outside :)
kevinbader
commented
7 years ago Thanks for pointing out Guam, I hadn't noticed the error. Turned out that the Cyrus port is configured to 9993 instead of 993, the same port Guam uses, so that was an easy fix. That's what I've changed so far:
At this point user login in Rouncube works again, and I can view my mails. However, (sending and) ~receiving~ delivering mails still doesn't. In /var/log/maillog I see the mails coming in, but Postfix cannot deliver it saying status=deferred (mail transport unavailable). Any ideas?
btw, I also see connect to transport private/smtp-amavis: Connection refused in the log even though Amavis is up and running, but I'm not sure whether this affects the mail transport or not.
EDIT: do we need saslauthd? It doesn't run by default. At least the default submission config in postfix' master.cf has -o smtpd_sasl_auth_enable=yes in it.
kvaps
commented
7 years ago Hi @kevinbader, thanks for investigation!
About status=deferred (mail transport unavailable), I think this is because postfix cannot connect to amavis (or wallace). This address is listed in content_filter option in mater.cf
buhaha
commented
7 years ago
- set cyrus imaps port to 993 (from 9993)
https://kolabsys.com/about/guam/configuration.html
In a Kolab Groupware setup, Guam is configured with listeners on ports 143 and 993, against an imaps IMAP server on localhost port 9993.
my config
/etc/guam/sys.config
{
kolab_guam, [
{
imap_servers, [
{
imaps, [
{ host, "127.0.0.1" },
{ port, 9993 },
{ tls, true }
]
}
]
},
{
listeners, [
{
imap, [
{ port, 143 },
{ imap_server, imaps },
{
rules, [
{ filter_groupware, [] }
]
},
{
tls_config, [
{ certfile, "/var/lib/acme/live/example.com/cert" },
{ keyfile, "/var/lib/acme/live/example.com/privkey" },
{ cacertfile, "/var/lib/acme/live/example.com/fullchain" }
]
}
]
},
{
imaps, [
{ port, 993 },
{ implicit_tls, true },
{ imap_server, imaps },
{
rules, [
{ filter_groupware, [] }
]
},
{
tls_config, [
{ certfile, "/var/lib/acme/live/example.com/cert" },
{ keyfile, "/var/lib/acme/live/example.com/privkey" },
{ cacertfile, "/var/lib/acme/live/example.com/fullchain" }@kvaps Thanks, removing the content_filter seemed to do the trick, although I still don't know how to use Amavis. @buhaha Thanks for pointing that out!
Is Postfix supposed to use Guam for delivery too, or is it okay to use lmtp to connect to Cyrus' unix-socket directly? Also I wonder how sasl authentication plays into this... The docs say that Guam should use it, but when I enable it Postfix picks it up and doesn't deliver anymore until I disable sasl again. Should this configured in the image, or is this meant to be configured individually?
In
/var/log/kolab/pykolab.log:In
/var/log/roundcubemail/errors:However, I can't find anything useful in the journal, and Cyrus itself seems to be happy:
The other services seem to be reachable, e.g.,
nc -v localhostworks inside the container with ports 389, 25, 80, 443, etc.EDIT: I found the following messages in
/var/log/maillog... are they relevant? I have no clue what they mean..