Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News A Few Facts As Antidote Against Microsoft's anti-ODF FUD Campaign Post 302314179 by Linux Bot on Thursday 7th of May 2009 02:45:04 PM
Old 05-07-2009
A Few Facts As Antidote Against Microsoft's anti-ODF FUD Campaign

The best antidote against FUD is facts. FUD only works when people don't know any better. So, given some recent anti-ODF FUD in the air, I thought it would be useful to provide some facts.
First, I'd like to show you who voted Yes to approve OpenDocument v1.1 as an OASIS Standard in January of 2007. ODF v1.2 is already being adopted by some now, of course, as development has continued, but Microsoft chose to stick with v1.1, so let's do the same. I think you'll find the list dispositive as to who is sincere in this picture. Next time you read some criticism of ODF, then, you can just take a look at the list and ask yourself what it tells you. And if you are a technical person, here's ODF v1.1, so you can compare any claims of deficiencies. Here's Groklaw's chronicle of the OOXML/ODF saga, where you can find many resources, including a chronology of events from 2005 to the present.
ODF v1.1 is the version that Microsoft chose to "support" in its latest Office SP2, which Rob Weir pointed out doesn't seem to actually achieve interoperability, when others -- even Clever Age, which Microsoft funded -- do. In fact, it seems to be moving in the opposite direction.Rather than fix the problems that have surfaced by responding to what is essentially a bug report, Microsoft chooses to attack the messenger and ODF, going so far as to call for Rob Weir to step down as co-chair of the ODF Technical Committee. Is the penalty for disagreeing with Microsoft a smear campaign and loss of a job? I remember what Tim Bray told us happened to him:
In 1997, as a result of signing a consulting contract with Netscape, I was subject to a vicious, deeply personal extended attack by Microsoft in which they tried to destroy my career and took lethal action against a small struggling company because my wife worked there.
To his credit, he continued to criticize OOXML, the process, even after that, but not everyone would. I remember the attack on Peter Quinn too, when he dared to choose ODF for his group in Massachusetts. And I certainly know what I've been put through since starting Groklaw. Why is it even appropriate for Microsoft to try to get anyone removed from any job or position because of criticism of their software or standard?
No. Really. I'd like Microsoft to explain that to us. I think they owe everyone an explanation. No other company, to my knowledge, behaves like that.

More...
 
rblsmtpd(1)						      General Commands Manual						       rblsmtpd(1)

NAME
rblsmtpd - blocks mail from RBL-listed sites. It works with any SMTP server that can run under tcpserver(1) SYNOPSIS
rblsmtpd opts prog DESCRIPTION
opts is a series of getopt-style options. prog consists of one or more arguments. Normally rblsmtpd runs prog. prog is expected to carry out an SMTP conversation to receive incoming mail messages. However, rblsmtpd does not invoke prog if it is told to block mail from this client. Instead it carries out its own limited SMTP conversa- tion, temporarily rejecting all attempts to send a message. Meanwhile it prints one line on descriptor 2 to log its activity. rblsmtpd drops the limited SMTP conversation after 60 seconds, even if the client has not quit by then. OPTIONS
-t n Change the timeout to n seconds. Blocked clients If the $RBLSMTPD environment variable is set and is nonempty, rblsmtpd blocks mail. It uses $RBLSMTPD as an error message for the client. Normally rblsmtpd runs under tcpserver(1); you can use tcprules(1) to set $RBLSMTPD for selected clients. If $RBLSMTPD is set and is empty, rblsmtpd does not block mail. If $RBLSMTPD is not set, rblsmtpd looks up $TCPREMOTEIP in the RBL, and blocks mail if $TCPREMOTEIP is listed. tcpserver sets up $TCPRE- MOTEIP as the IP address of the remote host. -r base Use base as an RBL source. An IP address a.b.c.d is listed by that source if d.c.b.a.base has a TXT record. rblsmtpd uses the con- tents of the TXT record as an error message for the client. -a base Use base as an anti-RBL source. An IP address a.b.c.d is anti-listed by that source if d.c.b.a.base has an A record. In this case rblsmtpd does not block mail. You may supply any number of -r and -a options. rblsmtpd tries each source in turn until it finds one that lists or anti-lists $TCPRE- MOTEIP. It also tries an RBL source of rbl.maps.vix.com if you do not supply any -r options. See http://maps.vix.com/rbl/ for more informa- tion about rbl.maps.vix.com. If you want to run your own RBL source or anti-RBL source for rblsmtpd, you can use rbldns from the DNScache (djbdns) package. Temporary errors Normally, if $RBLSMTPD is set, rblsmtpd uses a 451 error code in its limited SMTP conversation. This tells legitimate clients to try again later. It gives innocent relay operators a chance to see the problem, prohibit relaying, get off the RBL, and get the mail delivered. However, if $RBLSMTPD begins with a hyphen, rblsmtpd removes the hyphen and uses a 553 error code. This tells legitimate clients to bounce the message immediately. There are several error-handling options for RBL lookups: -B (Default.) Use a 451 error code for IP addresses listed in the RBL. -b Use a 553 error code for IP addresses listed in the RBL. -C (Default.) Handle RBL lookups in a ``fail-open'' mode. If an RBL lookup fails temporarily, assume that the address is not listed; if an anti-RBL lookup fails temporarily, assume that the address is anti-listed. Unfortunately, a knowledgeable attacker can force an RBL lookup or an anti-RBL lookup to fail temporarily, so that his mail is not blocked. -c Handle RBL lookups in a ``fail-closed'' mode. If an RBL lookup fails temporarily, assume that the address is listed (but use a 451 error code even with -b). If an anti-RBL lookup fails temporarily, assume that the address is not anti-listed (but use a 451 error code even if a subsequent RBL lookup succeeds with -b). Unfortunately, this sometimes delays legitimate mail. SEE ALSO
tcpserver(1), tcprules(1), tcprulescheck(1), fixcrio(1), recordio(1), rblsmtpd(1), tcpclient(1), who@(1), date@(1), finger@(1), http@(1), tcpcat(1), mconnect(1), tcp-environ(5) http://cr.yp.to/ucspi-tcp.html rblsmtpd(1)
All times are GMT -4. The time now is 07:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy