SeaMonkey Internet Suite

Unofficial News in English language


What about contributing to the SeaMonkey Project⁉


it’s not a secret that SeaMonkey-development is understaffed. At the right you see 2 statistic charts:

Totally 20 bugfixes / month, that is much better than (for example) at the AOo project with only 5 bugfixes each month, but much worse than in the LibreOffice project with: 545 bugfixes within 1/4 year — and see the colorful “pie“. Of course a pointless comparison, but it demonstrates the critical situation for the SeaMonkey project with very few developers.

But may be there are people with basic (or even good) bug fixing skills, who only shied from the many obstacles before they can start? Some of them can be surmounted easil:

But the next steps are much more difficult:

  • Install Mercurial, do some first steps
    Thinking about this until now my inner temptation became too strong, though there are lots of [good first bug] bugs, which should not need too much knowledge to fix them. And it would be not big, but visible progress if me and others could fix some of the bugs I find immediately. But for reaching this goal we would need a team of beginners who help each other to overcome obstacles which will appear during the beginning phase. We could start with some bugs in SeaMonkey Help and dare more demanding challenges step by step.
  • Do some first fixes
  • upload them for review

I think interested volunteers should fix a weekend with some kind of time table where they do these first steps together, help each other, might even get help of a mentor form the SeaMonkey Developers Team … .

May be we even can get some external volunteers from Hackerearth, CodeChef, TopCoder,Codeforces,HackerRank or similar communities (may be you know a better community were we can try to recruit volunteers?)? Or, if we are lucky, some “self compiling users” are willing to provide their knowledge to the SeaMonkey project?

If you have some own thoughts, please add a comment as reply to one of the threads:

  • “… – I am interested in participating”
    (only a short comment, 1 … 2 sentences concerning your background, no discussion)
  • “… – No, thanks
    (only a short comment concerning your reasons, no discussion)
  • “… general discussion
    (Ideas, criticism, anything else …)





Leave a comment

Future home of Thunderbird and SeaMonkey add-ons

I received the cited message because I’m an add-on developer registered on AMO ( and because I have an add-on that supports Thunderbird or SeaMonkey.

Firefox Quantum (version 57) launched on November 14th, with exclusive support for add-ons using WebExtensions APIs. AMO is moving forward in parallel with Firefox, and its features will progressively focus on WebExtension add-ons rather than legacy add-ons. This poses a problem in the long term for applications like Thunderbird and SeaMonkey, which don’t have plans to support the new API (legacy add-ons for Firefox will continue to be supported until mid-2018).

In order to move forward while providing continuity to the existing Thunderbird and SeaMonkey communities, we will move Thunderbird and SeaMonkey add-ons to a separate site that can be operated by their communities. We are working with members of the Thunderbird Council to make sure this transition is as smooth as possible.

We begun the first phase of this transition a few weeks ago. All add-ons that support Thunderbird or SeaMonkey will be automatically ported to the new site during this phase. However, you should expect some features for your add-ons to be temporarily unavailable, like uploading updates or even public listings. If you don’t want to be part of this process, please disable your listing by signing in to and make your extension(s) invisible, or remove Thunderbird and SeaMonkey support for all versions of your add-on.

We will share more information about this process as we move forward.

I don’t know whether someone from SeaMonkey project is involved? We have a very old note in the Status Meeting minutes, but I doubt that we really are involved.


🆕: official SeaMonkey 2.56 Nightly Trunk builds available

S e a M o n k e y y y    2.56   i i i n n   s i i i i g h h h h t ….

This blog post in German languageSince the day before yesterday we have SeaMonkey 2.56 Trunk builds available for testing here — for Linux and WINDOWS and Mac.

Only for testing, you will use those developer-builds on your own risk. I recommend to create a backup of your User Profile before you start testing those builds. My first experience with SeaMonkey 2.56 is that it is too buggy to be used, especially the email client causes lots of crashes.

Leave a comment

SeaMonkey 2.49.1 (ESR) – additional Release Notes

Blogpost Version 2017-11-08 (Sprachpaket-Version)

releasesSimilar blog post in German languageWe have a new release: SeaMonkey 2.49.1 (ESR)

Additionally to the official Release Notes here you find some more information concerning changes with SeaMonkey 2.49.

You need a Bugzilla-Account for the queries here in the blogpost. All queries without any liability, because (not only) correct use of TARGET MILESTONE is controversial.

Mistakes in official Release Notes

I don’t know.

New features

Continue reading

1 Comment

AMO Browsing for SeaMonkey: New Version 0.9.17rc1 with enhancements tested successfully

compat1After repair version 0.9.16 Isaac Schemm now created a new  version 0.9.17 with some enhancements. RC is available for testing on github, release will be available on AMO, soon,

I did several tests with unzipped installer of official en-US SeaMonkey 2.53a1 (NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 Build 20170706013410 (Default Classic Theme) on German WIN7 64bit and checked various functions, which were broken before. For these tests I used some Add-Ons from compatibility list. If you want to do tests directly from AMO, you will have to select an Other Application like Firefox; from the AMO SeaMonkey Area search will only show add-ons which are compatible with SeaMonkey. The FF-AMO-Area already show the new AMO design.

I did my tests from AMO FF Area.

  • 👍 Suppress”FF-Only” button, tested with BlockSite from Search Results list.
    • ✅ [+ Add To FF] or similar button  will be suppressed in search result list (which shows old AMO design) an replaced by “Convert this add-on here” – links.
    • ✅ On add-on download page [+ Add To FF] button is replaced by Convert Add-on link.
    • ✅ Conversion link in added explication text works fine
  • 👍 Useful Text for add-ons built with WebExtensions, which can’t be used with SeaMonkey and which can’t be converted with Add-On-Converter — tested with LEO Dictionaries 3.0 (and YouTube a MP3 1.0.6)
    • ✅ Adds explication to AMO web page for add-on
      • ✅ check previous versions – link works fine

        Convert Previous Version

        • ✅ Conversion link on previous versions page (replaces [+ Add to Firefox]) works fine
  • 👍 Find SeaMonkey Version of add-on — Tested with Lightning 5.4
    • SeaMonkey version of this add-on exists!– link is available and works fine, finds SM version


Did I forget something? All functions I tested worked fine

@Isaac: Thank you for great work.