Hmmm, the linux binary tarball seems to be corrupt:

$ tar xvzf mozilla-i686-pc-linux-gnu-SeaMonkey_M3_BRANCH.tar.gz package/ package/nsinstall package/bsdecho package/libmozdbm.so package/libreg.so package/libxpcom.so package/libmozutil.so package/libraptorbase.so tar: Skipping to next file header

gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error exit delayed from previous errors

I tried the download more than once, so it's not a transmission error. The file is dated March 20, 6076334 bytes, md5sum 077fe635512ab76f5501300ba54924c4.

Anybody get this successfully?

Has anyone been able to get mail working in the Win32 build? I followed the instructions, but no luck.

Yep, the Linux binary tarball is definitely broken. I get exactly the same error as above.

Mail right now is touchy. Chris and I have been working on getting it to work, and I had success (as seen in the screenshot) but Chris could not get it to work, in the same build.

Basically, take your old prefs.js from a 4.x version, clear all the prefs out, and use this:

// Netscape User Preferences // This is a generated file! Do not edit.

user_pref("mail.rootFolder", "C:\\Program Files\\Netscape\\Users\\Yourprofilename\\Mail"); user_pref("network.hosts.pop_server", "Your Server"); user_pref("network.hosts.smtp_server", "Your Server"); user_pref("mail.smtp_name", "Your Username"); user_pref("mail.pop_name", "Your Username"); user_pref("mail.pop_password", "Mail Password"); user_pref("mail.identity.reply_to", "Reply To Address"); user_pref("mail.identity.organization", "Your Organization"); user_pref("mail.identity.useremail", "Your Email"); user_pref("mail.identity.username", "Your Name");

Be sure to have the correct path to the mail directory, with double slashes (\\) between each directory as shown. Put this prefs.js either in the /bin/ dir in the nightly builds or in the /x86rel/ dir in the M3 build. Start apprunner as usual (just apprunner.exe, no parameters), and select Messenger from the Tools menu. Hopefully your mail folders should show up. Chris and I are yet to be able to send or get messages with Apprunner Messenger, but that should happen soon.

netscape should stop slacking or at least slack right! Since they no longer code they can at least take the time to learn how to make a tarball. I'm downloading the source and if it's busted I'm going to be pissed.

The prefs.js pasted quite yucky, so I have posted one up for you to use. It is located here - http://www.mozillazine.org/builds/prefs.txt

Be sure to rename it from prefs.txt to prefs.js, and place it in the correct directory.

Yup my Linux download was broken as well :(

Thanks, Jason. The prefs file you provided works beautifully.

teamwork is a beautiful thing :)

Does anybody know how to fix the Linux tarball? If not, does anyone know when people who know how to fix it are going to? Thanks

The title says it (at least in my copy). Sent myself a test message, and lo and behold apprunner downloaded it.

I just tried sending a message from apprunner, and that works too. The only problem is you can't enter any text in the body of the message.

The Win32 build seems a little flaky, definitely less stable than I imagined it would be. Oh well, it put on a good show, and confirmed a bug I have been watching.

Can't wait for M4!

Oh poo.

No linux tarball.

And I spent all that time downloading for naught. Argh.

I suppose I could try to build the source...

I posted something to the mozilla site about the program linux tarball. They are now aware of it at least. No word on when it will be fixed. The source does work, but is a little flaky. I am posting this from apprunner though. :)

Also posted using M3 apprunner :-)

Jawbone,

I believe I read in the documentation that you don't get a cursor in the composition area until you actually start typing...

I used Jason's template prefs file (in a post above), and it worked fine. I was even able to receive messages. Whew! I was getting worried that I wouldn't be able to get it to work.

Zontar, you are indeed correct. Just sent myself a test message with it, and boy does that "Mozilla 5.0" in the X-Mailer header look good.

Strangely, there seems to be a case of a problem with Netscape 4.51/Win32 - I can't download the file right off the page, but I can follow the directory tree up from /pub/ to get the file... Odd... Once I get M3 installed, I'll see if it has the same problem. =-)

Jawbone,

Congratulations!

I can't get email to send or receive with either M3 or the 0320 Win32 build, even after using Jason's prefs.js template. (Thanks, pal -- I'm sure you've got it right and I've probably just done something incredibly stupid...;-) But it's still VERY nice to see the mail and composition windows spring up. And the browser part is working beautifully. :-)

Now let's just get a:hover working so the little FrontPage kiddies who can't code the necessary 3-4 lines of JavaScript themselves will quit whining and/or pointing their fingers and saying "HA ha!" like that bully kid on The Simpsons... ;-)

I have added a new line to the prefs.js.

user_pref("browser.download_directory", "C:\\TEMP\\");

Allows you to send mail (hopefully). I have not gotten it to work yet, but I was able to download messages last night. I have added this to the sample prefs.js at http://www.mozillazine.org/builds/prefs.txt . Don't forget to rename it from prefs.txt to prefs.js. If you have any tips on how to get stuff working, don't hesitate to post!

I get undefined symbol errors on my glibc2.1 system. I can't think of any other reason for this to happen, so it looks like I'm going to have to try a source compile.

error in loading shared libraries: /home/paulad/package/libraptorhtmlpars.so: undefined symbol: seekpos__9streambufli

I've been able to download mail with 0320/Win32 after correcting a dumb typo or two that I made in my copy of Jason's prefs file. I've had to shut down and reboot Moz a couple of times in order to actually read it, tho.

Alas, I still can't send mail. However, I'm on a dialup and both my ISPs are pretty flaky, so who knows where the trouble may lie...?

At any rate, I'll keep checking back here for suggestions, and if I succeed in sending, I'll be sure to pass that info along.

I thought the editor was supposed to be working -- any secrets I need to be clued in on in that department?

Thanks, everybody.

Jason --

Never mind, that last fix of yours (which I didn't see until AFTER I'd posted the previous message) did the trick.

<BIG>Thanks!</BIG>

Zontar:

You can run the editor by running 'apprunner -editor' from a command line.

As with mail composition, you won't see a cursor until you start typing.

I used to be pessimistic about Mozilla's chances of actually becoming a real web browser, but it looks like it will survive for at least one more version...

What I AM afraid of is when the time comes that Netscape dumps funding for Mozilla and development grinds to a halt because I don't see many outside developers working on this MASSIVE project.

I can only hope that it succeeds!

So far so good! I like what I see.

I'm sorry, maybe you're in on something we're not, like AOL's board, but no where have I read that Netscape intends to "dump" funding for Mozilla.

Jawbone,

Thanks for the tip. It does run, even though it doesn't do much else at this point -- Still, it's good to see.

The release notes claim it's fully HTML 4.0 compliant, but the <Q> tag still doesn't work...

The release notes claim it's fully HTML 4.0 compliant, but the <Q> tag still doesn't work...

It is not like I am into any cutting edge information, but how can a company survive while pouring hundreds of thousands of dollars into a product that is:

A. Not generating any direct revenue and B. Competing directly with Microsoft's marketing machine.

I see that in the future, Netscape may "cut their losses" and drop funding for Mozilla...