How many want \n conversion to crlf in queueing to lmtp?
If so, why?
Net::LMTP
data ( [ DATA ] )
Initiate the sending of the data from the current message..."DATA"
may be a reference to a list or a list. If specified the contents of
"DATA" and a termination string ".\r\n" is sent to the server. And
the result will be true if the data was accepted...If "DATA" is not
specified then the result will indicate that the server wishes the data
to be sent. The data must then be sent using the "datasend" and
"dataend" methods described in Net::Cmd.
Net::Cmd
datasend ( DATA )
Send data to the remote server, converting LF to CRLF... "DATA"
may be an array or a reference to an array.
CLASS METHODS
These methods are not intended to be called by the user, but used
or over-ridden by a sub-class of "Net::Cmd"
rawdatasend ( DATA )
Send data to the remote server without performing any
conversions. "DATA" is a scalar.
____________________
For rawdatasend(), DATA may be a a scalar but the same test is made as
in datasend to see if that scalar is an array ref, and if it is, rawdatasend
handles an array as well as datasend, WITHOUT converting /n to crlf.
Is that what we want? No crlf crap?
Any badness in passing qpsmtpd's body array ref, when available
(instead of body tempfile)?
$lmtp->data;
$lmtp->rawdatasend( $transaction->header->as_string ) ;
$lmtp->rawdatasend( $transaction->{_body_array} )
if ref $transaction->{_body_array} ;
$lmtp->dataend(); # not done automatically by rawdatasend()
$lmtp->quit ;
-Bob Dodds
