Re: cut command

[Bob Proulx]

Eric Blake wrote:
> ashish wrote:
> > Spam detection software, running on the system "joseki.proulx.com", has
> > identified this incoming email as possible spam.
> 
> A copy of your mail finally made it to the list, but you probably ought to
> resolve the problems detected by the spam trap so that future mail from
> you is not lost.

Because of a convergence of things one of the listhelper volunteers
had a problem trying to approve that message to the mailing list.
After several attempts they forwarded the message with all of the
SpamAssassin markup which being a different message with the wrapping
then went through.  But that was unintentional.  Sorry about that.
The listhelper volunteers were working hard to make sure that every
message made it through while keeping the spam messages off of the
list and most of the time it works very well but sometimes mistakes
happen in the face of frustrating circumstances.

As far as this particular message is concerned the Bayes Engine
statistically decided that the headers of this message were very
similar to other spam messages.  In a normal world the statistics
would be self correcting but because there is so much spam the
statistics sometimes become skewed to the point that the tool believes
that all email is statistically spam.  In this case I have no clear
suggestions that a poster could do to order to avoid this.  The spam
filtering will need to be improved.

> >    i am trying to use cut command for = printing fields  in my order but it
> >    is unable to do it.
> > 
> >    e.g. cut -d" " -f 3,1,2 = filename
> > 
> >    it always print in field = 1,2,3
> 
> Yes, cut is documented to behave this way, as required by POSIX.  From
> 'cut --help': "Selected input is written in the same order that it is
> read, and is written exactly once."
> 
> > 
> >    there is now option  available.
> 
> awk or perl are better tools for rearranging field order.

Try this instead:

  awk '{print $3,$1,$2}'

Bob