On 2020-05-06 11:44:06 +0200, Christopher Zimmermann wrote:
> Hello dear mutt developers,
>
> I prepared a merge request that needs some consideration.
>
> Why? I use mutt on OpenBSD with heavily customized vi-like key bindings and
> colouring. Especially I'm used to line-wise scrolling being bou
On 06May2020 11:44, Christopher Zimmermann wrote:
Hello dear mutt developers,
I prepared a merge request that needs some consideration.
Why? I use mutt on OpenBSD with heavily customized vi-like key
bindings and colouring. Especially I'm used to line-wise scrolling
being bound to \Ce and \Cy
On Wed, May 06, 2020 at 11:23:32PM +0200, ilf wrote:
Kurt Hackenberg:
I guess msmtp is obsolete for Mutt users anyway, since Mutt now
contains an SMTP client.
No, msmtp is not obsolete for Mutt users. People have different
requirements, and it's good Mutt allows choice. (Mutt is an MUA, not
Kurt Hackenberg:
I guess msmtp is obsolete for Mutt users anyway, since Mutt now
contains an SMTP client.
No, msmtp is not obsolete for Mutt users. People have different
requirements, and it's good Mutt allows choice. (Mutt is an MUA, not an
MSA afterall. :)
-- sent with msmtp
--
ilf
If y
On Wed, May 06, 2020 at 04:12:27PM -0400, Kurt Hackenberg wrote:
Agreed.
I don't know of any expicit documentation of this either, but it seems
to be standard practice to convert in both directions between the
network form and the local form at the boundary between the network
and the local s
On 2020-05-06 15:32, Claus Assmann wrote:
On Wed, May 06, 2020, Kevin J. McCarthy wrote:
I suspect this is the contention point for opensmtpd. When invoking
$sendmail directly the headers and delimeter are all just LF. Is this
expectation that the MSP perform conversion documented anywhere?
On Wed, May 06, 2020, Kevin J. McCarthy wrote:
> I suspect this is the contention point for opensmtpd. When invoking
> $sendmail directly the headers and delimeter are all just LF. Is this
> expectation that the MSP perform conversion documented anywhere?
Not in an RFC as that's just a local pr
On Wed, May 06, 2020 at 08:44:29PM +0200, Claus Assmann wrote:
On Wed, May 06, 2020, Kevin J. McCarthy wrote:
RFC5322 states that headers and the header/body delimiter are
supposed to be CRLF, but I (and ticket #235) note that mutt is
writing them with just LF.
Thank you for your reply, Clau
On Wed, May 06, 2020, Kevin J. McCarthy wrote:
> RFC5322 states that headers and the header/body delimiter are supposed to be
> CRLF, but I (and ticket #235) note that mutt is writing them with just LF.
That's for SMTP -- if mutt is talking to an MTA (or MSA) it must
use CRLF (though some MSAs fi
I'd appreciate feedback on an area I'm not too clear about.
RFC5322 states that headers and the header/body delimiter are supposed
to be CRLF, but I (and ticket #235) note that mutt is writing them with
just LF.
The ticket reports this is causing opensmtpd to choke.
However, given that Mutt
Hi Christopher,
On Wed, May 06, 2020 at 11:44:06AM +0200, Christopher Zimmermann wrote:
> New functions `suspend` and `interrupt` are implemented.
> `suspend` is used to trigger SIGTSTP and is bound to \Cz by default.
> `interrupt` calls `mutt_query_exit` and is used to mimic the \Cc behaviour.
I
Hello dear mutt developers,
I prepared a merge request that needs some consideration.
Why? I use mutt on OpenBSD with heavily customized vi-like key bindings
and colouring. Especially I'm used to line-wise scrolling being bound to
\Ce and \Cy. \Cy can not be bound using the ncurses backend on
12 matches
Mail list logo
