Note that you if you are applying this patch for version 4.20 or earlier,
you must first compile pine, then apply the patch and
then compile pine again. Starting from version 4.21, you must apply the
patch and compile Pine.
Once you have succesfuly applied and compiled the patch, you
can send a message through the command line as follows:
(notice that the first switch is the capital letter ,
not the pipe command , I apologize if this causes you
any confusion) This will allow you to send to and . I could send a message from a script, just
enclosing in quotes. Please read the note
Note that depending on the operative system that you are using you may want
to enclose the part of the command in quotes
(like or ), if you
receive an error
saying that the option did not have any arguments.
Also if you are planning to use this patch in conjunction with a cron job
and these suggestions do not work for you, you may want to read some
extra suggestions sent to me
by Darrel Woodard.
You can also use the option with this
command. I recommend to alias the part
to be another command, to abbreviate the command.
A new improvement for version 4.33 has been made, now you can use your roles
when sending from the command line, for doing this you need to use
You can use your second role by writting , your third role by using
the command etc.
Note that Pine will not confirm the role that you will use when sending a
message even if you have set it to use with confirmation, in that way we
reduce prompting when sending. If you want to use a specific role, use the
method of sending it as described above ( etc).
In version 4.62 I have added code so that you can use commands in Pico and
or Pine before you send a message. For example, if you want to attach a file
you can use the ^J command to attach a message. Although you can do this from
the command line with the -attach switch, you can also use this method to add
a comment to the attachment, for example the command
worked in my Linux machine to send a message with attachments from the
command line. Thanks to Paulus Raimund for the suggestion and testing a version
of this patch.
Another interesting thing you can do is to add , , or any header with any value. For example, you can
As you can see, different headers are separated by commas
...else",Other-Hea...", while their values are enclosed in
..."person@some...somewhere.else"... The full
value is enclosed between single quotes
'Cc:...is the value"'. Since this is done in the command line, the correct way to
do this may depend on your shell. The above way works in the shell.