<commit_before>.\"
.\" %nmhwarning%
.\" $Id$
.\"
.TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
send \- send a message
.SH SYNOPSIS
.HP 5
.na
.B send
.RB [ \-alias
.IR aliasfile ]
.RB [ \-draft ]
.RB [ \-draftfolder
.IR +folder ]
.RB [ \-draftmessage
.IR msg ]
.RB [ \-nodraftfolder ]
.RB [ \-filter
.IR filterfile ]
.RB [ \-nofilter ]
.RB [ \-format " | " \-noformat ]
.RB [ \-forward " | " \-noforward ]
.RB [ \-mime " | " \-nomime ]
.RB [ \-msgid " | " \-nomsgid ]
.RB [ \-push " | " \-nopush ]
.RB [ \-split
.IR seconds ]
.RB [ \-verbose " | " \-noverbose ]
.RB [ \-watch " | " \-nowatch ]
.RB [ \-sasl ]
.RB [ \-saslmech
.IR mechanism ]
.RB [ \-user
.IR username ]
.RB [ \-width
.IR columns ]
.RB [ file
\&...] 
.RB [ \-version ]
.RB [ \-help ]
.RB [ \-attach
.IR header-field-name ]
.RB [ \-attachformat
.IR 0 " | " 1 " | " 2 ]
.ad
.SH DESCRIPTION
.B Send
will cause each of the specified files to be delivered
to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
\*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message.  If
.B send
is re\-distributing a message, as invoked from
.BR dist ,
then the
corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
.PP
By default,
.B send
uses the program
.B post
to do the actual
delivery of the messages, although this can be changed by defining the
.I postproc
profile component.  Most of the features attributed to
.B send
are actually performed by
.BR post .

.PP
If a
.I header-field-name
is supplied using the
.B -attach
option, the draft is scanned for a header whose field name matches the
supplied
.IR header-field-name .
The draft is converted to a MIME message if one or more matches are found.
This conversion occurs before all other processing.
.PP
The first part of the MIME message is the draft body if that body contains
any non-blank characters.
The body of each header field whose name matches the
.I header-field-name
is interpreted as a file name, and each file named is included as a separate
part in the MIME message.
.PP
For file names with dot suffixes, the context is scanned for a
.I mhshow-suffix-
entry for that suffix.
The content-type for the part is taken from that context entry if a match is
found.
If no match is found or the file does not have a dot suffix, the content-type
is text/plain if the file contains only ASCII characters or application/octet-stream
if it contains characters outside of the ASCII range.
.PP
Each part contains a name attribute that is the last component of the path name.
A
.I x-unix-mode
attribute containing the file mode accompanies each part.
Finally, a description attribute is generated by running the
.I file
command on the file.
.PP
The
.B -attachformat
option specifies the MIME header field formats:  a value of
.B 0,
the default,
includes the
.I x-unix-mode
attribute as noted above.  A value of
.B 1
suppresses both that and the \*(lqContent-Description\*(rq header, and
adds a \*(lqContent-Disposition\*(rq header.  A value of
.B 2
adds the file
.I modification-date
parameter to the \*(lqContent-Disposition\*(rq header.  You can
specify one value in your profile, and override it for individual
messages at the
.I whatnow
prompt.
.PP
Here are example message part headers for each of the
.B -attachformat
values:
.PP
.nf
-attachformat 0:
Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
Content-Description: ASCII text 

-attachformat 1:
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="VERSION"

-attachformat 2:
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
.fi
.PP
If
.B \-push
is specified,<commit_msg>Replaced second line of Content-Tyhpe of -attachformat 0 example.<commit_after>.\"
.\" %nmhwarning%
.\" $Id$
.\"
.TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
send \- send a message
.SH SYNOPSIS
.HP 5
.na
.B send
.RB [ \-alias
.IR aliasfile ]
.RB [ \-draft ]
.RB [ \-draftfolder
.IR +folder ]
.RB [ \-draftmessage
.IR msg ]
.RB [ \-nodraftfolder ]
.RB [ \-filter
.IR filterfile ]
.RB [ \-nofilter ]
.RB [ \-format " | " \-noformat ]
.RB [ \-forward " | " \-noforward ]
.RB [ \-mime " | " \-nomime ]
.RB [ \-msgid " | " \-nomsgid ]
.RB [ \-push " | " \-nopush ]
.RB [ \-split
.IR seconds ]
.RB [ \-verbose " | " \-noverbose ]
.RB [ \-watch " | " \-nowatch ]
.RB [ \-sasl ]
.RB [ \-saslmech
.IR mechanism ]
.RB [ \-user
.IR username ]
.RB [ \-width
.IR columns ]
.RB [ file
\&...] 
.RB [ \-version ]
.RB [ \-help ]
.RB [ \-attach
.IR header-field-name ]
.RB [ \-attachformat
.IR 0 " | " 1 " | " 2 ]
.ad
.SH DESCRIPTION
.B Send
will cause each of the specified files to be delivered
to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
\*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message.  If
.B send
is re\-distributing a message, as invoked from
.BR dist ,
then the
corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
.PP
By default,
.B send
uses the program
.B post
to do the actual
delivery of the messages, although this can be changed by defining the
.I postproc
profile component.  Most of the features attributed to
.B send
are actually performed by
.BR post .

.PP
If a
.I header-field-name
is supplied using the
.B -attach
option, the draft is scanned for a header whose field name matches the
supplied
.IR header-field-name .
The draft is converted to a MIME message if one or more matches are found.
This conversion occurs before all other processing.
.PP
The first part of the MIME message is the draft body if that body contains
any non-blank characters.
The body of each header field whose name matches the
.I header-field-name
is interpreted as a file name, and each file named is included as a separate
part in the MIME message.
.PP
For file names with dot suffixes, the context is scanned for a
.I mhshow-suffix-
entry for that suffix.
The content-type for the part is taken from that context entry if a match is
found.
If no match is found or the file does not have a dot suffix, the content-type
is text/plain if the file contains only ASCII characters or application/octet-stream
if it contains characters outside of the ASCII range.
.PP
Each part contains a name attribute that is the last component of the path name.
A
.I x-unix-mode
attribute containing the file mode accompanies each part.
Finally, a description attribute is generated by running the
.I file
command on the file.
.PP
The
.B -attachformat
option specifies the MIME header field formats:  a value of
.B 0,
the default,
includes the
.I x-unix-mode
attribute as noted above.  A value of
.B 1
suppresses both that and the \*(lqContent-Description\*(rq header, and
adds a \*(lqContent-Disposition\*(rq header.  A value of
.B 2
adds the file
.I modification-date
parameter to the \*(lqContent-Disposition\*(rq header.  You can
specify one value in your profile, and override it for individual
messages at the
.I whatnow
prompt.
.PP
Here are example message part headers for each of the
.B -attachformat
values:
.PP
.nf
-attachformat 0:
Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
	charset="us-ascii"
Content-Description: ASCII text 

-attachformat 1:
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="VERSION"

-attachformat 2:
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
.fi
.PP
If
.B \-push
is specified,
{'fraction_non_alphanumeric': 0.11771716101694915, 'fraction_numerical': 0.008871822033898306, 'mean_word_length': 3.2939169982944856, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6289528', 'n_tokens_mistral': 2628, 'n_tokens_neox': 2453, 'n_words': 1086}