Re: Disable capability UTF8 USER
Sam Varshavchik <[email protected]> Wed, 14 Aug 2024 20:29:09 -0400
| Newsgroups | gmane.mail.imap.courier.general |
|---|---|
| Message-ID | <[email protected]> |
Bertrand COTTENET via courier-users writes: > « HTML content follows > > Hi all, > > > We updated our mail server to debian 12 with latest courier packages > (courier-pop 1.0.16-3+b6) > I see some new capabilities now implemented in courier-pop (in my case RFC > 6856 UTF8 and UTF8 USER) > > > But I have an issue with the famous microsoft mail tool : outlook. > If I understand the RFC, UTF8 (with no argument) is related to mails , and > MUST be called after authentication. > If UTF8 take the USER argument, then the capability is related to > authentication ONLY and should be called BEFORE LOGIN and PASS . > > > However, Outlook, when connecting tp courier-pop, sends CAPA, the LOGIN, then > PASS, then UTF8. > courier-pop answers with -ERR > > > Is a way to disable UTF8 capability in courier-pop ? Maybe I misunderstood > the RFC ? Or should I set some other options to have Outlook working with > courier-pop ? > > > I tried several others mail tools, the issue is only with Outlook. The current version of Courier is 1.3.11. A workaround for this Outlook bug was released in 2018. _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCZr1L1QAKCRCKYPgoojZS 4oO4AP9wYqKoH2c0L5xCTMBzut/nDtYG31HSI5edtHpTy98whgD+K/8RjgrjVcZE 3YX8lr/7CEwj+MZdbbFONKx5P0mCYAU= =Ghwk -----END PGP SIGNATURE-----