use of the
comma if you want to also handle the case of
To: "Dearest, My"
Ultimately this is a case of which failure mode you prefer: sending an
email with the smoochy signature to your manager at work, or sending
an email with the default signature to your wife. Optimizing for the
latte
onal header which you can unignore normally.
--
Michael Kjörling
🔗 https://michael.kjorling.se
you can do that from
within WSL; with or without "needsterminal" in the mailcap.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
med with a -Old suffix. See the formail man page.
I have a number of similar rules in my setup and it works like a
charm. The biggest caveat is that procmail operates on the _raw_
message, so for example if the sender name may be surrounded by quotes
or encoded somehow, you need to account for that.
ine is:
set attribution="On %{!%-e %b %Y %R %z}, from %a (%n):"
The %{} stanza expands to the date and time of the message I'm
replying to, and is passed to strftime(3) as also described under
$date_format. In turn, %z is the time zone specifier; in your case,
"-0500".
Hope thi
term
support (it's now ELTS) since about a week, and Debian 11 stops
getting security updates very soon (Wikipedia puts end of security
support for Debian 11 at July 2024). Current stable is Debian 12.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
eason to turn
it off.
In my case, I have explicitly set $send_charset="us-ascii:utf-8" for
best adherence to RFC 5198. (Technically, since everything US-ASCII is
also valid UTF-8, I could in principle remove the US-ASCII part; but
with it, if an email can be represented in US-ASCII, the re
an page, it doesn't appear
that w3m has anything similar.
In case it helps, my mailcap entry using lynx is:
text/html; /usr/bin/lynx -width=$COLUMNS -dont_wrap_pre -dump -force_html
-localhost -assume_charset=%{charset} -display-charset=utf-8 %s; copiousoutput
--
Michael Kjörling
in place of \n in the bind command? Per
http://www.mutt.org/doc/manual/#tab-key-names \n is technically
interpreted as "newline" whereas is interpreted as the Enter
key; that seems like it might be significant here.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
ldn't that at a minimum cause a discrepancy between the message-ID
of what is actually sent, and of what is stored in the Fcc?
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
following that requirement _is_
going to cause a variety of issues, quite possibly up to and including
messages not being delivered properly. Violate that requirement at
your own peril.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
; the
others effectively set overrides for the default.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
://michael.kjorling.se/internet-reserved-names-and-networks/
helpful.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”
script put the replacement contents (including headers if those are
passed in) back in the named file when you're done, return success,
and you should get much the effect you're after.
--
Michael Kjörling 🔗 https://michael.kjorling.se
“Remember when, on the Intern
; even when there is a problem
> (and the mail is not sent). I always used a simple msmtp configuration,
> and could not identify any major changes in the msmtp docs related to
> exit codes.
What's your $sendmail_wait?
--
Michael Kjörling 🔗 https://michael.kjorlin
15 matches
Mail list logo
