WebExtension: Changing port number in client

[bernd-schroedter]

Sieve is running on our Suse Linux mailserver for many years.
Last Sieve configuration modification has been made month/years ago. I enjoyed working with the Thunderbird add on at that time.
Now I have problems to connect to our server with the actual add on.
My client is a Windows 10 - Thunderbird 78.7.0 with Sieve add on V0.5.3.

The problem is probably the configured port number.
The add on is using port 4190. On the server sieve is provided on port 2000.
In the earlier add on I could configure the port number.
I can't find how to change the number in the actual add on.
Can anyone give me a hint how to do?

[Ceaus]

You can unzip the extension in the Thunderbird directory, change the port (SieveAbstractSession.js) and re-zip it. In theory this should work.

[thsmi]

WebExtension in contrast to classic addons are limited by design. They do not provide any kind of preference system. There are workaround but all are hacky and it easily happens that you loose the settings upon an extension update.

For this reason (and also some others) the port is hard coded in WebExtension to the default one specified in the RFC.
As mentioned in the post above the xpi file of WebExtension is just a zip which can be unpacked, edited and repacked. But upon a new release the xpi will be automatically replaced.

If you need to configure a custom port, just use the standalone application. It has full feature parity with the legacy add-on and allows you to freely configure the settings.

[bernd-schroedter]

Thank you Thomas for your reply!
Please tell me which standalone application you were talking about. Give me a hint where I can find it.

Meanwhile I found a solution how I can work with the add-on.
I modified some lines in the source code of the extension.
Maybe someone is interested in this changes.
Therefore I send my memo in the following lines:

Sieve - Add-On V0.5.3 (filter manager) for Thunderbird 78.8.0

Adaptation of the add-on to our Sieve server (part of the mail server)

Bernd Schrödter - February 25, 2021

Problem:
The Sieve Add-On expects a Sieve server on port 4190 with secure transmission.
Our Sieve server communicates on port 2000 (old standard) and is unsecured.

Solution:
Editing / change in the program code of the extension.

The program code is compressed in the file "[email protected]".
The file is located in the directory of the Thunderbird user profile.
For me this is the directory E: \ Documents \ zdufi6iy.Schroedter \ extensions .
I was able to unpack the xpi file with WinRAR 5.60.
After unpacking, the individual program code files can be edited and then individually pushed back into the xpi file in WinRAR.
I made changes in 4 program code files.

---

File. \ libs \ libManageSieve \ SieveAbstractSession.js:

Comment out the line with the 4190 and insert a line with 2000.

const {
SieveClientException,
SieveServerException,
SieveReferralException,
SieveTimeOutException,
SieveCertValidationException
} = require ("./ SieveExceptions.js");

const FIRST_ELEMENT = 0;
/ *

• const SIEVE_PORT = 4190;
• /
  const SIEVE_PORT = 2000;

---

File. \ Libs \ managesieve.ui \ settings \ logic \ SieveAbstractHost.js:

Replace “PORT_SIEVE_RFC = 4190” with “PORT_SIEVE_RFC = 2000”.

(function (exports) {

"use strict";

const PORT_SIEVE_RFC = 2000;
const PORT_SIEVE_OLD = 2000;

const TYPE_RFC = 0;
const TYPE_OLD = 1;
const TYPE_CUSTOM = 2;

---

File. \ Libs \ managesieve.ui \ settings \ logic \ SieveSecurity.js:

Replace "return await true" with "return await false".

/ **

• Defines the security related settings for an account.
• It is a minimal, mozilla specific implementation.
• /
  class SieveSecurity {

/ **
 * @inheritdoc
 * /
async isSecure () {
  return await false;
}

/ **
 * @inheritdoc
 * /
async getMechanism () {
  return await "default";
}

}

---

File. \ Libs \ managesieve.ui \ settings \ logic \ SieveSecuritySettings.js:

Replace “getBoolean (PREF_TLS, true)” by “getBoolean (PREF_TLS, false);”.

  / **
 * Gets the current security settings. In case it is set to true
 * a secure connection shall be used.
 *
 * @returns {boolean}
 * true in case a secure connection should be used.
 ** /
async isSecure () {
  return await this.account.getConfig (). getBoolean (PREF_TLS, false);
}

[thsmi]

Thank you Thomas for your reply!
Please tell me which standalone application you were talking about. Give me a hint where I can find it.

The project is released as Linux and Windows standalone application as well as a Thunderbird WebExtension

In the release section. https://github.com/thsmi/sieve/releases/latest