Outlook kein authomatische erkennung

[hefrug]

Contribution guidelines

• [X] I've read the contribution guidelines and wholeheartedly agree

I've found a bug and checked that ...

• [X] ... I understand that not following 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.

Description

Problem mit Autodiscover in Outlook und Mailcow

Hallo zusammen,

ich habe ein Problem mit der Autodiscover-Funktion in Microsoft Outlook in Verbindung mit unserem Mailserver Mailcow. Trotz mehrerer Versuche kann Outlook die E-Mail-Konten nicht automatisch konfigurieren.

In der Mailcow-Dokumentation konnte ich nicht eindeutig erkennen, welche Outlook-Versionen unterstützt werden sollten und welche nicht. Laut einem GitHub-Issue funktioniert Autodiscover bei Outlook 2016 oder höher von Office 365 nicht. Wir verwenden jedoch kein Office 365 sonder Outlook 2019,  daher sollte es eigentlich funktionieren. Trotzdem erhalte ich den gleichen Fehler wie in dem genannten Issue.

Deshalb meine Frage: Ist die Dokumentation korrekt, https://docs.mailcow.email/de/manual-guides/u_e-autodiscover_config/

oder gibt es hier möglicherweise Fehler oder Unklarheiten? Hat jemand eine Idee, was ich noch überprüfen könnte oder was möglicherweise falsch konfiguriert ist?

Logs:

logs ist leer

Steps to reproduce:

wenn ich mich  in outlook einlogge autodiscover funktioniert nicht

Which branch are you using?

master

Which architecture are you using?

x86

Operating System:

ubuntu 22.04 LTS

Server/VM specifications:

8,2

Is Apparmor, SELinux or similar active?

no

Virtualization technology:

VMware

Docker version:

26.1.3

docker-compose version or docker compose version:

v2.27.1

mailcow version:

2024-06

Reverse proxy:

nginx

Logs of git diff:

-MIIDBDCCAe6gAwIBAgIQeJMoL/3dxhxhT9EwuRTL/DALBgkqhkiG9w0BAQswEjEQ
-MA4GA1UEChMHbWFpbGNvdzAeFw0xNjEyMTMxMDExMDBaFw0xOTExMjgxMDExMDBa
-MC0xEDAOBgNVBAoTB21haWxjb3cxGTAXBgNVBAMTEG1haWwuZXhhbXBsZS5vcmcw
-ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDRg0xT3At9DSb3H5OMp3K1
-MpXAgYyotSK6TS61fC0QEHy2fMXiws7Agcye6Ln7CG63Fe1eN2jkdlefy9xJivS8
-y5w0M8i168v5znzC8fnylL2iOiSYfK/B/oEqfU7YH4RcegO53oDDIUZmi4Frgnu7
-39VVOU1ZyHEVqGJ2H2aAIkoZRjGzumD9Ym4LWGidtKJzBgFt/qmhUeWXipM8w281
-XkQnJU79+x2ywnJSvEZ3r/ZVJC7kbjiVw+/k15k9Cxk6Ik8wmJ0X/+xWxoZomHQI
-1LM0VKAS/iaU95dn2bplvL6jTiiyWAbrMjSKs4XbPt/fIbOicNkj6+CFy0MVfyyH
-AgMBAAGjPzA9MA4GA1UdDwEB/wQEAwIAqDAdBgNVHSUEFjAUBggrBgEFBQcDAgYI
-KwYBBQUHAwEwDAYDVR0TAQH/BAIwADALBgkqhkiG9w0BAQsDggEBAI/jBJa1P8nB
-eHUN5muQmjBVDVOYyWAAEapOe2HYsBcpjaB2H8Iw3DQzJtz6peYeYSCmHRVqFLCm
-VPrq36l9mPUotyPDPlQQAxCj9R2+WbGaJO+N/E1F8FQ94dr3jqwUyfjVPoqEjmIH
-NFkvbA0RJOeBm9oYGdhM0wjOBV9c9MTHFG82nQ/zQeTuPb7GXuKIOXYCxoLNOZMw
-UJ02Cqjv5ImrgOhcstAKX3Ip0urSvZUGvtPla4CGh+M6yDFJ08GzX6OiMIH207RW
-jAbUXXERSUv/7hysdDjGo5HZjCeMzVu9KAxoZXqnmvkk8g2swKWtWBRcoeU1VGx0
-Bx4Q4KMjuYQ=

Logs of iptables -L -vn:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Logs of ip6tables -L -vn:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Logs of iptables -L -vn -t nat:

pkts bytes target     prot opt in     out     source               destination

Logs of ip6tables -L -vn -t nat:

pkts bytes target     prot opt in     out     source               destination

DNS check:

pkts bytes target     prot opt in     out     source               destination

[milkmaker]

THIS IS A AUTOMATED MESSAGE!

It seems your issue is not a bug. Therefore we highly advise you to get support!

You can get support either by:

• ordering a paid support contract at Servercow (Directly from the developers) or
• using the community forum (Based on volunteers! NO guaranteed answer) or
• using the Telegram support channel (Based on volunteers! NO guaranteed answer)

This issue will be closed. If you think your reported issue is not a support case feel free to comment above and if so the issue will reopened.