附加组件
![[警告]](https://addons.thunderbird.net/static/img/developers/test-warning.png?b=b00ed3ed-652d8172)
权限
关于这个附加组件
TB v68 compatibility note:
There is no plan to move the addon to the TB v68 "standards", and here is why:
- Mozilla itself has decided not to work on compatibility developments and leave "that" to the addon developers.
I don't know how much a mozilla developer is paid, but speaking for myself the sum of the contributions i have ever received for 6 free addons during almost 10 years are a figure with 3 digits max...
- Besides the fact Mozilla leaves us doing the "dirty work", they are not even able to provide detailed information about how to make the old addons compatible with their new standards.
I mean a relevant guide, not an information note explaining that the addons should be restartless, turned into webextensions and so on, and not even giving an example.
- That is not the first time that Mozilla is acting as if addons developers and the community was not important.
I have had already several bad experiences in the past when my addons got broken just because Mozilla changed something which used to work without even thinking about compatibility or giving information.
- I'm tired of all this, and as i have another real job to afford my bills, i'm not ready to make all that effort for so few consideration.
- It already took me thousands and thousands and thousands of hours to develop my addons, working everyday on making them the more stable and practical possible. Why would i do twice something which worked pretty well?
- All my addons are Mozilla-licensed (~ free softwares), so sources are open for all developers which would be interested to follow the new Mozilla standards.
I think i made this work the best professional i could, so my code is well structured and full of comments. If you do so, sending me a simple "thank-you" email would be greatly appreciated.
- All my addons are already compatible with TB v60. Are there so much interest to move to TB v68?
Do you change your toaster every year just because there are new ones on the market? I don't.
- The choice is between v68 without addons or v60 with addons. Your call.
SMTP Switch Reborn is a Thunderbird add-on which allows to change global default SMTP server on the fly when sending a message.
When moving from one location to another, you have to change the SMTP server to use the one from your current location, otherwise the message cannot be sent.
For security reasons (spams) ISP generally forbid to use a 3td party SMTP server, and only allow their SMTP servers to be used.
Features are the following:
* All platforms are supported. Tested versions are:
- Windows: XP sp3 (x86), Seven Pro sp1 (x64);
- Linux: Mandriva 2011-2 (x86);
- Mac: OS X 10.7 / Lion (x64).
* Available languages are: french (fr-FR), english (en-US).
* The main feature, which is changing SMTP server, is available in a drop-down list on the right of the native "send message" button.
* This addon can only control SMTP servers of accounts which are set to use the global default SMTP server.
* Settings dialog allow to set easily mail accounts with global default SMTP server.
* The addon allows to define automatic detection rules based on IP address in order to set automatically the default SMTP server.
* The add-on provides a 'debug mode' which writes information into embedded error console (see Tools > Error Console) or in a dedicated debug log file.
* Error and warning messages are also written into error console (regardless debug mode is enabled or not).
If for any kind of reason the add-on seems not to work properly, open error console and look for messages regarding add-on which could give you information about the issue (all messages are prefixed by add-on name).
If the issue is reproducible and you think it's an add-on bug:
1. Enable debug mode and enable 'Log messages in a file'.
2. Click on 'Export settings' to create settings file.
3. Proceed again (messages will be saved in debug log file').
4. Contact us and report us relevant and maximum information regarding the issue:
- screen captures of each step of the action which leads to the issue
- screen captures of each settings tab
- settings file
- debug log file
NB: Incomplete issue reports will not be answered.
Contact (bug reports, features request, etc.): [email protected].
NB: Usage support email will not be answered.
There is no plan to move the addon to the TB v68 "standards", and here is why:
- Mozilla itself has decided not to work on compatibility developments and leave "that" to the addon developers.
I don't know how much a mozilla developer is paid, but speaking for myself the sum of the contributions i have ever received for 6 free addons during almost 10 years are a figure with 3 digits max...
- Besides the fact Mozilla leaves us doing the "dirty work", they are not even able to provide detailed information about how to make the old addons compatible with their new standards.
I mean a relevant guide, not an information note explaining that the addons should be restartless, turned into webextensions and so on, and not even giving an example.
- That is not the first time that Mozilla is acting as if addons developers and the community was not important.
I have had already several bad experiences in the past when my addons got broken just because Mozilla changed something which used to work without even thinking about compatibility or giving information.
- I'm tired of all this, and as i have another real job to afford my bills, i'm not ready to make all that effort for so few consideration.
- It already took me thousands and thousands and thousands of hours to develop my addons, working everyday on making them the more stable and practical possible. Why would i do twice something which worked pretty well?
- All my addons are Mozilla-licensed (~ free softwares), so sources are open for all developers which would be interested to follow the new Mozilla standards.
I think i made this work the best professional i could, so my code is well structured and full of comments. If you do so, sending me a simple "thank-you" email would be greatly appreciated.
- All my addons are already compatible with TB v60. Are there so much interest to move to TB v68?
Do you change your toaster every year just because there are new ones on the market? I don't.
- The choice is between v68 without addons or v60 with addons. Your call.
SMTP Switch Reborn is a Thunderbird add-on which allows to change global default SMTP server on the fly when sending a message.
When moving from one location to another, you have to change the SMTP server to use the one from your current location, otherwise the message cannot be sent.
For security reasons (spams) ISP generally forbid to use a 3td party SMTP server, and only allow their SMTP servers to be used.
Features are the following:
* All platforms are supported. Tested versions are:
- Windows: XP sp3 (x86), Seven Pro sp1 (x64);
- Linux: Mandriva 2011-2 (x86);
- Mac: OS X 10.7 / Lion (x64).
* Available languages are: french (fr-FR), english (en-US).
* The main feature, which is changing SMTP server, is available in a drop-down list on the right of the native "send message" button.
* This addon can only control SMTP servers of accounts which are set to use the global default SMTP server.
* Settings dialog allow to set easily mail accounts with global default SMTP server.
* The addon allows to define automatic detection rules based on IP address in order to set automatically the default SMTP server.
* The add-on provides a 'debug mode' which writes information into embedded error console (see Tools > Error Console) or in a dedicated debug log file.
* Error and warning messages are also written into error console (regardless debug mode is enabled or not).
If for any kind of reason the add-on seems not to work properly, open error console and look for messages regarding add-on which could give you information about the issue (all messages are prefixed by add-on name).
If the issue is reproducible and you think it's an add-on bug:
1. Enable debug mode and enable 'Log messages in a file'.
2. Click on 'Export settings' to create settings file.
3. Proceed again (messages will be saved in debug log file').
4. Contact us and report us relevant and maximum information regarding the issue:
- screen captures of each step of the action which leads to the issue
- screen captures of each settings tab
- settings file
- debug log file
NB: Incomplete issue reports will not be answered.
Contact (bug reports, features request, etc.): [email protected].
NB: Usage support email will not be answered.
