tips and tricks
Mozilla derived web and email clients, dropping self signed certificate support.
Late in 2014, many people noticed Firefox, Seamonkey, and many other derived products no longer allowed users to easily access content using self signed SSL certificates. Often simply reverting to older product version (i.e. pre-FF 31) restores ability to access self signed SSL encrypted web and email services. This apparently is deliberate as Mozilla Foundation will soon launch a free Certificate Authority (CA) in 2015, Let's Encrypt.
Mozilla - User Agent indentifier
For Mozilla family web browsers (Mozilla classic, Firefox, Seamonkey, Camino, ...) many of the browser identification attributes can be manually adjusted. Just browse to about:config (may need to manually type this). Search for useragent.
general.useragent.extra.seamonkey default string SeaMonkey/1.0.2
If there is a web application that complains your browser is not compatible, try adjusting you browser identification string and see if works anyway.
SeaMonkey/Thunderbird - Email Riddled With Double Question Marks ?? (#mozmime)
For Mozilla family message applications (Thunderbird, Seamonkey, ...) in some cases improperly configured mail gateways may misinterpret white space characters which result in spurious junk text characters sprinkled into a message body. Work around is to browse to about:config (may need to manually type this) and adjust the mail.strictly_mime setting (make it true).
Mozilla is actually not the culprit, instead overzealous Microsoft Exchange servers that may be relaying email are. So reverting to an archaic mime protocol alas is an unfortunate workaround.
mail.strictly_mime false example.
mail.strictly_mime true example
SeaMonkey/Thunderbird - IMAP Folders
Avoid the dreaded "The current command did not succeed" message when creating sub-folders that contain other folders. Typically this can be seen when running SeaMonkey (a Firefox/Thunderbird mashup) under recent versions of Apple's OS X with client set to not allow folders to contain both messages and sub-folders.
The work around is to create two nested folders simultaneously using a forward slash.
This will result with a folder_a being a non-message containing folder, and folder_b a message only containing folder.