NoComposeAccount Version History
9 versions
Be careful with old versions!
These versions are displayed for reference and testing purposes. You should always use the latest version of an add-on.
Version 1.5.4
Bug fix: Sending an email without selecting a compose account would allow dispatch
- Source code released under MIT/X11 License
Version 1.3
Bug fix: The addon would fail in situations where "Use the default account" was selected and more than one identity was configured on the default account.
Version 1.2
Bug fix: when NoComposeAccount was set to start with blank compose account Thunderbird would fail to save drafts.
Most likely draft saving fails because Thunderbird doesn't know where to save when no account is selected.
You can now use the "Force selection of compose account" option to have NoComposeAccount force you to select account before writing the email.
When the "force" option is on and no compose account is selected it will be impossible to enter text in the message body window until an account has been selected.
Once again thanks to Giacomo for help and support.
Most likely draft saving fails because Thunderbird doesn't know where to save when no account is selected.
You can now use the "Force selection of compose account" option to have NoComposeAccount force you to select account before writing the email.
When the "force" option is on and no compose account is selected it will be impossible to enter text in the message body window until an account has been selected.
Once again thanks to Giacomo for help and support.
Version 1.1
Compatibility with TB5 beta tested. No issues found.
Two bugs fixed:
1) NoComposeAccount didn't correctly trigger change of email footer.
Scenario: You have NoComposeAccount set to always use the default account.
You have the inbox of another account (account2) selected when you start a message.
The "From" address changes to the default account, but the mail footer remains that of "account2".
The hint from review by Mark fixed it. Thank you Mark van Renswoude.
Note: if you choose to start with a blank compose account the footer of the currently selected account will still be inserted.
2) When re-focusing the compose window NoComposeAccount would also re-run.
Scenario: You have NoComposeAccount set to always use a blank "From" account.
You have started a new email and selected "account1" as "From" account.
You then go to your internet browser to look up something.
When you return to the email you were writing NoComposeAccount re-runs and in turn changes the "From" account back to blank.
This behavior has now been been removed. NoComposeAccount will run only the first time the compose window is loaded.
Thank you Giacomo.
Two bugs fixed:
1) NoComposeAccount didn't correctly trigger change of email footer.
Scenario: You have NoComposeAccount set to always use the default account.
You have the inbox of another account (account2) selected when you start a message.
The "From" address changes to the default account, but the mail footer remains that of "account2".
The hint from review by Mark fixed it. Thank you Mark van Renswoude.
Note: if you choose to start with a blank compose account the footer of the currently selected account will still be inserted.
2) When re-focusing the compose window NoComposeAccount would also re-run.
Scenario: You have NoComposeAccount set to always use a blank "From" account.
You have started a new email and selected "account1" as "From" account.
You then go to your internet browser to look up something.
When you return to the email you were writing NoComposeAccount re-runs and in turn changes the "From" account back to blank.
This behavior has now been been removed. NoComposeAccount will run only the first time the compose window is loaded.
Thank you Giacomo.
Version 1.0
Changed compatability max version to "3.1.*"
Testing with Thunderbird 3.1 rc2 on XP SP2 yielded no issues.
Add-on version number bumped up to 1.0
Testing with Thunderbird 3.1 rc2 on XP SP2 yielded no issues.
Add-on version number bumped up to 1.0
To create your own collections, you must have a Mozilla Add-ons account.