Nach Update auf 4.2: Kopano nimmt keine Mails von extern mehr an

mail
kopano
german

#1

Ich habe gestern auf 4.2-3 aktualiesiert. Nach den ersten Hürden, die ich beseitigen konnten, bleibt jetzt noch das Problem, dass die Mails, die ich von extern abhole, nicht mehr ankommen in Kopano.

Hier die kopano/server.log:

Thu Jan  4 08:02:38 2018: [ notice] Starting kopano-server version 8.4.5.0 (pid 4507)
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'sync_log_all_changes' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'plugin_path' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'thread_stacksize' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_enabled' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_path' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_level' is not used anymore.
Thu Jan  4 08:02:38 2018: [warning] Config warning: Option 'client_update_log_path' is not used anymore.
Thu Jan  4 08:02:39 2018: [error  ] Coredumps will not be generated: kopano-server requires the fs.suid_dumpable sysctl to contain the value 2, not 0.
Thu Jan  4 08:03:42 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan  4 08:14:27 2018: [error  ] Previous message logged 71 times
Thu Jan  4 08:14:27 2018: [error  ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan  4 08:14:28 2018: [error  ] Previous message logged 3 times
Thu Jan  4 08:14:28 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan  4 08:22:20 2018: [error  ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan  4 08:22:29 2018: [error  ] Previous message logged 2 times
Thu Jan  4 08:22:29 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan  4 08:22:31 2018: [error  ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.
Thu Jan  4 08:22:31 2018: [error  ] Error while connecting to search on "file:///var/run/kopano/search.sock"
Thu Jan  4 08:30:03 2018: [error  ] Previous message logged 57 times
Thu Jan  4 08:30:03 2018: [error  ] LDAP search error: Can't contact LDAP server. Will unbind, reconnect and retry.

Und hier die mail.log

Jan  4 09:23:27 ucs002090 fetchmail[11821]: Nachricht mkolowicz@t-online.de@sfwdallmx.t-online.de:1 von 1 wird gelesen (20461 Bytes) gelöscht
Jan  4 09:23:27 ucs002090 postfix/smtp[12303]: warning: database /etc/postfix/tls_policy.db is older than source file /etc/postfix/tls_policy
Jan  4 09:23:27 ucs002090 postfix/smtpd[12300]: disconnect from localhost[127.0.0.1]
Jan  4 09:23:27 ucs002090 postfix/smtpd[12306]: connect from localhost[127.0.0.1]
Jan  4 09:23:27 ucs002090 postfix/smtpd[12306]: E24124B0025C: client=localhost[127.0.0.1], orig_queue_id=F17C54B00104, orig_client=localhost[127.0.0.1]
Jan  4 09:23:27 ucs002090 postfix/cleanup[12302]: E24124B0025C: message-id=<003201d38535$a07b4370$e171ca50$@gmx.de>
Jan  4 09:23:27 ucs002090 postfix/qmgr[3409]: E24124B0025C: from=<michael.kolowicz@gmx.de>, size=21606, nrcpt=1 (queue active)
Jan  4 09:23:27 ucs002090 postfix/smtpd[12306]: disconnect from localhost[127.0.0.1]
Jan  4 09:23:28 ucs002090 amavis[10400]: (10400-02) Passed CLEAN {RelayedInternal}, LOCAL [127.0.0.1]:53186 [134.3.22.6] <michael.kolowicz@gmx.de> -> <michael.kolowicz@xxxxxxx.lan>, Queue-ID: F17C54B00104, Message-ID: <003201d38535$a07b4370$e171ca50$@gmx.de>, mail_id: dWMXyTKrUrwp, Hits: 1.275, size: 20821, queued_as: E24124B0025C, 855 ms
Jan  4 09:23:28 ucs002090 postfix/smtp[12295]: E24124B0025C: to=<michael.kolowicz@xxxxxxx.lan>, relay=none, delay=0.08, delays=0.07/0/0.01/0, dsn=5.4.6, status=bounced (mail for xxxxxxx.lan loops back to myself)
Jan  4 09:23:28 ucs002090 postfix/cleanup[12302]: 11D2D4B00350: message-id=<20180104082328.11D2D4B00350@ucs002090.xxxxxxx.lan>
Jan  4 09:23:28 ucs002090 postfix/bounce[12307]: E24124B0025C: sender non-delivery notification: 11D2D4B00350
Jan  4 09:23:28 ucs002090 postfix/qmgr[3409]: 11D2D4B00350: from=<>, size=23646, nrcpt=1 (queue active)
Jan  4 09:23:28 ucs002090 postfix/qmgr[3409]: E24124B0025C: removed
Jan  4 09:23:28 ucs002090 postfix/smtp[12303]: F17C54B00104: to=<michael.kolowicz@xxxxxxx.lan>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.15/0.03/0/1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as E24124B0025C)
Jan  4 09:23:28 ucs002090 postfix/qmgr[3409]: F17C54B00104: removed

Als Grund für die “Ablehnung” wird genannt: “dsn=5.4.6, status=bounced (mail for xxxxxxx.lan loops back to myself)”. Was muss ich dazu noch einstellen, damit es wieder funktioniert?


#2

Nur zur Sicherheit (wegen der Meldungen im server.log) - der slapd laeuft
und univention-ldapsearch funktioniert?


#3

Ja - wenn ich

univention-ldapsearch -LLL '(|(mailPrimaryAddress=*)(mailAlternativeAddress=*))' uid mailPrimaryAddress mailAlternativeAddress

aufrufe, werden alle Benutzer angezeigt mit ihren Adressen


#4

Im Gegensatz zu der Aussage im Link https://help.univention.com/t/tutorial-fehlermeldungen-setting-up-univention-to-allow-multiple-e-mail-addresses-per-user/5590/10 das man

univention-config-registry set mail/postfix/virtual/enabled = 'false'

setzen muss, habe ich diesen Wert jetzt auf “true” gesetzt - seit dem funktionier mein Maileingang auch wieder wie vorher