WebExtension: Changing port number in client #482
Replies: 3 comments 1 reply
-
You can unzip the extension in the Thunderbird directory, change the port (SieveAbstractSession.js) and re-zip it. In theory this should work. |
Beta Was this translation helpful? Give feedback.
-
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. 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. |
Beta Was this translation helpful? Give feedback.
-
Thank you Thomas for your reply! Meanwhile I found a solution how I can work with the add-on. 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: Solution: The program code is compressed in the file "sieve@mozdev.org.xpi". File. \ libs \ libManageSieve \ SieveAbstractSession.js: Comment out the line with the 4190 and insert a line with 2000. const { const FIRST_ELEMENT = 0;
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 TYPE_RFC = 0; File. \ Libs \ managesieve.ui \ settings \ logic \ SieveSecurity.js: Replace "return await true" with "return await false". / **
} File. \ Libs \ managesieve.ui \ settings \ logic \ SieveSecuritySettings.js: Replace “getBoolean (PREF_TLS, true)” by “getBoolean (PREF_TLS, false);”.
|
Beta Was this translation helpful? Give feedback.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions