On Sat, 16 Mar 2019 22:14:41 -0600, "Anthony J. Bentley" said:
> "mhshow: invalid BASE64 encoding in --"
>
> Since it's a public mailing list, one of these messages is enclosed below.
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: base64
Yeah that's a reasonable thing to
On Sun, 17 Mar 2019 09:28:53 -0400, David Levine said:
> More generally, what if a sender (improperly) had annotated an already
> encoded message with, say, "DO NOT FORWARD THIS!"? Bad, yes, but could lead
> to
> undesired results if that was dropped.
My reading of RFC2045 says a conforming bas
On Sun, 17 Mar 2019 17:29:16 -0400, Ken Hornstein said:
> >My reading of RFC2045 says a conforming base64 decoder is allowed to toss out
> >the blanks and the '!' char and decode the rest.
> >
> > Any characters outside of the base64 alphabet are to be ignored in
> > base64-encoded data.
> >
>
On Sun, 17 Mar 2019 20:43:40 -0400, David Levine said:
> Note the "in base64-encoded data". The characters in the footer are after
> the end of the base64-encoded data, per the use of "end" here:
>
>Special processing is performed if fewer than 24 bits are available
>at the end of the dat
On Mon, 18 Mar 2019 21:10:45 -0400, Ken Hornstein said:
> But the email you sent out was marked as having a character set of UTF-8
> with characters encoded as ISO-8859-1. Dude, I know you could do better
> (also, I am puzzled as to how that happened; I think with nmh you'd have
> to work to make
On Sun, 21 Apr 2019 17:05:58 +0100, Ralph Corderoy said:
> works. If so, then /etc/nmh/mts.conf's `servers' entry isn't being
> obeyed. Either it isn't being read, or its getting trumped by something
> else.
I wonder if the file got installed with wrong permissions? I've seen installers
screw th
On Sun, 21 Apr 2019 18:29:57 +0100, Ralph Corderoy said:
> ISTM it's also a bug to ignore problems opening a file that exists, and
> to ignore a file given in an environment variable not existing.
I agree on the first. The second probably need to be more nuanced, and
"a *specific* file given in
On Tue, 23 Apr 2019 13:35:44 +0100, Ralph Corderoy said:
> It's not the only one, e.g. docs/historical/mh-6.8.5/uip/post.c has
>
> 2622 if (fd != 0)
> 2623 (void) dup2 (fd, 0);
> 2624 (void) freopen ("/dev/null", "w", stdout);
> 2625
On Wed, 24 Apr 2019 00:01:08 +0700, Robert Elz said:
> I don't know why fd 3 was wanted to be a dup of stdin, but aside from
> that oddity, there's notthing remarkable about the code (no WTF), the
> test is just avoiding a (pointless) dup2(3,3).
>
> Whatever fd 3 was before executing this code, it
On Tue, 23 Apr 2019 13:34:26 -0400, Ken Hornstein said:
> As discussed here:
>
> https://lists.gnu.org/archive/html/nmh-workers/2019-02/msg00035.html
>
> Currently our message/partial support does not work. I believe fixing
> it is straightforward, but given the links that David posted in th
On Wed, 24 Apr 2019 03:46:04 +0700, Robert Elz said:
> fd is also made to be fd 3.
>
> If it is good enough to be stdin, it is good enough to be 3 as well,
> if there is (or once was) some reason this is important.
Derp. -ENOCAFFEINE :)
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo
On Sat, 04 May 2019 06:16:27 -0500, n...@trodman.com said:
> This is OT/not a nmh issue. It does concern spam unicode chars in the mail
> header
> though, so maybe you could direct me a bit.
> I use procmail, so I should be able to filter out msgs like the above,
> but I could use some tips on a
I know %(num) gets you the current message number in a folder. Is
there an easy way to get the *name* of the folder?
(Part of a truly bletcherous plan to use Fcc: and/or Bcc: to subvert GMail's
auto-suppression of messages that result in you usually not getting a copy of
mail you post to a list, b
On Fri, 10 May 2019 12:58:22 -0400, Ken Hornstein said:
> >And many MIME-extension-fields may be present.
> >https://www.rfc-editor.org/rfc/rfc2045.html#section-9 suggests that's a
> >header matching /^content-/i, including `Content-: foo', I presume,
> >unless some RFC says a header can't end in
On Fri, 10 May 2019 23:30:45 -0400, Ken Hornstein said:
> Hoo boy, some names from the past in that thread. And Valdis, of course :-)
Hey, I didn't post at all in that particular food fight. :)
pgpZ7HdwrlIx4.pgp
Description: PGP signature
--
nmh-workers
https://lists.nongnu.org/mailman/listi
On Thu, 16 May 2019 20:56:28 -0400, Ken Hornstein said:
> It occur to me that this might still be useful, but making this switch
> on a component is obviously wrong, and it should really be a function
> escape. So I propose we switch all of the default scan formats from
> using %{encrypted} to a
On Thu, 16 May 2019 23:10:32 -0400, Ken Hornstein said:
> >Note that 'E' in the format is different to the alternate annotations
> >that can occur in the same position (and trump the E if more than one
> >applies) in that the others tell what I have done to the message
> >(that I have replied, or
On Fri, 17 May 2019 14:01:53 -0400, Ken Hornstein said:
> Apologies to our friends across the pond, but I noticed the #ifdef UK
> in scansbr.h today, and I couldn't help wonder if anyone still uses this.
As noted elsewhere, it probably shouldn't be an ifdef. On top of
that, the behavior selected
On Sun, 19 May 2019 01:24:26 +0700, Robert Elz said:
> That's it, entirely -- nothing related to ancient UK backwards domain
> names or anything else exotic like that.
I always wished the rest of the Internet had gone that way - it would have
made it at least theoretically possible to tab-complet
On Thu, 23 May 2019 13:45:02 -0400, Jude DaShiell said:
> echo "first available message:"
> scan -width 6|head -1
scan -width 6 first will be much faster.
> echo "last available message:"
> scan -width 6|tail -1
scan -width 6 last will be much faster.
If you have 10,000 entries in a folde
On Sat, 25 May 2019 10:37:17 -0400, aalin...@riseup.net said:
> Is there a way to do something similar in nmh? If not how do nmh users handle
> such a situation?
Hmm.. 'anno +folder cur -component X-Reminder -text "Pay This Bill"
and then run scan `pick -component X-Reminder`
Or 'refile +re
On Sun, 26 May 2019 10:12:56 +0100, Ralph Corderoy said:
> anno does have a -component option, but pick doesn't.
> I think you mean
>
> scan `pick --x-reminder bill`
>
> with the double dash.
Gaah. And I even checked 'man pick' because I don't use 'pick' that often, so
figured I better doubl
On Sat, 01 Jun 2019 18:51:35 -0700, Bakul Shah said:
> If you are calling procmail from ~/.forward, mail may not be
> left in your system mailbox
Also true if you've configured your system to skip a step and invoke
procmail as the local delivery agent directly
pgp1hCsM6HcIT.pgp
Description: PGP
On Mon, 03 Jun 2019 15:58:18 -, masud.anw...@hmrc.gsi.gov.uk said:
> 73 * bool is a built-in type in standard C++ and as such is not
> 74 * defined here when using standard C++. However, the GNU compiler
> 75 * fixincludes utility nonetheless creates it's own version of this
On Mon, 03 Jun 2019 15:58:18 -, masud.anw...@hmrc.gsi.gov.uk said:
> I get the following compile errors compiling on solaris 10 - sparc and I'm
> not sure how to resolve it.
> Sun Compiler developer studio ansi C compiler
> "/usr/include/curses.h", line 86: invalid type combination
> 8
On Tue, 04 Jun 2019 13:08:43 -0400, Ken Hornstein said:
> True story: a long time ago we had a number of IRIX systems. The inetd
> on those systems was buggy so it was common when you changed the inetd
> configuration you just restarted it instead of sending it a HUP signal.
> But even though the
So trying to work with the linux-kernel mailing list firehose (800-1500
messages a day), and hitting a problem with 'pick'.
Am trying to match all messages from a given person with a given part of
a subject line.
pick -from -subject '\[PATCH [45]\.[0-9]'
*almost* does what I want - catch al
On Sat, 08 Jun 2019 14:55:01 +0100, Ralph Corderoy said:
> I often switch to another user to see if they've any new email they'd
> like to know about. All I really need for that is setuid inc that scans
> the From and Subject fields.
At which point the other user can't use their preferred mail t
On Fri, 07 Jun 2019 16:19:15 -0700, Bakul Shah said:
> You can directly use search as follows:
>
> -search 'Subject[ \t]:[ \t]*\[PATCH [45]\.[0-9]'
[~] grep ^Subject Mail/linux-kernel/321805
Subject: Re: [PATCH 4.9 04/20] net: Fix for_each_netdev_feature on Big endian
[~] scan `pick +linux-
On Sat, 08 Jun 2019 17:17:40 -0700, Bakul Shah said:
>
> So pick runs -search on header lines as well as the body a header specific
> option is only run against headers.
In a world of Microsoft Office attachments, is having -search go through the
body by default as well still a good idea? Maybe ha
On Mon, 10 Jun 2019 11:25:30 -0700, Bakul Shah said:
> On Mon, 10 Jun 2019 18:45:45 +0100 Ralph Corderoy
> wrote:
> >
> > > Like "Undo Send" ... how does THAT work?
> >
> > What now? send -delay 30m
>
> Great idea! Until actual send occurs, the message stays in
> +outgoing. "send -delay 5m"
On Mon, 08 Jul 2019 17:25:42 +0100, Ralph Corderoy said:
> Is -42nd handled?
I admit being totally mystified as to what situations require proper handling
of negative ordinals
pgpM4SES7TBLk.pgp
Description: PGP signature
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
On Tue, 09 Jul 2019 17:43:06 -0400, Steven Winikoff said:
> sm_reply.length = rp - sm_reply.text;
> sm_reply.text[sm_reply.length] = 0;
> +#ifndef NOSYSLOG
> +if (strncmp(sm_reply.text, "OK id=", 6) == 0)
> +{
This is highly dependent on the remote MTA.
Google, for ins
On Tue, 16 Jul 2019 09:44:58 +0100, Ralph Corderoy said:
> Hi Ken,
>
> > >Content-Type: text/html; charset="ansi_x3.4-1968"
> >
> > That character set is interesting.
>
> The 1968 revision allows LF to occur on its own compared to 1967's where
> it always had to be LF CR or CR LF, but other tha
On Thu, 25 Jul 2019 11:09:38 -0500, n...@trodman.com said:
> On Tue 7/23/19 21:44 -0400 Ken Hornstein wrote:
> >> mhannotate=Resent mhaltmsg=~/Mail/sent/bar mhdist=1 send
> >> ~/Mail/drafts/foo
> >
> >It wouldn't surprise me that the problem is that ~ in mhaltmsg. Is that
> >actually being exp
On Thu, 26 Sep 2019 12:36:41 -0400, Ken Hornstein said:
> I received this email, and I wanted to pass it along. The executive
> summary is: in the near future subject lines to nmh-workers will no
> longer be prefixed with "[nmh-workers]" and there won't be a footer
> at the end of the message any
On Sun, 20 Oct 2019 12:11:03 +1000, Alexander Zangerl said:
> personally i think spending any further effort on verifying addresses for
> deliverability on the sending side is wasted because of how little
> verification/guarantee it provides (see bugs section in man whom).
The only thing I've eve
On Sun, 03 Nov 2019 15:08:12 -0500, David Levine said:
> And it looks like BCC: has never listed the bcc recipients. This
> is from the MH 6.8.5 post.c:
>
> fprintf (out, "BCC:\n");
That's proper behavior. BCC is *blind* carbon copy, specifically intended
to *not* show who else got copies. I
On Wed, 06 Nov 2019 19:56:45 -0800, "Chris Richmond" said:
> Not sure what you need to know, but this is on a current Devuan 2.0.0
> install. This is what failed:
That's unusual behavior. Can you tell us where you got the source tree,'
and what release of gcc you're using?
4 of 108 tests fai
On Wed, 20 Nov 2019 10:41:34 +0530, Greg Minshall said:
> hi. i'd like first, of course, to thank you all for nmh!
>
> then, i'd like to use something like fmttest(1) to print out all the
> "Received:" lines in an e-mail message. ideally, each "Received:" line
> would come out on a separate line;
On Fri, 22 Nov 2019 20:51:52 +0100, Steffen Nurpmeso said:
> I prefer people using Mail-Followup-To: instead of some ML
> software modifying the address lists, they could as well just
> avoid resending the mail!?! Yes, i mean, well.
> I really like looking into old archives and i hope what i see
On Thu, 05 Dec 2019 15:54:50 +, Ralph Corderoy said:
> Hi Ken,
>
> > Norm, if you create a .netrc file I bet it will work. If you've
> > forgotten the format of a .netrc file, you want the file to contain a
> > line that looks like this:
> >
> > machine pop.gmail.com login normanzalmonshap...@
On Thu, 05 Dec 2019 21:30:22 -0500, David Levine said:
> The description or the semantics? It really did/does use the login
> name for the password. I think it's long past time that we remove
> that.
Gaak. That's so "No Even Wrong" that every time I've read that, I've
parsed it as "use the log
On Mon, 16 Dec 2019 07:39:48 -0800, n...@dad.org said:
> With Comcast as my Internet Provider, Gmail as my Email server, and nmh as my
> Email client, all seems to be well. Thank you so much.
Glad it all worked out for you. :)
pgpAuDIi0uk1Y.pgp
Description: PGP signature
On Mon, 24 Feb 2020 21:10:15 -0500, aalin...@riseup.net said:
> This is the raw email From line:
>
> From: "The New Yorker"
>
> And this is the line in my ~/.fdm.conf file:
>
> match "^From:.*@eml.condenast.com" in headers action pipe
> "/usr/local/libexec/nmh/rcvstore +trash"
>
> My question is,
On Tue, 25 Feb 2020 12:26:48 +0700, Robert Elz said:
> There was a caret there in the message I saw (0x5e) which perhaps
> your font is somehow missing (here it is: ^). Assuming that means
Gaak. Totally right.
Now I have to delve into two messes. Why my laptop has a font that borked,
and why
On Mon, 23 Mar 2020 13:16:56 +0100, Philipp said:
> [2020-03-22 14:53] Ken Hornstein
> > >We think currently about removing the Previous-Sequence support for
> > >mmh. But because we don't use it we are not sure, if we missed some
> > >aspect of it. Therefor I would like to ask some questions.
> >
So I got a user report that exmh was doing something weird with bcc:.
I looked at the exmh code, which doesn't do anything special with bcc:,
it just assumes that the underlying nmh will DTRT.
So.. I go to test nmh. As tested, it had:
From: "Valdis =?utf-8?Q?Kl=c4=93tnieks?="
To: valdis.kletni
On Sat, 11 Apr 2020 23:05:25 -0400, Ken Hornstein said:
> >So I got a user report that exmh was doing something weird with bcc:.
> >[...]
>
> Geez, Valdis, people have only talked about (n)mh's weird bcc for ...
> 30 years? :-) Even in threads you have commented on, as recently
> as a year ago:
>
On Sun, 12 Apr 2020 14:54:31 +0700, Robert Elz said:
> That will be do that is one of the addresses is bad (and the receiving
> MTA can work that out - which it once would have often done, and sadly these
> days, amost never) then the message gets delivered to no-one, rather than
Well, the -snoop
On Sun, 12 Apr 2020 18:59:01 +0700, Robert Elz said:
> Yes, so both were OK, which means it is OK to transmit the message.
>
> That needed to be done in two different SMTP transactions, to avoid
> revealing the bcc user's address to the other user (nmkh doesn't
> know they're both you).
But if it
On Fri, 29 May 2020 14:41:05 -0400, Ken Hornstein said:
> > 2) would it be reasonable to have a mh-format that returned the number of
> > hard links so that I could see in my scan that it was also stored
> > elsewhere?
>
> That should be relatively straightforward, although it sounds like
On Thu, 02 Jul 2020 21:58:04 +0100, Justice Jvsta said:
> I don't know what next to do am stuck with the command
Well... it says it can't change to the directory. Investigate why.
/data/data/com.termux/files/home/Mail/inbox (Egads. :)
Does it exist? Is it the directory you *expect* your inbo
On Mon, 31 Aug 2020 20:44:42 -0400, Ken Hornstein said:
> >- Paragraph 4.b.1, which states that "You will keep your credentials
> >> confidential and make reasonable efforts to prevent and discourage other
> >> API Clients from using your credentials. Developer credentials may not be
> >> embedded
(Merging replies to two related items)
On Sat, 26 Sep 2020 00:14:59 +0100, Conrad Hughes said:
> Just saw this for the first time:
>
> Content-Disposition: =?utf-8?Q?inline?=
I can do you one better.. In my folder of broken mail that gives exmh
heartburn, I found this one back in 2016:
X-Maile
On Tue, 23 Mar 2021 16:09:38 -0400, Ken Hornstein said:
> We USED to use $(...) in the test suite. But that was dropped because
> it turns out that /bin/sh on Solaris does not support that (at least, that
> was my memory). I am neutral about whether or not we should continue
> to support ancient
On Sun, 02 May 2021 19:23:06 +0100, Ralph Corderoy said:
> I went for -range because it's controlling the printing as âlo-hiâ and
> mh-sequence(5) already says things like
>
> A message range is specified as âname1-name2â or âname:nâ, where
> `name', `name1' and `name2' are mes
On Mon, 03 May 2021 09:30:46 +0100, Ralph Corderoy said:
> +0845 Australia/Eucla
To quote Casey Schaufler:
EGADS - Concept violates the principle of Least Astonishment.
And here in North America, we tease Newfoundland for being
on the half-hour.
pgp55RpIHwHdW.pgp
Description: PGP signatu
Noticed I hadn't updated since Feb, did a git pull, things went poorly.
The gory details:
git bisect says:
[~/src/nmh] git bisect bad
c723593d2af190d9c86062d2a265fceec25fb777 is the first bad commit
commit c723593d2af190d9c86062d2a265fceec25fb777
Author: David Levine
Date: Sun Mar 21 09:31:21
On Mon, 10 May 2021 04:17:44 -0700, David Levine said:
> Valdis wrote:
>
> > which gives free() indigestion. I suspect Fedora is using a hardened
> > malloc()
> > that does more sanity checking and that's why it didn't get caught right
> > away.
>
> Or the tests don't cover a path starting with '
On Tue, 11 May 2021 17:58:21 -0700, David Levine said:
> Valdis wrote:
>
> > I originally put "patch in next mail" in the subject because the fix to not
> > use
> > a static char[] seemed obvious.
>
> I went the other way, so all the other callers of etcpath() wouldn't
> have to change:
That work
On Wed, 12 May 2021 18:16:28 +0200, Laura Creighton said:
> Oh goodness. I had no idea. And here I have been happily editing
> /etc/mailcap
> every time somebody sends me something I cannot read, adding a rule about how
> to
> read it, and smiling contentedly when nmh starts being able to read
On Wed, 12 May 2021 12:58:23 -0400, Ken Hornstein said:
> >> Oh goodness. I had no idea. And here I have been happily editing
> >> /etc/mailcap
> >> every time somebody sends me something I cannot read, adding a rule about
> >> how to
> >> read it, and smiling contentedly when nmh starts being
On Wed, 02 Jun 2021 00:13:51 -0400, Ken Hornstein said:
> So this bug was reported yesterday:
>
> https://savannah.nongnu.org/bugs/?60713
> I am wondering if the simplest solution is to put in isascii() in front
> of those tests in that function. We only really care about those tests
> retu
On Fri, 11 Jun 2021 14:04:36 -0400, Ken Hornstein said:
> character. This obviously works best if your local character set is
> UTF-8. I am aware that some people, for reasons I cannot comprehend,
> want to run in the "C" locale but PRETEND that their character set
> is UTF-8 and this approach d
On Sat, 12 Jun 2021 10:04:36 +0100, Ralph Corderoy said:
> What sorry excuse for an MUA are you using over there? :-)
That would be exmh.
> And why doesn't it complain at you when it spots the attempt to send
> these transgressions onto the wire?
That's a very good question - I *thought* I fix
On Sun, 13 Jun 2021 08:01:12 +0100, Ralph Corderoy said:
> What produces the draft when you repl(1) to Ken's, as is the faulty QP
> visible to you at the start of the edit?
It's displaying correctly inside exmh, but bad in the fcc: to outbox.
> > But linemode 'show' displays it correctly as well
On Sun, 13 Jun 2021 19:29:59 -0400, Ken Hornstein said:
> >> What produces the draft when you repl(1) to Ken's, as is the faulty QP
> >> visible to you at the start of the edit?
> >
> >It's displaying correctly inside exmh, but bad in the fcc: to outbox.
>
> Forgive me for calling you out ... but y
On Mon, 05 Jul 2021 12:22:55 -0700, n...@dad.org said:
> Second: I copied /home/norm/lib/Jar/chart.jar to /tmp/,chart.zip and attached
>
> This time whatNow accepted an 's'. But then I got the an error Email, which
> I am attaching to this message.
> Final-Recipient: rfc822; csfuh...@verizon.net
On Sun, 06 Feb 2022 09:26:14 -0800, David Levine said:
> Ok, commit 41ce4490ac5d might fix the problem for you. The cause
> was mismatch between the character set of content generated by the
> external program (lynx, in this case) and mhfixmsg -textcharset
> UTF-8. mhfixmsg wasn't capturing the
On Sun, 13 Mar 2022 21:37:12 +0100, "Thomas Dupond" said:
> If so, what should I use to have all the goodness of filtering and 'unseen'
> behaviour from nmh?
Procmail also knows how to deal with mh-style folders. You can either have it
deliver it directly (which doesn't update sequences), or inv
The good news is that I did a 'git pull' of nmh, 'make clean', './configure',
'make'.
Zero gcc warnings even with -Wall -Wetra, 'make check' reported all 118
tests passed, and nothing broken that I have noticed...
pgpeqmXn58Tso.pgp
Description: PGP signature
72 matches
Mail list logo
