neomail-announce Mailing List for NeoMail
Brought to you by:
neorants
Menu
▾
▴
neomail-announce
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(1) |
Mar
(6) |
Apr
(2) |
May
(12) |
Jun
(6) |
Jul
(1) |
Aug
(5) |
Sep
(4) |
Oct
(2) |
Nov
|
Dec
(6) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
|
From: Neo <ne...@ne...> - 2003-11-25 16:47:42
|
Hi all. NeoMail 1.27 has been released. Head to http://www.neomail.org to get your copy. Changes from 1.26: * Added the ability to lock in user domains, instead of allowing users to choose from all domains on the server. Developed due to a donation from Caladan Communications, Ltd. (http://www.caladan.net) * Added a fix for the tell() bug that was causing file corruption on certain Perl installations. Thanks to Paulo Matos for the fix. |
|
From: Neo <ne...@ne...> - 2003-10-14 21:07:19
|
OK all,
As you may or may not have noticed on the NeoMail homepage, there has
been a link for some time to a PayPal page allowing you to make a donation
if you have enjoyed using or profitted from NeoMail in the past.
Now, I hate being the begging sort and asking for donations, but I have
seen NeoMail being used on some pretty large sites in the past, and many of
them are run by quite profitable companies or government agencies. So far,
I've received a grand total of $157.00 in donations, from 6 people (A big
thank you to Anna, Chou, Kenneth, Lloyd, Douglas, and "Leebies" by the way!)
, since putting the PayPal link on the page over 5 months ago. I know for a
fact that there are a large number of companies out there making good money
partly due to offering Webmail via NeoMail, and I had hoped to get a few
kind souls to help me out in financing a honeymoon with the woman of my
dreams, whom I'm marrying in just a bit over 2 months from now. However, to
date, that doesn't look like it's going to happen, so I'm upping the ante in
the hopes of raising a bit of extra cash to help me out. (Douglas and Chou,
contact me to obtain the respective incentives you each qualify for under
this system)
** First, for any donation in the amount of $25.00, I will be placing
your name or company name on a special "Supporters" section of the web site
linking to a site of your choice.
** Second, for any donation in excess of $50.00, I will do the above but
also place up to 25 words of your choice next to the link.
** Third, for larger donations, I will perform custom coding and
modification of NeoMail to your specifications. Contact me detailing what
you would like done, and whether or not the changes in question should be
rolled into the official release of NeoMail or performed as a work-for-hire
for your company (meaning you would retain ownership of the modified
source). I will let you know how much it would cost to have the work done.
One final qualification: neither the text nor link provided may be
pornographic in nature.
Thanks in advance for your support!
-Ernie 'Neo' Miller
|
|
From: Neo <ne...@ne...> - 2003-08-16 16:00:07
|
Hi all,
NeoMail 1.26 has been released. Here is the changelog:
Changes from version 1.25:
* Updated to use Digest::MD5 and fix a few problems with Perl 5.8.0's
taint checking. Basically just brought the codebase up to date to
allow it to run without having to download patches.
Check out http://www.neomail.org to download.
-Ernie
|
|
From: Neo <ne...@ne...> - 2003-05-07 19:00:44
|
Hi all,
I'm not dead yet!
I've made a couple of updates to the NeoMail homepage, not the least of
which is to finally move it to http://www.neomail.org, which has been a
redirect to the SourceForge-hosted page for some time.
Also, I'd like to take this opportunity to mention that since I'm
recently engaged (http://www.neorants.com/archives/00000002.html) and
looking to raise some extra cash to pay for the upcoming honeymoon expenses,
I'm both looking for contract programming work (telecommutable only) and
finally accepting donations on the homepage. If you happen to have any
connections who need some custom Perl development I'd appreciate a mention.
Likewise, if you're one of those people who is making money by using
NeoMail, and would like to share the wealth, it would come in exceedingly
handy at this point in my life.
Thanks for reading, and for continuing to use NeoMail!
-Ernie 'Neo' Miller
|
|
From: Ernie M. <em...@ch...> - 2001-12-14 01:50:54
|
Hi all, Well, it's been fun. Around 2 years of development sucking up most of my free time early on, particularly, a few code forks, near miss lawsuit, many heated arguments over everything from licensing to design choices. Seriously, though, it HAS been fun, even if it doesn't sound like it. ;) Today, I received a copy of my company's new handbook. In it, there is a clause that states that anything developed while under their employ that may be of interest to them becomes their property. Because of this, no further development will be done to NeoMail. I will continue to accept any patches, posting these at the homepage, but just won't risk working on the software given the information in the latest handbook, especially since I'm a salaried employee without set hours. This should not be held against my employer in any way, as it's becoming almost standard in employee agreements, and is solely my decision -- no direct threat has been made against me, I'm just playing it safe, fair, and legal. Any nastygrams sent in their direction will likely just cause me trouble, so unless you hate me, please don't do that. :) I apologize in advance to the thousands of NeoMail users, hundreds of which have mailed me over the past two years. I'll truly miss working on the software. I actively encourage you guys to fork as many branches of the software as you want at this point (don't call them NeoMail of course :)). A little credit would be nice, possibly something saying it was based on NeoMail, would give me warm fuzzies, but not necessary. Again, I'm sorry. :( -Ernie |
|
From: Ernie M. <em...@ch...> - 2001-07-26 18:01:06
|
Hi all. The latest and last version of NeoMail 1.x has been released. Barring a security flaw being discovered, no new versions of 1.x will be released, under any circumstances. Patches, additions, translations, and etc will be linked to from the homepage should anyone decide to set up a page to house them, as before. The new version is available from http://neomail.sourceforge.net, as always. Following is a list of the changes from 1.24, along with the new additions to the FAQ, which should either put to rest the HTML debate or stif up new discussion, either of which is interesting in itself. You can enjoy the last one with sound, linked from the homepage. :) Changes from version 1.24: * Fixed "fix" for charset introduced in 1.24. Thanks to co...@ma.... * Fixed sometimes not detecting attachment names properly. Thanks to David Mathog for the report. * Fixed problem handling messages containing header text matching the db delimiter sequence. Thanks to Mauricio Terrats for the diagnosis. * Removed dependence on CGI::escape for better CGI.pm 3.x compatability. * Removed feedback.pl and installation report mailing from this final version. * Made a few FAQ updates at the beginning of the FAQ file. The new FAQ entries: Q. Why aren't HTML e-mails supported? A. Because HTML e-mails are the most abhorrent things that exist in the e-mail world. All self-respecting mail clients that can send HTML e-mail provide an option for sending mails in both plaintext and HTML format, and NeoMail can read the plaintext version of those just fine. Anyone sending their e-mails in solely HTML format is probably someone you don't want to be corresponding with. Malicious Javascript in HTML mails is bad news. Worse yet, many spammers will send their mails in HTML only, and reference an image that is loaded from a server's CGI script, which logs your e-mail address as valid. Q. I still want HTML mail. It's a shortcoming of NeoMail that it doesn't filter out all the possible nastiness and display the HTML as best it can. A. Do you have any idea how incredibly difficult it is to ensure the absence of any HTML that could possibly be used maliciously in a processor- and memory-efficient manner? It's not possible in a purely perl CGI without incurring unacceptable performance penalties. Anyone who tells you otherwise is either lying, or not really taking into consideration all possibilities of abuse. Additionally, as NeoMail is viewed through a web browser, any time a new hole opens up in a browser, a new vulnerability exists which the user should be protected from. Guess what? Not displaying HTML messages eliminates EVERY ONE of these possibilities. Q. I STILL want HTML mail. Can't you at least include it as an option? A. In the immortal words of Arnold Schwarzenegger in Kindergarten Cop, "STOP WHINING!" I will not dedicate my time to including a feature that puts users at risk, and only serves a purpose for those who would like to send fancy e-mail advertisements or do something more nefarious. Those who are in the know support me in this decision, thank you for your e-mails. Please, just trust me. HTML was designed for the web, not for e-mail. It's one of the reasons that NeoMail's slogan is "Webmail that doesn't suck... as much." Because, let's be honest. Webmail sucks. ALL webmail sucks. Hotmail sucks. Yahoo mail sucks. And yes, NeoMail sucks. I just think it sucks less. Please understand, I don't mean "sucks" in the sense that the programs themselves don't do something really cool, I simply mean that when you compare them to the feature set and responsiveness of a standalone e-mail client, the fall flat on their face. They don't hold a candle to a custom application. Internet culture as a whole needs to get back to its roots. Protocols were used for what they were designed for. HTTP/HTML are not designed for e-mail. It's a testament to the ingenuity of thousands of people out there that they are now flexible enough to do almost anything, but you cannot expect a webmail client to be on par with a standalone POP/IMAP client. It's like trying to perform heart surgery with a dull survival knife. The tool wasn't created for the job. Standards for remotely accessible e-mail (IMAP, for instance) need to be widely adopted and clients for commonly needed functions need to be as ubiquitous as the web browser is. If so many people require something, this should not be an uphill battle. I have a mac.com e-mail address. Did you know that Apple provides a real IMAP account for access from anywhere in the world, and any new Mac has the software capable of reading it already available? Any IMAP-compatible mailreader will work, of course, but that's not the point. What we see as a need for Web-based mail is really a need for a centrally located, remotely stored, universally accessible e-mail inbox. Standards exist that can provide that now. If the standards aren't scalable enough in real-world situations, then a panel of industry talents needs to convene to create one that is. We need to stop looking at the lowest common denominator and start innovating again. And I don't mean "innovating" like that software company that shall remain nameless considers it. I mean innovation accomplished by the joint efforts of companies, government, and the Internet population at large. Because, despite what IP law, corporations, and the government might lead you to believe, the most earth-shattering innovations don't occur behind closed doors, or in tiny locked rooms. The most earth-shattering innovations occur when someone has an idea, and he or she makes it available to others, who build on it, and go from there. The important thing is that the idea doesn't get locked up in a cage at some point, unable to progress. We don't have that now. The environment on the early Internet is the closest I can honestly say we've ever gotten to it in modern times. Anyway, just some thoughts off the top of my head -- sorry for the rant but those of you know me know it's what I do best. |
|
From: Ernie M. <em...@ch...> - 2001-04-30 13:20:18
|
Hi all,
A small update, including the fix that was committed to CVS a few
weeks ago and discussed in neomail-users.
Changes from version 1.23:
* Fixed a bug in the modified attachment boundary detection change
introduced in 1.23.
* Fixed charset not being set for neomailerror() and addressboook().
* Added a link that, when clicked, will add the sender's address to
your
address book from the folder view
That is all. With any luck (and I say this almost every release lately)
this will be the last 1.x release, and I'll finally get to take the
break from NeoMail development I've been so greatly desiring then start
fresh on 2.x. A couple quick thoughts on my mind about NeoMail 2:
- I will be the sole developer -- Thanks much for the offers to the few
who have asked to be co-developers, but I've tried that in the past and
all it's ended up with is disagreements and eventual forks of the
project.
- Version 2 will be modular enough that if you don't like a particular
aspect of its design, you can create an alternate plug-in to remedy the
"problem." The subs for retrieving inbox contents, folder contents,
etc., will be in separate files and totally abstracted from main program
logic. That's the plan, anyway.
- At this point I'm unsure as to what license I'll be using for version
2. I'm still leaning towards the GPL, but I've run into a few issues
with 1.x that have made me reconsider. Whatever the case, NeoMail 2
will still be available in source code form, as I don't believe in
artificially obfuscating code. There may be licensing restrictions on
redistributing modified versions of the source, however. It's really
difficult to draw a line that says "taking this much of my source and
making some slight changes and calling it a new piece of software isn't
fair, but taking this much of my source and writing a new program around
it is completely fine." Giving this a little bit of thought has given
me a newfound respect for people writing software licenses, open-source
and otherwise. It's a tricky situation. I like Dan Bernstein's take on
distribution at http://cr.yp.to/qmail/dist.html. The "modified versions
of qmail" bit kind of captures the essence of what I'm getting at -- if
it's still NeoMail, but with a few small changes, don't go around
calling it a brand new piece of software. This has happened with a few
NeoMail clones lately. if imitation is the sincerest form of flattery,
I guess I should be happy -- but software forks are a pain in the neck.
-Ernie
|
|
From: Ernie M. <em...@ch...> - 2001-03-16 13:48:32
|
Hi all... Been a long time since the last release, which is a good
thing, IMHO, as it means the NeoMail source has stabilized. Since the
last release in January, NeoMail has hit its first birthday! Believe it
or not, on Feb. 15th, NeoMail became one year old. :)
Anyway, on to the stuff you're reading for:
Changes from version 1.22:
* Added extra checks to $from and $realname during message send, for
good
measure.
* Added Korean translation, submitted by Tsoi.
* Added support for a global addressbook, based on a patch submitted
by
Luca Salvadori <sal...@la...>. To use a central address
book,
just place a file named addressbook.central in /var/neomail, in the
same
format as a user's address book. Its contents will be appended to
the
address books of all users, after their personal addresses.
* Slightly modified attachment boundary detection, thanks to Michael
Weis.
* Hopefully solved file locking problem on Solaris/other OSes that
require a
file to be open for read-write to be lockable. Thanks to Taco
Scargo for
the report and fix.
Grab it at http://neomail.sourceforge.net, as always. :)
-Ernie
|
|
From: Ernie M. <em...@ch...> - 2001-01-24 16:03:18
|
Hi all,
New release... just some minor cleanups and a few new translations. :)
Changes from version 1.21:
* Folders now sorted alphabetically in message display, except default
folders which are prepended at the top of the list.
* Folders named "INBOX," "SENT," "SAVED," or "TRASH" cannot be created.
Note that this deliberately does not account for localized naming of these
folders as no conflict will be created by a user creating a folder named
the same as one of these in an alternate language, and it would make no
sense to block them since the user may change language prefs later.
Thanks to Alejandro Ramirez for the report.
* Movemessage() now updates the correct headerdb files and doesn't create
.db files to be orphaned later. Thanks again to Alejandro.
* Added Slovene translation, courtesy of Robert Hrovat.
* Improved cleanup on folder deletion.
* Added GB2312 Chinese translation, from Wang Man.
-Ernie
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2001-01-09 04:24:42
|
Hi all, The NeoMail trademark dispute has reached a resolution. Thank you for your support and input. Contributions to the legal defense fund will be returned or destroyed, as requested. Per our settlement agreement, NeoMail will continue to be the name of the web-based e-mail software you find here, as well as the name of NeoPets.com's e-mail service. Please remove any references or logs of the dispute you may have posted, and inform others to do the same. -Ernie |
|
From: Ernie M. <em...@ch...> - 2000-12-29 21:26:00
|
Hi all, I sent an e-mail this morning to NeoPets. Though almost everyone that sent in their opinions believed that the position I took in response to NeoPets' registration was ethically and lawfully right, the majority said that the fight just wasn't worth the money and effort I'd have to put into it. I've told them that we'll accept their offer, pending a read of the actual license fine print. Like I said before, I'm going with the majority opinion on this. To those who sent along donations to help with legal fees, thank you for the gesture. Once we've determined the wording of the contract is fair (depending on the format I might post it here for some extra sets of eyes to check out for problems) and we're accepting it, expect your checks to be returned or torn up, according to the instructions you sent along with the donations. As I've said before, it's a shame to have to back down from a position I feel in my heart is the right thing to do, but donations came nowhere near putting a dent in the expected legal fees associated with the opposition, which were around $10,000.00, and I can see your point regarding the effort not being worth it. I have a stomach/intestinal condition aggravated by stress and my life has been a living hell ever since I've been worrying about this whole thing, so it's kinda nice to see it coming to a close. Again, thank you all for your support, monetary and otherwise. -Ernie -- NeoMail - Webmail that doesn't suck... as much. http://neomail.sourceforge.net |
|
From: Ernie M. <em...@ch...> - 2000-12-20 14:42:22
|
Hi all,
News on the NeoMail trademark front -- A while back I sent a mail to
NeoPets.com asking for a clarification on their stance... An individual on
the Slashdot.org forums had told me they believed NeoPets.com's statement
had indicated their willingness to cooperate, and I was hypocritically
ignoring that. I never saw any indication that NeoPets would offer me a
guarantee of protection in writing, and would have much preferred that
NeoPets would simply alter the goods/services listed in their application
such that they would not conflict with other projects they insisted were not
the same as their own as had been indicated in my initial e-mails to them
and their legal counsel (before this whole thing got big).
It appears as though Mozilla gobbled up my e-mail that provoked their
response (or perhaps in the two weeks it took to receive their response I
screwed up) but you can gather by the content of their response to my
proposals that I'm not leaving anything out.
Read from bottom up, first is their response, then what our stance on
the issue is, from comments and votes of support I had received. Their
current proposal would protect me personally, but I don't think they're
playing the IP game quite fairly, if, indeed, there is such a thing as fair
IP. :)
Send me your votes on what you think we should do at this point at
neo...@us..., or, if you have questions for further
discussion, post them to the neo...@li.... If you
can get this information spread further than just our lists to the
open-source community at large, I encourage you to do so -- I want the
largest amount of feedback I can get -- I will act as the community says I
should.
I will get this posted to the site ASAP -- might not be until later
today, as I'm due at the hospital at noon. Thanks for all your support thus
far.
(As a complete side note, my mom is in the hospital for heart trouble,
has been since Monday night. They aren't sure if she had a tiny heart
attack or not, doing stress tests today. I apologize if I've left your
e-mails to the list or otherwise go unanswered, I've been taking off work to
be at the hospital. If you're the praying type, as I am, then pray for her
-- we'll need it, as if the stress test doesn't go well today they have to
do more invasive procedures. Thanks again.)
-Ernie
------ Forwarded Message
From: Ernie Miller <em...@ch...>
Date: Wed, 20 Dec 2000 09:21:49 -0500
To: Stephanie Yost Cameron <Ste...@ne...>
Subject: Re: NeoMail
Ms. Cameron,
While your proposal would certainly take care of me, I think you
misunderstand the aim of my entire opposition. While most companies don't
entirely grasp this, the open source community can be quite altruistic at
times. My opposition of your trademark wouldn't serve only to protect my
product's name, but to preserve the notion that a free software project can
in fact maintain its common law rights without being muscled around by a
commercial entity that has the backing of corporations, however large they
may be.
Remember, it is still my firm belief that should this continue on to the
opposition stage, NeoPets.com, Inc. will lose their trademark in full -- any
new, amended application will have to be re-filed, while were you to agree
to the narrowing of your goods/services scope now, you would spare yourself
the costs of the opposition phase, as well as the time it will take to file
a new trademark application with an amended scope that we would not oppose.
>From the USPTO:
"Use clear and concise terms specifying the actual goods and services by
their common commercial names. A mark can only be registered for specific
goods and services. The goods and services listed will establish the scope
of the applicant's rights in the relevant mark."
Your definition of your goods/services as "Electronic Mail (E-mail)
service" is far too broad for the good of the Internet community. This is
especially true since, by your own admission, your current service cannot
even send true e-mail messages. It only, at this point, allows internal
messaging among your subscribers. I am aware of the poll you are running to
find out if your subscribers want full-fledged e-mail capabilities ("Would
you like free web based e-mail from NeoPets??") which is still open, so it
would appear that you don't really classify what you now offer as e-mail
either. As it stands, your trademark application would need to be rewritten
to state an intent to use, rather than an actual use of the mark in that
context.
I understand that as a company running on VC funding, with no current
source of profitability, your company is most likely out to obtain a large
user base and as much IP as possible to make themselves attractive to a
buyer, thus the importance you would place on any patent or trademark you
have pending. However, a fund is being collected from the NeoMail/Open
Source community in preparation for this case going any further, to protect
what we would say is morally and ethically the right thing to do in this
situation.
I will forward your proposal on to the community for consideration over
the holidays. While I am doing so, however, I would encourage NeoPets.com,
Inc., in the spirit of the season, to consider who is morally correct in
this case, given the facts laid out above, and make an adjustment to their
scope of goods/services such that further litigation is unnecessary. I have
heard from various sources that much of your business is run on Open Source
software, even that to one job applicant you could be called Open
Source-friendly. If you truly wish to be friendly to Open Source, consider
the PR benefits in modifying your trademark application such that it avoids
conflict with existing open source software voluntarily, rather than being
forced to after a lengthy and costly litigation. Several prominent
technology news sites, including the often-quoted Slashdot.org, are
following this story, and I suspect that the community could garner much
more press -- I can at least guarantee favorable press regarding the
resolution of the issue on the NeoMail site itself. NeoPets stands to gain
greatly from cooperation, or lose greatly from hostility.
Thank you for your time. I will be in response with the community's
answer to your proposition sometime after the holidays if I haven't received
a response from you before then.
-Ernie Miller
NeoMail author
> Dear Mr. Miller:
>
> We have carefully considered your proposal of December 7th concerning some
> type of amicable arrangement with regard to the mark "NeoMail."
>
> In response, we propose the following: In exchange for you agreeing not to
> oppose or otherwise interfere with NeoPets' trademark application for
> NeoMail or its use of the mark, NeoPets.com, Inc. will provide you with an
> irrevocable royalty free perpetual license (in writing, of course)
> permitting you to use the mark "Neomail" in conjunction with your existing
> shareware e-mail software program (and updates thereof) free of interference
> from NeoPets.com, Inc. Regarding your suggestion that NeoPets change its
> PTO application, we are unwilling to make any changes to the application's
> description of goods and services -- and, as a practical matter, in view of
> the license that we are offering there is no need for a change. So long as
> you are in compliance with the license, you have no reason to be concerned
> with the scope of our mark.
>
> The foregoing is offered only in the interest of settlement. Nothing in
> this e-mail is intended as a full and complete statement of our rights and
> remedies, all of which are expressly reserved.
>
> I look forward to hearing from you at your earliest convenience. Please be
> advised, however, that our offices will be closed for the holidays after
> tomorrow.
>
> Most sincerely,
>
> Stephanie Yost Cameron, Esq.
> General Counsel, NeoPets.com, Inc.
>
--
NeoMail - Webmail that doesn't suck... As much.
http://neomail.sourceforge.net
------ End of Forwarded Message
|
|
From: Ernie M. <em...@ch...> - 2000-12-16 00:37:14
|
Hi all,
Posted the 1.21 release on the SourceForge servers... Going to remove it from my
workstation now. Thanks for the courtesy shown while using my workstation as a
download repository, and to the one guy who shows in my web logs as having
downloaded my remix of "Just Got Wicked" while here. ;)
Changes from version 1.20:
* The Content-Type header with charset specification is now included in all
outgoing mails. This should fix instances where MUAs weren't decoding the
content of messages with international charsets.
* Length of name and address information entered into the address book is
now limited to 50 chars for name, 100 for address. Thanks to Srinath for
this suggestion.
* Added a Swedish translation. Thanks very much to Daniel Johnsson for
submitting it.
* Fixed a problem forwarding messages with attachments when running suid
root. Nothing security related, but caused perl to bomb with an
"insecure dependency" message and not forward the message. Thanks to
Mike Dugas for the report.
* Cosmetic change to all the login.templates... Was requested by too many
people to list, just never felt like the tedious work of changing each one
for something that always looked fine to me. :)
* Made checklogin.pl chomp() the password lines before checking passwords,
for cases where users use a username:passwd format $passwdfile, where the
lines end right after each password. Thanks to Jonathan Philbin for
the bug report.
* "No messages" is now displayed in a more noticeable location in addition
to the upper-right hand corner as before, when a folder is empty.
* FEATURE FREEZE -- I mean it this time. :) Any mails requesting new features
in NeoMail 1.x will be ignored. If there are any remaining bugs to squash
I want to get that done, then focus on making a Maildir-compatible version
available again. After that, I'll take a break then start work on 2.0.
No, lack of some feature you wanted to see in 1.x doesn't count as a bug,
so don't ask. ;)
-Ernie
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-12-13 21:24:37
|
Hi all, By now I'm sure you probably know that sourceforge.net's upload FTP server is out of commission -- I've been sitting on 1.21 for several days now waiting for it to come back up to make a release, but decided to try a little experiment in the meantime. I've posted the tarball on my personal development workstation, at http://neo.charterpa.net/neomail-1.21.tar.gz ... If you're interested in grabbing it without waiting for the official release when upload.sourceforge.net comes back online, feel free. Behave yourselves, though. If all this brings me is a bunch of cracking attempts on my workstation or something, I'm not trying this again. I have to be productive on this box unless you guys want me fired. :) While you're here, feel free to check out the spartan homepage I put up for the benefit of my coworkers when I was vacationing in Hawaii,or download an MP3 of a pathetic first attempt at remixing -- the brunt of my lack of skill being borne by Cold's excellent tune, "Just Got Wicked," from the main index.html on my box. Anyway, on with the CHANGES: Changes from version 1.20: * The Content-Type header with charset specification is now included in all outgoing mails. This should fix instances where MUAs weren't decoding the content of messages with international charsets. * Length of name and address information entered into the address book is now limited to 50 chars for name, 100 for address. Thanks to Srinath for this suggestion. * Added a Swedish translation. Thanks very much to Daniel Johnsson for submitting it. * Fixed a problem forwarding messages with attachments when running suid root. Nothing security related, but caused perl to bomb with an "insecure dependency" message and not forward the message. Thanks to Mike Dugas for the report. * Cosmetic change to all the login.templates... Was requested by too many people to list, just never felt like the tedious work of changing each one for something that always looked fine to me. :) * Made checklogin.pl chomp() the password lines before checking passwords, for cases where users use a username:passwd format $passwdfile, where the lines end right after each password. Thanks to Jonathan Philbin for the bug report. * "No messages" is now displayed in a more noticeable location in addition to the upper-right hand corner as before, when a folder is empty. -Ernie -- NeoMail - Webmail that doesn't suck... as much. http://neomail.sourceforge.net |
|
From: Ernie M. <em...@ch...> - 2000-12-06 13:58:55
|
Hi all. I'd like to strongly encourage you all to visit http://neomail.sourceforge.net/neopets.html for updated news regarding the trademark issues that were the source of the legal trouble I had mentioned on the site earlier. I feel that this issue, and those like it, need to be given some attention as they'll only get worse as more and more open source software gets released by entities that can't afford to back their choices up in the legal system. It's a companion issue to software patents, in my opinion, allowing organizations to give broad, sweeping generalizations in a description of goods/services... I could go into more detail, but it's just as well I stop here and let you guys check out the page for the whole scoop. I tried submitting this story to slashdot to try and garner some publicity but they rejected it. It's sort of part of a hotbutton issue, so I'd have thought they'd post it, but oh well. :( -Ernie -- NeoMail - Webmail that doesn't suck... as much. http://neomail.sourceforge.net |
|
From: Ernie M. <em...@ch...> - 2000-12-04 23:18:17
|
Hi all,
Subject pretty much says it. :) Head to http://neomail.sourceforge.net
for the download link.
Changes from version 1.20pre4:
* Replace any carriage returns in address book entries with spaces.
* Set umask to a more restrictive setting.
* Made getmessage() a bit more efficient by using cached data for fields
in which it's useful.
* Added handling for messages of type message/rfc822. This fleshes out
NeoMail MIME support about as far as I plan to take it.
* Display the logged in user's name in the browser titlebar.
* Make foreign charsets display properly in more browsers/cases.
* Cleaned up setup.pl a bit.
* Handled a glitch that shows up with decoding the last attachment in a
message with perl 5.6.0.
-Ernie
--
NeoMail - Webmail that doesn't suck... As much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-10-29 17:23:26
|
Hi all... Long time, no release. Been kinda busy with the legal issues, and the day job, but I made a few changes that should hopefully solve some problems or at least make the problems more obvious if not. In particular, regarding DBM implementations -- this release performs a check for the two free DBM implementations, the Berkely DB one, and the GNU DB one, that are known to work well with NeoMail, before installing itself. Avoiding NDBM and NDBM compatibility layers also eliminated the concern of system-specific DB implementation file extensions, letting me statically specify .db and eliminate a setup question, always a good thing for ease-of-install. Grab your copy from http://neomail.sourceforge.net Changes from version 1.20pre3: * Properly handle dates in simple ctime() format as opposed to the more verbose ones common today. * Sender is now a link to the message as opposed to a blank e-mail to the sender in the folder display page. * Corrections in the Spanish translation provided by Alejandro Ramirez. * Berkely or GNU DBM libraries are now required. * A compatibility test is run in setup.pl to check for adequate CGI.pm version, as well as proper DBM libraries and the MD5 module. This should hopefully reduce bogus tech support mails and bug reports. * Make sure DBM files are created with proper permissions to prevent read errors later. -Ernie |
|
From: Ernie M. <em...@ch...> - 2000-10-06 16:55:30
|
Hi all.... From the homepage:
Pre3 is hopefully the final prerelease before 1.20 final. While the
warning you see during installation still applies, I'd appreciate as
many people as possible giving this one a test as if there isn't
sufficient testing, 1.20 final could be released with serious bugs, and
I don't want that happening. If you have an extra server sitting around
to stress-test it on, by all means, do it. It'll be much appreciated.
Changes from version 1.20pre2, rerelease:
* Added a Czech translation, provided by Michal ©varc <sp? This was a
cut
& paste from my mail client>
* Fixed a bug in neomail-prefs.pl that was creating user dirs with
insufficient permissions for NeoMail to access them properly all
the
time, causing mailboxes to show up empty when they weren't.
* Set the umask of the neomail processes to avoid having user
directories'
permissions affected by the system default umask.
Thanks guys,
Ernie
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-09-29 01:29:08
|
Boy -- sourceforge is acting weird..... tried posting this earlier today.
Changes from version 1.20pre, rerelease:
* Fixed a newly introduced bug with sent message dates not showing up
properly just after sending. Thanks to Roddie Hasan for the heads-up.
* Finally got around to handling two-digit years in Date fields so they
sort
right. ;)
* Message-ID headers should no longer be an issue, no matter what.
NeoMail
now computes a Message-ID for each message itself, using an MD5
checksum
of the header. It strips the Status: header before doing the checksum,
so
status changes won't affect message IDs. However, NeoMail could
find itself unable to find a message that was listed before if you're
simultaneously modifying message headers while in a NeoMail session.
That's the only drawback I can see compared to the huge benefit of
avoiding coping with handling message-id: headers or lack thereof.
I debated long and hard over whether this would break my oath of "no
additional modules required," but since most systems that ship with
Perl
installed have the MD5 module installed already as well, and so many
other
Perl scripts require it, I went ahead and implemented it. If you're
one of
the few who needs to install the module yourself, grab it from CPAN at
www.cpan.org.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-09-28 20:31:46
|
Here you go guys, sink your teeth into it. :) I think you'll love this
last change if you were having problems with messages arriving with no
message-id headers, or weird ones, or the same ones, or some such. :)
Changes from version 1.20pre, rerelease:
* Fixed a newly introduced bug with sent message dates not showing up
properly just after sending. Thanks to Roddie Hasan for the
heads-up.
* Finally got around to handling two-digit years in Date fields so
they sort
right. ;)
* Message-ID headers should no longer be an issue, no matter what.
NeoMail
now computes a Message-ID for each message itself, using an MD5
checksum
of the header. It strips the Status: header before doing the
checksum, so
status changes won't affect message IDs. However, NeoMail could
find itself unable to find a message that was listed before if
you're
simultaneously modifying message headers while in a NeoMail
session.
That's the only drawback I can see compared to the huge benefit of
avoiding coping with handling message-id: headers or lack thereof.
I debated long and hard over whether this would break my oath of
"no
additional modules required," but since most systems that ship with
Perl
installed have the MD5 module installed already as well, and so
many other
Perl scripts require it, I went ahead and implemented it. If
you're one of
the few who needs to install the module yourself, grab it from CPAN
at
www.cpan.org.
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-09-27 16:35:53
|
Hi all,
New release is out... I've posted this warning everywhere else, and
should probably do it here as well to avoid getting yelled at. The
changelog is below the warning.
-Ernie
This is a PRERELEASE copy of NeoMail. It contains drastic performance
improvements over previous NeoMail releases, but has NOT (I REPEAT, NOT)
been thoroughly tested, which is what this PRERELEASE is for. DO NOT
USE THIS VERSION IN A PRODUCTION ENVIRONMENT. Furthermore, if you do
decide to use this version, BACK UP YOUR MAIL SPOOLS AND ALL NEOMAIL
FOLDERS PRIOR TO INSTALLATION. So far, this version is working well for
me, on my workstation, but I have NO IDEA how robust it's going to be on
a system with heavy mail spool activity. It may CORRUPT YOUR MAIL
SPOOLS,
REFUSE TO RUN PROPERLY, or DEMAND YOUR FIRSTBORN CHILD AS A SACRIFICE
for
all I know (well, maybe not the last one, but the other two are a
distinct
possibility)! USE AT YOUR OWN RISK!
Changes from version 1.14:
* Modified handling of Message-ID lines to handle extremely long
message-ids
more reliably.
* Modified getmessage() to handle attachment filenames that are
inside
a content-disposition header instead of content-transfer-encoding.
* Improved internationalization support based on a suggestion and
patch
submitted by Garry Shtern. A variable $lang_charset is defined in
the
language translation file now, controlling the charset used when
sending
mail in a given language, as well as the display of messages. This
should
also make translations to Japanese and other languages that simply
won't
display properly without a charset specified possible now.
* Drastically increased speed for large folders is in this
experimental
release, based on a patch submitted by and dialogue I had with
Chun-Kie
Tung while in Hawaii. So much for not working on vacation. ;)
The code for this is new and largely untested -- heed the message
in the WARNING file -- or face great peril. :)
* A couple small bugfixes I found during perusal of the code, which I
can't
remember now for the life of me.
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-08-30 22:30:49
|
Hi guys,
Made a re-release for 1.13 just now.... The details are in the
CHANGELOG.... grab it if you had this issue with 1.13 from yesterday:
Changes from version 1.13, original release:
* Made a quick re-release of 1.13 to fix a problem some people were
experiencing with cookies... Apparently different individuals got
different variations of the problem, all causing the same result:
neomail-prefs.pl couldn't see neomail.pl's cookie. Now, according
to the
CGI.pm docs, the cookie path should be set to '/' which would work,
but
Mark Thomas informed me that it was being set to /cgi-bin/ which,
again,
should work (and was in fact the case for me) but doesn't in some
instances of rewritten URLs and the like. OTOH, thhart from the
SourceForge bugtracker says his install is setting the cookie path
to
the entire path of the neomail.pl and causting the problem. In any
case,
the version posted now has the path explicitly set to what the docs
say are
the default to avoid this issue altogether. I'd increment the
version
number for this minor change but it's easier to re-release and have
people
with the problem re-download. Thanks to both of the guys mentioned
above
for their great bug reports, with detailed troubleshooting info. I
had
gotten a couple reports without such detailed info and since I
hadn't
heard much from most people assumed it was user error. Thanks
guys!
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-08-29 17:57:00
|
Hi guys,
A couple of small changes in this release -- The primary reason I'm
releasing it now is that a lot of people behing multi-homed proxies will
benefit from the new session handling method.
-Ernie
Changes from version 1.12:
* Added JavaScript to the login page to automatically focus the
userid
field. Thanks for the suggestion Ryk.
* Changed session validation method from IP to cookie, to bypass
issues with
multi-homing proxies and the like altogether.
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-08-15 09:23:20
|
Hi all,
Nothing much this time around.
Changes from version 1.11:
* Fixed a problem where NeoMail wouldn't always display the contents of the
attachments where the first attachment was plaintext. Thanks to Elmo Recio
for the sample spool.
* Fixed an issue where NeoMail wouldn't open a message if it had a really
long message-id that was on a line of its own after the message-id: header.
Thanks to Travis Fitch for the sample mail spool exhibiting the problem.
* Added Finnish translation, provided by Mikael Puusa.
-Ernie
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
|
From: Ernie M. <em...@ch...> - 2000-08-04 19:18:08
|
Hi all,
In the process of performing a little security audit on NeoMail, I remembered
something that had been a concern of mine way back when deciding to leave out
home directory mail spool support... Been working all morning to patch the
issue, stupid mistake on my part. No reports of this being exploited have been
received, and you're only at risk if you're using home directory Mailbox files
or PINE compatibility.
-Ernie
Changes from version 1.10:
* Security fix -- I won't divulge here, anyone who checks the diffs can
surely figure it out... suffice it to say, I remembered why I REALLY hated
the idea of storing stuff in a user's home directory.
* Fix in setup.pl - Home directory Mailbox file setups weren't being
installed setuid.
--
NeoMail - Webmail that doesn't suck... as much.
http://neomail.sourceforge.net
|
1 message has been excluded from this view by a project administrator.