From nobody Mon Jul 18 17:02:05 2022 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4LmpCy0mV0z4Wf7Y for ; Mon, 18 Jul 2022 17:02:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LmpCx5FVBz3Qpf for ; Mon, 18 Jul 2022 17:02:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4LmpCx4LGnzn8Z for ; Mon, 18 Jul 2022 17:02:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 26IH25wZ075581 for ; Mon, 18 Jul 2022 17:02:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 26IH25rb075580 for ports-bugs@FreeBSD.org; Mon, 18 Jul 2022 17:02:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 261893] mail/davmail: Fails to run: java.lang.ClassNotFoundException: davmail.exchange.auth.O365InteractiveAuthenticator Date: Mon, 18 Jul 2022 17:02:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: noisetube@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1658163725; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=z427c32wW1FR2+gncwofPz+cDdUXRDADu7/FCvyL7L4=; b=KUQrMHjBbo5MrUjVqDIr/ii8Czip5HDyGyOLSohelnfU01p4gyiVTJi0SCd5TJMfZQM7Xk 3h0pG0kkwTrnN1E9CH+3+PJTtv+Zo1SJYaq2i+SMqW4mqU6eL9WnHX1dcO43WJ8wA38NF6 c5bZGGV0JlTH1z6c62fxaE3tHYP2KCk9d25W0NbYZWli+F36MyeZIYluFAaKLJzOi+Zrpt 0Ierb9MF2JmAyzW0IoMqjjZ0k+m3KlNQ3PIQh2KC5/iRCZss3Sk3spnUJHO1fj2hJCN6T2 EbeASqwoxfPAhaV/+9OmHaaV/Ugfp3VHrw0R3QBqMXurBUFqjC2AE/krVuRXJg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1658163725; a=rsa-sha256; cv=none; b=Y/R/bPsoSKSvof6b9nJvN+ZMpvHAAfvf8Sj3KAx2Si0kmGPaLzIIP/3wm2yEMYeItAjIsV TARi0GY29+gFPOpwvljQNCVwUC8M/3vjKgUfab4dUvi9lY8dN5Gd2r4B752HKMbDAiGpdf 9m+z82qNQpfmxxUAC8rOQKBm1vVAeYDSBaG7x9szGCmZZtPFq7mAV3hhXS6bHT8/2gyvfu m1KJpCY0kzu7Gl/y7zeh3r+m6mkPAbYa6uGmCzIt+iAs6xibIaxIogZNduVVpwTJ4wtNcO MYD+6TrNB828G9D36QzrZyNG7yy5+ZiZ8x3pGL1FqIh9E+fPpjkaF58hpx/ruA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261893 Bill Paul changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noisetube@gmail.com --- Comment #5 from Bill Paul --- The original submitter did not follow up, but I will. There are actually a couple of different Davmail builds for various platfor= ms: - Windows - MacOS - Linux - Platform-independent You would think this would not be necessary given that it's written in Java, and Java is supposed to be a "write once, run anywhere" language. Part of t= he reason they did this is so that they could have platform-specific archives (self-extracting EXE for windows, .deb for Linux), but there's a little mor= e to it than that. In order for the O365Interactive authentication method to work, it needs to open a browser window that accesses the Office365 login page (and, possibly, the single sign-on and/or 2FA page for a user's organization) so that the u= ser can interactively enter their credentials and get an OAuth2 token. The problem is that the way in which the interactive window is opened and t= he way the info from it is exchanged with Davmail is apparently platform-speci= fic. The Windows, MacOS and Linux builds know how to do it for their respective platforms, but since there isn't a platform-independent way to do it, the platform-independent build just doesn't include the support for this featur= e. Unfortunately, since FreeBSD uses the platform-independent version, that me= ans you can't use the O365Interactive authentication method. Apparently this limitation in the platform-independent build is not well documented (otherwise this bug wouldn't have been filed). You would think whatever works for Linux would also work for FreeBSD, but I= 'm not sure if it's possible to adapt the port so that it uses the Linux distribution instead. What I suggest as a workaround is to use the O365Manual mechanism instead. = With this method, a small pop-up window will appear, prompting you to open a lin= k in your browser to access the Office 365 login page, and once you successfully enter your credentials, you have to manually cut & paste the resulting URL = back into the pop-up dialog and click "Send." This is a little more clumsy than = the O365Interactive scheme, but ultimately it has the same results. --=20 You are receiving this mail because: You are the assignee for the bug.=