Re: [msmtp-users] msmtp 1.6.0rc1 is released!

[grarpamp <grarpamp@...20...>]

On Tue, Dec 2, 2014 at 11:26 AM, Matus UHLAR - fantomas
<uhlar@...186...> wrote:
>>> >- From: and Date: headers are now added to mails if necessary
>
>>On Tue, 2 Dec 2014 14:24:05 +0100, Matus UHLAR - fantomas wrote:
>>> btw, can this be turned off?
>>> I've been happily using msmtp as smtp client to check servers'
>>> antispam filter.
>
> On 02.12.14 16:22, Martin Lambers wrote:
>>This can currently not be turned off, because it is the expected
>>behavior of the /usr/sbin/sendmail interface that msmtp tries to be
>>compatible with.
>>
>>However, we could add options to turn this off if there is a use
>>case for it.
>
> haven't I mentioned it already?
>
> I've been using msmtp as simple smtp client for checking spam/virus filters.

I previously suggested here that there should be options to
override any field with user supplied data, or set such fields
to NULL. For server testing purposes. ie: other than (and after) the
login authentication (which is also technically user supplied fields)...
all other interaction with the server, such as 'mail from', 'rcpt to'
and the 'data through to . (dot), including any proposed msmtp
supplied "headers" therein should be allowed to be arbitrarily settable,
even to NULL. Otherwise you have to write your own SMTP backend
and feed such fields to it. Why bother when msmtp provides a great
SMTP backend already that can be scripted well.

Defaulting to the RFC required supplying of fields based
on parameters/DATA given to msmtp is correct for normal users.
For this default operation, searching 'from:' or 'date:'
in rfc 5321 and 5322 gives relevant info.


Overriding such things is useful for system administrators.

How would such overrides be given to msmtp?
It would seem to be needed on the command line
or in the config, since the 'DATA' part sent is I think already
parsed/interpreted by msmtp if it's missing/NULL or not
matchable by msmtp. So maybe like...

--rfc-body-from="<string|NULL>" , where NULL may be said by just '=""'.
--rfc-body-date="<string|NULL>" , where NULL may be said by just '=""'.

Where the value completely literally controls that field line presence:
--rfc-body-from="" --> no line injected in DATA at all
--rfc-body-from="blah" --> 'blah'
--rfc-body-from="Fro" --> 'Fro'
--rfc-body-from="From: " --> 'From: '
--rfc-body-from="From: a b <a.b@...45...>' --> obvious


[I don't like the phrase 'sendmail [interface] compliant'. Sendmail is
no longer sole and king by default. In fact, others such as postfix
have risen well, such that 'RFC compliant' is probably the more useful
phrase now, to which all competing MTA's need adhere.

Does anyone know of a community/formally developed spec/doc/link for
the MTA/MSA 'commandline interface' as called by MUA's (other than
"just clone what sendmail does"?]