NEOSYS Technical Support Wiki - User contributions [en]

Implementing NEOSYS

2026-01-14T05:23:11Z

Saif: /* Setting up the System Configuration File */

==Setting up the System Configuration File==
See [http://userwiki.neosys.com/index.php/System_Configuration_File System Configuration File] for detailed description. The following points are essential configuration and must not be ignored.

#All configurations must be carefully done after evaluating which [http://userwiki.neosys.com/index.php/System_Configuration_File#Scope Scope] they fall under.
#Configure alert email addresses in the System Configuration File (make sure that there is at least 1 person from the client management and one person from client IT who receives the backup alert, in addition to backups@neosys.com)
#Configure [http://userwiki.neosys.com/index.php/System_Configuration_File#Web_Address_and_Description URL/Web Address] to access NEOSYS. This is very important for a Timesheet module installation as the approver links are picked up from the configuration.
#Set the User Timezone
#Set up [http://userwiki.neosys.com/index.php/System_Configuration_File#Email_Domains Email Domains] and [http://userwiki.neosys.com/index.php/System_Configuration_File#IP_numbers IP Numbers]. Support staff MUST add the client's email domain to NEOSYS internal email whitelist (Webmin > Servers - SpamAssassin Mail Filter > Allowed and Denied Addresses), so that emails from this client do not get automatically marked as spam.
#If NEOSYS is hosted by the client, then add the client's outgoing public IP address to Zoneedit > manage > DNS Settings > TXT > EDIT > neosys.com , otherwise email providers may refused to receive emails from the client's NEOSYS server. The outgoing IP number can be found by doing Ctrl+u on an email from the client's NEOSYS server and checking the "Received: from" section.
#Set up [http://userwiki.neosys.com/index.php/System_Configuration_File#Sender_Email_Address Sender Email Address]. Support staff MUST add the Sender Email Address to the aliases for support@neosys.com (Virtualmin > Mail Options > Edit Mail Aliases). Then send a test email to the Sender Email Address to check whether the sent email is received in support@neosys.com inbox

==Start neosysddns service for Client's with dynamic ip==

See [[NEOSYS_DDNS_Service#Starting_Windows_service_on_the_client_server|Starting NEOSYS DDNS Service]] to start the neosysddns service so that NEOSYS monitoring server at monitor.neosys.com updates zonedit.com with the latest ip of the client server.

You MUST check if the ip is actually getting updated otherwise if the ip changes and neosysddns is not working we will lose access to the server. See [[NEOSYS_DDNS_Service#Troubleshooting_NEOSYS_DDNS_Service|Troubleshooting NEOSYS DDNS Service]] for commands to do so.

==Update Support.htm==
Add the new client to the list of clients page.

See [http://itwiki.neosys.com/index.php/Updating_Support.htm Updating Support.htm]

==Setting up a new company in the new database==
Refer to the [http://userwiki.neosys.com/index.php/Setting_up_multi_company_installations_/_Setting_up_a_new_company#Draft_email_requesting_info_required_to_add_new_company_to_existing_database sample email for New Company creation in existing Database/New Database]

Once the new company is added to the database:
#Set up exchange rate as "1" for the base currency by going to the Currency and Exchange Rate File
#Delete “Client X” from the Client and Brand File
#Set the letterhead refer to [http://userwiki.neosys.com/index.php/Configuring_Letterhead Configuring Letterhead]

Change the system mark for each of the new databases that were created. See [http://userwiki.neosys.com/index.php/Setting_up_and_Configuring_NEOSYS_Generally#Configuring_Client_Security_mark Configuring Client Security Mark]

Uninstalling clients hosted on NEOSYS Server

2025-10-01T05:52:53Z

Saif:

This must be done in the following circumstances:

#Reinstallation on other servers
#Reinstallation on clients own server
#Termination of contract
#Any other reason

NEOSYS needs to:

#Ensure that the databases can no longer be logged in to by accident or design.
#Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.

Include admin@neosys.com when sending emails regarding this subject.

====Stage 1. Disabling====

1. Ensure that the services for the client being uninstalled have been stopped.
./doall <dbname> stop

2. Delete the website
./doall <dbname> delete_site

3. Disable the service, otherwise the services will start up every time ex1 reboots.
./doall <dbname> disable

4. In ~/hosts/clients.cfg, comment out the line corresponding to the client being uninstalled.

5. On nagios, comment out the lines for the stopped installation in the config file so that Nagios stops alerting for it. (edit: genclients.sh)

6. On www, strike-through the terminated client's link on support home page (support.htm).

7. Create Thunderbird reminder to permanently delete the client 1 year later.

====Stage 2. Permanent Deletion====

We keep ex client data for up to one year before deleting, but after this period:

1. Retain a copy of the client's latest backup sql.gz file in a separate directory (in ex1:/backups/current/deleted as of 3/4/2023)
mv ~/hosts/<dbname>/work/<dbname>.sql.gz /backups/current/deleted/

2. Delete the database and service
sudo -u postgres dropdb <dbname>
sudo -u postgres dropdb <dbname_test>

3. In ~/hosts/clients.cfg, uncomment the line corresponding to the client being uninstalled and delete service.
./doall <dbname> delete_service

4. In ~/hosts/clients.cfg, delete the line corresponding to the client being uninstalled.

5. Delete client directory from /root/hosts directory.
rm -r ~/hosts/<dbname>

6. On www, remove the terminated client's link from support home page (support.htm).

7. Delete the associated entry from Zone Edit.

8. On nagios, delete the lines for the stopped installation in the config file (edit: genclients.sh).

Uninstalling clients hosted on NEOSYS Server

2025-10-01T05:25:12Z

Saif: /* Stage 2. Permanent Deletion */

This must be done in the following circumstances:

#Reinstallation on other servers
#Reinstallation on clients own server
#Termination of contract
#Any other reason

NEOSYS needs to:

#Ensure that the databases can no longer be logged in to by accident or design.
#Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.

Include admin@neosys.com when sending emails regarding this subject.

====Stage 1. Disabling====

1. Ensure that the services for the client being uninstalled have been stopped.
./doall <dbname> stop

2. Delete the website
./doall <dbname> delete_site

3. Disable the service, otherwise the services will start up every time ex1 reboots.
./doall <dbname> disable

4. In ~/hosts/clients.cfg, comment out the line corresponding to the client being uninstalled.

5. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)

6. Strike-through the terminated client's link on support home page (support.htm).

7. Create Thunderbird reminder to permanently delete the client 1 year later.

====Stage 2. Permanent Deletion====

We keep ex client data for up to one year before deleting, but after this period:

1. Retain a copy of the client's latest backup sql.gz file in a separate directory (in ex1:/backups/current/deleted as of 3/4/2023)
mv ~/hosts/<dbname>/work/<dbname>.sql.gz /backups/current/deleted/

2. Delete the database and service
sudo -u postgres dropdb <dbname>
sudo -u postgres dropdb <dbname_test>
./doall <dbname> delete_service

3. Delete client directory from /root/hosts directory.
rm -r ~/hosts/<dbname>

4. Remove the terminated client's link from support home page (support.htm).

5. Delete the associated entry from Zone Edit.

6. In ~/hosts/clients.cfg, delete the line corresponding to the client being uninstalled.

7. Delete the lines for the stopped installation in the Nagios config file (edit: genclients.sh).

Uninstalling clients hosted on NEOSYS Server

2025-10-01T05:24:15Z

Saif: /* Stage 2. Permanent Deletion */

This must be done in the following circumstances:

#Reinstallation on other servers
#Reinstallation on clients own server
#Termination of contract
#Any other reason

NEOSYS needs to:

#Ensure that the databases can no longer be logged in to by accident or design.
#Ensure that for a reasonable period of time that NEOSYS can be re-enabled in case of error or change in circumstances.

Include admin@neosys.com when sending emails regarding this subject.

====Stage 1. Disabling====

1. Ensure that the services for the client being uninstalled have been stopped.
./doall <dbname> stop

2. Delete the website
./doall <dbname> delete_site

3. Disable the service, otherwise the services will start up every time ex1 reboots.
./doall <dbname> disable

4. In ~/hosts/clients.cfg, comment out the line corresponding to the client being uninstalled.

5. Comment the lines for the stopped installation in the Nagios config file so that Nagios stops alerting for it. (edit: genclients.sh)

6. Strike-through the terminated client's link on support home page (support.htm).

7. Create Thunderbird reminder to permanently delete the client 1 year later.

====Stage 2. Permanent Deletion====

We keep ex client data for up to one year before deleting, but after this period:

1. Retain a copy of the client's latest backup sql.gz file in a separate directory (in ex1:/backups/current/deleted as of 3/4/2023)
mv <dbname>/work/<dbname>.sql.gz /backups/current/deleted/

2. Delete the database and service
sudo -u postgres dropdb <dbname>
sudo -u postgres dropdb <dbname_test>
./doall <dbname> delete_service

3. Delete client directory from /root/hosts directory.
rm -r ~/hosts/<dbname>

4. Remove the terminated client's link from support home page (support.htm).

5. Delete the associated entry from Zone Edit.

6. In ~/hosts/clients.cfg, delete the line corresponding to the client being uninstalled.

7. Delete the lines for the stopped installation in the Nagios config file (edit: genclients.sh).

New Client Training Notes

2025-09-18T06:40:47Z

Saif: /* Finance Module */

==Prior to Training – Preparation for the Meeting==
#List the modules for your own reference that you are going to train the users in (Media, Jobs, Timesheets and/or Finance) and prepare accordingly
#Get an idea of your audience with details like the number of users, their designations and what kind of access they have to NEOSYS
#Prepare handouts listing the topics to be covered in the training session. The user can use this handout to keep track of what happens in training and take notes for reference later
#Create a time-table for trainings and inform the client the same
#Contact Client IT to ensure technical details like firewall exclusions and proxies (if applicable) are configured correctly so that users have access to NEOSYS without issues
#Email training session pre-requisites to the client contact e.g. internet connectivity and projector in the meeting room
#Create an account in the Authorisation file namely Admin, with complete access to NEOSYS. This account can be used for emergency changes in the configuration of the system while at the client location

==During Training==
NEOSYS Staff are responsible to cover the whole of training superficially and not do in depth training. Show users what they need to get started and don’t allow them to slow down training by replying to in depth queries.

Onsite sessions at the client are not just "training" sessions. They are implementation sessions and need to set clear objectives for clients to start implementing the system. It is easy to squander time and resources if client staff believe they can sit back and "be trained" instead of "learn and implement". The end result of such squandering is likely that NEOSYS is asked to return again and again simply due to bad organisation.

How to train:

Training should be done in HALF DAYS and never in whole days because it doesn’t allow client staff time to IMPLEMENT THE SYSTEM. In between sessions client staff has to do work to get things.

Initial training on site is half a day per module and NO MORE because client needs to mentally get into action themselves and not sit back thinking all they have to do is listen.

There are two very different jobs that have to be done during training:

a) Embedding into knowledge of how NEOSYS works into peoples brains

b) Users working out how to use NEOSYS to perform their work since NEOSYS might not handle everything exactly as they imagine

Trainees will often slow down (a) by trying to solve every petty problem in (b). NEOSYS trainers must find a healthy balance to ensure that (a) is done before going in depth in (b). The trainer, like a good chairman of a meeting, should control who can speak and for how long. Failing to do this allows few people to talk too long and everybody complaining that the training was not productive.

Every client staff member must be given some tasks to complete in NEOSYS by themselves before they get into the next training session. The task should include getting printouts of their work. Each person’s work should be inspected and discussed at the next session.

Only ONE NEOSYS staff should conduct implementation sessions unless it is to introduce a junior NEOSYS member to on-site work. Training in parallel by multiple NEOSYS staff is a waste of resources because of the lack of coordinated implementation.

Client finance staff needs to participate in all sessions and not be given private training sessions for what has already been done for operations staff.

Care and attention will produce a quality implementation. Easy and relaxed approach will not produce good results. TAKE ACTION! MAKE A DIFFERENCE!

===Introduction===
Spend 15min in introducing the users to NEOSYS and explaining basic essential points of accessing NEOSYS

Topics to cover
* URL
* Turning off Pop-up Blocker
* Login Page
* Dataset
* Reset Password

===Media module===

Spend 20-30 min showing a complete schedule creation with 1 client and 1 brand, vehicle and supplier. Show schedule booking, certification and invoicing.

Topics to cover
* NEOSYS schedule per brand
* New schedule
* NEOSYS Codes
* Client and Brand file
* Supplier and Vehicle file
* Media Types
* Specification, Time, dates
* Gross unit, Other charges and exchange rate file
* Booking in a schedule
* Certifying ads in a schedule
* Invoicing ads in a schedule
* Media Diary
* Reports under Media menu
* Media Analysis

===Job Module===
Do 20-30min showing 1 Job, client and brand creation, estimate, purchase order, invoicing and purchase invoicing.

Topics to cover
* Creation of Job
* Client and Brand file
* Supplier file
* Job types
* Estimate
* Purchase order
* Invoice
* Purchase Invoice

===Finance Module===
Do 20-30min showing how to enter opening balances, link client and supplier to finance, Chart of Accounts, posting invoices on the journal entry screen, unposted batches, allocations, analysis codes and financial reports.

Topics to cover
* Chart of Accounts
* BL, PL, TD and TC charts
* Company File
* Link between Finance and Operations – Media and Job type files
* Automatic entries in Finance
* Automatic Accrual Accounts
* Manual PUR entries required if PO converted to PI when there is no estimate in the job file.
* Analysis codes
* Journal entry screen – unposted batches, posting batches and doing a manual entry
* Voucher file
* Voucher allocations in Journal entry and Allocations screen, partial allocation and de-allocation
* Journal setup
* Finance Settings
* Ledger and Statement of Account
* Financial Reports
* Billing Analysis Reports

===Timesheet Module===
Do 10-15 min showing users how to select a job and enter details in the timesheet, how to avoid reminders for holidays and timer usage.
Show Timesheet administrators how to take Timesheet printouts, how to setup hourly rates, avoid email reminders for all users and change settings in timesheet configuration file.

Topics to cover

For Users
* Selecting Jobs in timesheet
* Entering details and saving

For Admins
* Timesheet approval
* Timesheet printout and approval emails
* Timesheet files (Activity, hourly rates and configuration file)
* Timesheet Analysis

===Additional Topics===
In addition to the modules, the following points have to be explained to the users.
* File lock and release in 5 mins
* Reopen and Release
* File in use/File open for viewing only
* NEOSYS maintenance window to perform backup and updates

Configuring Thunderbird

2025-09-01T07:11:50Z

Saif: /* Shared Email Tags between Support machines */

==Setting Up the Inbox Accounts==

The instructions given below explain how to set up the "Support" account on Thunderbird.

1. Open Mozilla Thunderbird. Choose the "Create a new account" option. Click on "Skip this and use my existing email" option on the "Welcome to Thunderbird" window.

[[File:Thunderbird_1.jpg]]

2. In the Mail Account Setup window, enter "support@neosys.com" for Your Name, "support@neosys.com" for Email Address and the password provided by Neosys staff. Click on continue.

[[File:Thunderbird_2.jpg]]

3. Click on "Manual Config".

[[File:Thunderbird_3.jpg]]

4. Key in "imap.neosys.com" for incoming IMAP host name, server hostname "smtp.neosys.com" and port "587" for outgoing SMTP and "support.neosys" as username. For SMTP, change the SSL to "STARTTLS" and authentication to "No authentication". Click on the "Re-test" button and then click "Done".

[[File:Thunderbird_4.jpg]]

BEFORE clicking on inbox and BEFORE adding other inboxes, you MUST refer to [[Configuring_Thunderbird#Adding_email_accounts_with_large_numbers_of_emails | Adding email accounts with large numbers of emails]]. This is because if you add all the accounts together at once, they will all sync together and it will take 1-2 days for the sync to complete.

For backups@neosys.com, support2@neosys.com (Nagios), name.neosys@gmail.com repeat the steps mentioned above, with the below-mentioned replacements.

1. For backups@neosys.com, enter "backups@neosys.com" for Your Name, "backups@neosys.com" for Email address and enter the password provided by Neosys staff.
Enter the username as "backups.neosys".

2. For support2@neosys.com, enter "support2@neosys.com" for Your Name, "support2@neosys.com" for Email address and enter the password provided by Neosys staff.
Enter the username as "support2.neosys".

3. For name.neosys@gmail.com, enter your full name for Your Name, "name.neosys@gmail.com" for Email address and enter the password. You do not need to follow the steps for manual config as the settings will be automatically configured.

[[File:thunderbird_6.jpg]]

[[File:thunderbird_7.jpg]]

==Account Settings==

Verify that the account settings for all the accounts are entered as shown below.

[[File:acsettings1.jpg]]

[[File:acsettings2.jpg]]

[[File:acsettings3.jpg]]

[[File:acsettings4.jpg]]

[[File:Account junk.jpg|500px]]

For backups@neosys.com account, under "Synchronization and Storage", change the setting to "Delete messages more than 365 days old"

The Synchronisation & Storage settings should be changed to the settings shown below only at a convenient time, since downloading all the emails will take a lot of time for accounts with large number of emails. Also see [[Configuring_Thunderbird#Adding_email_accounts_with_large_numbers_of_emails |Adding email accounts with large number of emails]]

[[File:acsettings6.jpg]]

[[File:acsettings7.jpg]]

[[File:acsettings8.jpg]]

===Adding email accounts with large numbers of emails===

After adding email accounts with large numbers of emails, in order to avoid long wait while downloading all the emails, it is best to change the account settings - BEFORE clicking on INBOX, which triggers the download/sync - to download the bodies of only the last 30 days of emails. The email headings are always synced but that does not take long.

See Account Settings, Synchronisation and Storage.

Since searching of emails only works when the bodies of emails have been downloaded, if you need to text search all emails, then, at a convenient time, you can remove or increase the number of days in the setting and somehow trigger the full sync.

[[File:thla.jpg]]

===Configuring Outgoing SMTP Mail Servers===

By default Thunderbird adds a new smtp profile with each Inbox added.

However you only need two, main and backup.

1. Right click on any Inbox > Settings.

2. Scroll down and click "Outgoing Server (SMTP)".

3. Delete all smtp server profiles except the default and ensure your settings match below screenshot.
[[File:Smtpsettings.png]]

4. Add a new profile with settings in below screenshot.

TODO - setup backup imap2 container and add settings screenshot here. (old imap2 smtp port 2500)

==Add-ons==

#Install addons: General settings menu (Top right 3 bars) > Addons
#Search and install the addons in below screenshot.
#Configure Mailbox Alert by Right e.g support inbox > Mailbox Alert:
##Check default sound and message.
[[File:Addon2.png]]

==Other General Configurations==

===Configure inbox to display selected columns===

The below options MUST be set in Support Inbox. To do so Right click on a column heading and select the below options:

#Thread
#Starred
#Attachment
#Subject
#Correspondents
#Received: You MUST add column RECEIVED which is the email date received to email inbox because the default Date seems to be the DATE SENT whereas we are primarily interested in the date we received the email. The difference is due to delays in email servers or spam tricks.

The below options MUST NOT be set in Support Inbox

#Junk status: Emails will automatically be moved to Junk folder if the junk icon in this column is clicked. Hence remove Junk Status column so that emails are not accidentally moved to junk. To remove, right-click on a column heading and untick "Junk Status".

===Configure Mail Content===

Settings > Privacy > untick "Allow remote content in messages"

Support MUST set the "Allow remote content in messages" as blocked in Thunderbird without adding any exceptions for any email id. The reason is remote content i.e embedded images, stylesheets etc is a privacy concern as it sends your private information to the mail sender. We do not know the source of these embedded content in emails so cannot trust them as they can be web bugs.

===Configure Layout View===

Layout view should be set as Vertical view.

===Optimise Titlebar Space===

Follow below steps to merge the titlebar with the tabs bar to reduce wastage of screen space.

#Go to Settings -> General
#Scroll to the bottom and click "Config Editor..."
#Search for mail.tabs.drawInTitlebar
#Change its value to "true"

===Thunderbird Preferences===

#Preferences > Display > Advanced > untick " Automatically mark messages as read".
#Keep settings as below for Preferences > Security.
#Keep settings as below for Preferences > Composition > Spelling.

[[File:Globaljunk.jpg|500px]]

[[File:Composition.png|500px]]

===Configure MailAlert===

Right click Inbox > Mailbox Alert > Edit Mailbox Alert alerts > Select Default message. Set as below. Once set Right click Inbox > Mailbox Alert > check Default message

[[file:thsh.jpg]]

===Configure Auto Resize Image===

Set the preferences for the Auto Resize Image add-on as shown in the screenshot at the end of this section.

To handle different scenarios when resizing images in emails, follow the below steps:

*Resize all images in the email: Click "Send" followed by "Confirm" on the Auto resize screen.

*Skip resize all images in the email: Click "Send" followed by "Cancel Resizing" on the Auto resize screen.

*Resize Images only in the email trail and skip resizing new images: Click "Resize" on top of your screen and proceed with writing the email/adding new images. When ready to send the email, follow above step for skipping resize all images in the email.

[[File:Resize2.png]]

===Configure Header Tools Lite===

Set the preferences for the Header Tools Lite add-on as shown in the screenshot below.

[[File:headertoolslite.jpg]]

===Configure Dorando Keyconfig===

Menu > Add-ons > Edit Keyconfig Preferences > Disable shortcuts for 'Archive' and 'Junk' as shown in the screenshots below.

[[File:Keyconfig1.png]]

[[File:Keyconfig2.png]]

===Getting access to NEOSYS support calendar===

After confirming that the steps below are successfully done, delete your local personal calendar and make the shared support calendar the default.

In Thunderbird, add a new CalDAV network calendar by navigating to File (Alt+f) -> New -> Calendar.

[[File:Cal1.png]]

Location: https://nextcloud.hosts.neosys.com:44318/remote.php/dav/calendars/support/support_shared_by_steve/

You will have to enter your nextcloud user and pass.

[[File:Cal2.png]]

[[File:Cal3.png]]

It should show a tick if successful, otherwise you will have to Unsubscribe and try again.

[[File:Cal4.png]]

Change the new calendar properties to Refresh every 5 mins.

[[File:Cal5.png]]

===Applying filter for backup failure emails===

In order to filter any backup failure emails as Important, go to Tools > Message Filters and create a new filter with settings as shown below:

Refer to filters list of other staff members.

===Shared Email Tags between Support machines===
1. Close Thunderbird.

2. Find and open the prefs.js file in your profile directory. Check Thunderbird -> Account Settings -> Server Settings to find the correct directory.

locate ~/snap/thunderbird/common/.thunderbird/ prefs.js

nano ~/snap/thunderbird/common/.thunderbird/w9nakioc.default/prefs.js

3. Search for tags and replace them with the list below.

If adding a new tag and don't know what color code to use, then create the tag in Thunderbird so that you can select a color. Close Thunderbird and edit prefs.js. The new tag will be created with a name and color, replace them with "$label<n>.color" and "$label<n>.tag" as below. Copy the new color and tag lines, to use in next step.

<pre>
user_pref("mailnews.tags.$label1.color", "#FF0000");
user_pref("mailnews.tags.$label1.tag", "Important");
user_pref("mailnews.tags.$label2.color", "#FF9900");
user_pref("mailnews.tags.$label2.tag", "Work");
user_pref("mailnews.tags.$label3.color", "#009900");
user_pref("mailnews.tags.$label3.tag", "Saif");
user_pref("mailnews.tags.$label4.color", "#3333ff");
user_pref("mailnews.tags.$label4.tag", "Greg");
user_pref("mailnews.tags.$label5.color", "#993399");
user_pref("mailnews.tags.$label5.tag", "Arvind");
user_pref("mailnews.tags.$label6.color", "#ff6e6e");
user_pref("mailnews.tags.$label6.tag", "Follow up");
user_pref("mailnews.tags.$label7.color", "#28e2d8");
user_pref("mailnews.tags.$label7.tag", "Delay support");
user_pref("mailnews.tags.$label8.color", "#986a44");
user_pref("mailnews.tags.$label8.tag", "Pending review");
</pre>

4. Recreate across all Support machines by adding the new lines to the correct prefs.js file. Thunderbird should not be running on any of the machines, as the prefs.js file is overwritten on application exit.

5. Start Thunderbird again. Check that the new tags are available and that tagging an email on one machine reflects on other machines.

==[[Procedures#Email_Retention_Policy| Email Retention Policy]]==

==[[Procedures#Handling_junk.2Fspam_email| Handling junk/spam emails]]==

==Viewing long running processes on Thunderbird==
When setting up and configuring Thunderbird, using its Activity Manager (Tools > Activity Manager) and possibly using the header bar "Always on top" option on the Activity Manager window may be helpful to know what long running processes are being performed.

[[File:Activity manager.jpg]]

==Deleting Thunderbird accounts==
Check the option "Remove Message Data" when removing accounts from Thunderbird. Otherwise, the old messages stay forever taking space on the disk.

[[File:dt2.png]]

Select Remove Message Data option as shown below.

[[File:dt.png]]

==Clearing out old improperly deleted Thunderbird Accounts==

If you delete Thunderbird accounts without checking the option "Remove Message Data" the old messages stay forever taking space on the disk.

To locate any such unnecessary files

ls -l -h /home/*/.thunderbird/*.default/ImapMail/*/INBOX

<pre>

-rw------- 1 arvind arvind 16M May 25 16:36 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.gmail.com/INBOX
-rw------- 1 arvind arvind 668M Mar 29 08:54 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.neosys-1.com/INBOX
-rw------- 1 arvind arvind 242M May 28 14:45 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.neosys-2.com/INBOX
-rw------- 1 arvind arvind 755M May 25 12:39 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.neosys-3.com/INBOX
-rw------- 1 arvind arvind 420M Apr 24 10:27 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.neosys-4.com/INBOX
-rw------- 1 arvind arvind 13G May 28 14:37 /home/arvind/.thunderbird/odi5mrka.default/ImapMail/imap.neosys.com/INBOX

</pre>

Check the dates, which indicate the date of the last message received, to get a rough idea of what accounts are in use and not in use

Check which of the folders are currently in use by looking in Thunderbird settings for each account one by one, "Server Settings", "Local Directory"

Delete the folders and files which are not in use using whatever method you like.

".thunderbird", like all files and folders which start with a dot, is a hidden folder which you can make visible in Nautilus File Manager by pressing Ctrl+h

==Troubleshooting Thunderbird==

===High CPU usage when idling===

If Thunderbird consumes 100+% CPU when there is no activity seen on Thunderbird activity manager (Tools -> Activity Manager), then try the below steps from https://kb.mozillazine.org/Performance_-_Thunderbird :

#Go to Settings -> General
#Scroll to the bottom and click "Config Editor..."
#Search for mail.db.idle_limit
#Change its value to 30000000 (7 zeroes, not 5 zeroes) and save
#Restart Thunderbird

===Emails show wrong body===

Sometimes emails may not load correctly. Clicking an email will show some other email's body. To fix this:

#Right click the Thunderbird folder that has the issue (e.g. Inbox)
#Properties
#Repair Folder
This will rebuild the folder index that connects email subjects with message bodies.

[[File:Repair_folder.jpg]]