Been working through an issue trying to do the sending of an email from a script that will run on a cronjob.

Now, from what I've found, the latest mailx package in portage, as of the end of last week, is version 8.1.2.20050715-r6 and the homepage entry in portage for mailx points to http://www.debian.org/. However, when you search Debian's site for mailx, you get a bunch of security advisories, with nothing more recent than 2003 and a developer list with 2 *similar* entries (e.g. heirloom-mailx a.k.a. "nail", which apparently is hosted at sourceforge under the Heirloom Project and is at version 11.25 with the last release in July 2005, and bsd-mailx which seems to be Debian's own package, and it's current stable version is 8.1.2-0.20111106cvs-1).

My question is: Is there a reason we are staying with such a legacy version of mailx?

I wanted to ask here before I went to post a version-bump request at b.g.o.

TIA._________________------
"There is no value to explaining sanity to an insane person, just as there is no value of explaining rabies to a rabid dog... They will both bite you for your effort."
-- oldbitman

I was more of the idea of getting ourselves right. It seems to me to be a bit embarrassing when you are looking online for help with a utility and everyone is telling you to use a feature that your version doesn't have. (Namely, the "-A" argument to pull account information from the ~/.mailrc.)

And, along those lines, I did find the mail-client/nail package in the portage tree which lists it's homepage as http://heirloom.sourceforge.net/. But, that brings me back to the original question of why we are keeping that legacy version in the portage tree?

I spoke with one of the devs at #gentoo-netmail who said to go ahead and put a ticket in at b.g.o, so I will do that. (Thanks again, JM.)_________________------
"There is no value to explaining sanity to an insane person, just as there is no value of explaining rabies to a rabid dog... They will both bite you for your effort."
-- oldbitman