Mass Migration/Bughunt For Thunderbird Tuesday
maggeth writes "mozillaZine is spreading the word of a plan to have a mass migration of users from other email clients on this coming Tuesday in order to find any remaining bugs in the migration process. 'Bring your Outlook, Eudora, Mozilla, Outlook Express, and Communicator e-mail clients with you and join us on IRC for a day of testing the Thunderbird migration features. The goal is to get as many testing migrations performed on as many clients and as many operating systems as possible and to discuss and record all the problems in Bugzilla.' Read the full article for more details and for the IRC location."
"While we test our pile of shit, could you please ask the maker of your fully functional secure fast and stable email client to disable the feature that sends me spam each time some script kiddy mails you an .exe attachment? Thank you."
.EXE.
;))
Sorry to suck the fun out of your witty comment here, but please don't confuse Outlook for Outlook Express. OL still has the occasional exploit, but it is nowhere near as bad as OLE. In all seriousness, with OLXP (released in 02 I think) you have to hack the registry to even get it to download an
(For the record, I did have a chuckle at this comment.
"Derp de derp."
Get it here and PGP/GPG all your messages, at the very least start signing them.
Better yet, get yourself a cheap old computer, set it up with linux, a good MTA (exim, postfix, qmail), an imap server, and fetchmail. Use that machine to fetch all of your mail from your ISP, in which case it won't matter if the ISP uses POP3 or IMAP. Then set up your mail clients on your dual-boot box to point to your local mail cache instead of your ISP. You can even setup the mail clients to use the local server to send mail, if you like. There'll be a small delay in receiving mail this way, though you can setup fetchmail to poll more often if you like, but I've never found that to be a problem. Finally, you can also setup a good spam solution like SpamAssassin and solve your spam problems in a single place rather than relying on the varying spam features of your different email clients (assuming they even have spam features, unlike a lot of console-based clients like pine or mutt).
There are more benefits for running your own server like this, too. It doesn't have to function solely as a mail machine. You could install Squid and an ad-killing plugin like AdZapper, and use the box as a web proxy. You could setup NAT and a DHCP server and have yourself an internal network that will support N clients, all with ineternet access, without having to buy a pre-packaged router (and you can do this with a single dialup connection, if you can't get broadband -- I don't know of any consumer routers you can buy that will dial on demand for you). You can firewall your entire internal network from a single point. You could add a wireless access point for cheaper than it would cost to buy a wireless router, plug it into a port on your switch, and have an instant wireless network. Setup samba and have an internal file share network. The sky (and hardware you have available) is the limit!
Please see bug 3157 on bugzilla.m.o
Fix was chcked in near 2004-07-16 - any nightly / milestone after that should work (excluding the security updates; that's from different code)
"If you plan to participate in this. Please remember to back up your email in case something goes wrong."
Wow, that is a great way to get a +3 informative.
Let me try:
Before you try to check for new messages, make sure that you are connected to the internet.