Re: Disable capability UTF8 USER

Sam,

Unfortunately, the version of Courier that is packaged up and available 
within the Debian archives is woefully out of date.

At the end of 2020, the maintainer of the package raised a "Request for 
Help" 'bug' (https://bugs.debian.org/978755), and there doesn't appear 
to have been much activity on the package since then.


Bertrand,

Because of the above, unfortunately the only option to get a more recent 
version of the courier packages is to build them yourself - the process 
is relatively straight forward:

  * Download the source for either the whole suite or just the
    components you require (the authlib and unicode components are most
    likely to be needed as well)
  * Extract the `courier-debuild` file from within the tarball for the
    unicode module
  * Run `courier-debuild` script with `-us -uc` options
      o `apt-get` extra packages as required
  * Install the unicode library
      o `apt-get` extra packages that `dpkg` says you need.
  * Repeat for authlib
  * Repeat for courier-pop

I've got this working within a docker container (albeit for the whole 
suite) on my desktop computer, and it drops out the build .deb's so that 
I can `scp` them across to my server for installation - I can provide 
the .Dockerfile if you like.


Hope this helps,

Regards,

Krystal

On 15/8/24 10:29, Sam Varshavchik wrote:
> 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

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users