Re: [Nmh-workers] Large MH directories

2017-04-08 Thread Ralph Corderoy
Hi Thomas, > some of these directories will have lots of files. > > Is this a bad idea? I'm mainly concerned about speed: Other than like > pick and scan on the whole folder, will anything else get very slow? Well, `scan .' will also read all entries in the folder's directory even though it knows

Re: [Nmh-workers] Changes to mh-tailor.man

2017-03-24 Thread Ralph Corderoy
Hi Ken, > Ralph, do you want to officially take over the job of committing > Larry's man page changes to the tree? Sure, OK. But it'll take me a couple of days to catch up with the backlog. I'll go through all the "Larry" emails and update README.manpages at the same time. -- Cheers, Ralph. h

Re: [Nmh-workers] Changes to mhmail.man

2017-03-24 Thread Ralph Corderoy
Hi Paul, > > I still don't know how to interpret "non-trivial". > > i'd say "content", vs. punctuation, formatting, or spelling. larry's > changes wouldn't qualify, IMO. In the latter bucket I'd also put removing removing double words, adding the odd word to improve grammar, swapping some words

Re: [Nmh-workers] Environment variables - with or without $?

2017-03-24 Thread Ralph Corderoy
Hi Valdis, > > No dollar. I have an environment variable called `$FOO'. > > Which shows up that way in 'printenv', and requires the use of $$FOO > to dereference? (Some quick testing with bash 4.4 seems to indicate > that it *really* doesn't want to see $ as the first character of a > variable na

Re: [Nmh-workers] Environment variables - with or without $?

2017-03-23 Thread Ralph Corderoy
Hi Larry, No dollar. I have an environment variable called `$FOO'. Agreed that `$HOME/foo' is OK because it's mixing environment variables and literal text using understood shell notation. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___

Re: [Nmh-workers] Changes to mh-tailor.man

2017-03-23 Thread Ralph Corderoy
Hi Larry, > - Don't escape hyphens unecessarily Is it worth recording some of the decisions, conventions, and common errors in the existing docs/README.manpages so there's less chance of regression over time by others? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy __

Re: [Nmh-workers] scan - Funky output with utf-8

2017-03-23 Thread Ralph Corderoy
Hi, > I can re-create the `-width 137' spew with git, but not with 1.6. > That suggests a bisect might help So git-bisect(1) blames commit e537b780f7aea8df01ddca1976f8c128d9c1fb55 Date: Fri Aug 29 08:50:51 2014 -0500 fmt_scan() no longer subtracts 1 from the width. This has t

Re: [Nmh-workers] zero'ed, zero'd or zeroed - take your pick

2017-03-22 Thread Ralph Corderoy
Hi Larry, > settle upon zero'ed, zero'd or zeroed, for the zeroing of sequences. > > (Personally, I favour the unadorned mundanity of zeroed.) +1 https://en.oxforddictionaries.com/definition/zero has zeroed. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy

Re: [Nmh-workers] Error in `comp': core dump when refile run at 'What now?' prompt

2017-03-22 Thread Ralph Corderoy
Hi Valdis, > Does 'git tags --contains (tag or commit id)' do what you want? Thanks, yes. It confirms the whatnow `ref +foo' core dump first shipped in 1.6. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Nmh-workers mailing list Nmh-wo

Re: [Nmh-workers] UNIX vs Unix in man pages - any appetite for change?

2017-03-22 Thread Ralph Corderoy
Hi Larry, > I have edits made here that will change UNIX to Unix in: ... > Before I commit and diff them, would they be welcome? Already a +1 from me, obviously. What do you mean by "commit"? Wondering if that means your patch submission could be simpler for you. -- Cheers, Ralph. https://plus.

Re: [Nmh-workers] Error in `comp': core dump when refile run at 'What now?' prompt

2017-03-22 Thread Ralph Corderoy
Hi, > Thanks, I've found the problem in git; will commit a fix later. Pushed commit. The "+foo" argument to ref was being appended to a *char[] to execvp(3). The rest of the array were malloc'd strings; that one wasn't. The array was freed later. Now copying those appended arguments too. Is

Re: [Nmh-workers] Error in `comp': core dump when refile run at 'What now?' prompt

2017-03-22 Thread Ralph Corderoy
Hi Tom, > In case you have not fixed this already, after my sig is example of > core dump that happens when I run 'refile' at the 'What now?' prompt. > Despite the dump the refile works OK. Thanks, I've found the problem in git; will commit a fix later. Telling the list now to avoid duplication

Re: [Nmh-workers] scan - Funky output with utf-8

2017-03-21 Thread Ralph Corderoy
Hi Valdis, > Ralph wasn't able to replicate it with a 7-byte string With your provided email and format file I can re-create the `-width 137' spew with git, but not with 1.6. That suggests a bisect might help; I may have time tomorrow. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy

Re: [Nmh-workers] mhshow in background

2017-03-21 Thread Ralph Corderoy
Hi Jon, > No problem stopping evince after the mhshow. The problem is running > it in the background so that I can look at the pdf and do other stuff > at the same time. When I do a control-Z followed by a bg the mhshow > job and it's children stay stopped. Oh, I get that here with mupdf. It's

Re: [Nmh-workers] Starting 1.7 release cycle

2017-03-21 Thread Ralph Corderoy
Hi Jon, > > What's the route between mhshow and evince, e.g. xdg-open(1)? > > What's the relevant mhshow-... lines in the profile? ... > The relevant profile line is "mhshow-show-application/pdf: evince > '%F'". That's a direct chain of processes between mhshow and evince. You might want to try

Re: [Nmh-workers] Changes to mh-draft.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, > > > directly, they supply > > > .B send > > > -with the UNIX pathname of the message draft, and > > > -.B not > > > -a > > > +with the UNIX pathname of the message draft; NOT a > > > .B \-draftmessage > > > .I msg > > > argument. As far as > > > > Must we shout for emphasis? :-)

Re: [Nmh-workers] Changes to mh-draft.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, > directly, they supply > .B send > -with the UNIX pathname of the message draft, and > -.B not > -a > +with the UNIX pathname of the message draft; NOT a > .B \-draftmessage > .I msg > argument. As far as Must we shout for emphasis? :-) -- Cheers, Ralph. https://plus.google.co

Re: [Nmh-workers] Starting 1.7 release cycle

2017-03-21 Thread Ralph Corderoy
Hi Jon, > I just had this problem today when displayin a pdf attachment via > evince. What's the route between mhshow and evince, e.g. xdg-open(1)? What's the relevant mhshow-... lines in the profile? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy

Re: [Nmh-workers] Starting 1.7 release cycle

2017-03-21 Thread Ralph Corderoy
Hi Ken, > bug tracking database (I know Ralph put some stuff in there recently) That was just to stop faults discussed on the mailing list from being forgotten when no one has time to address them promptly. 1.7 arriving is good news. If it's not already the case, perhaps some notes could be tak

Re: [Nmh-workers] Update .SH NAME for fmttest.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, > > That looks wrong, not due to your change. The line after .SH should > > be a single physical line with a `\-'. > > I had spotted that, but being rather monofocal I pressed on with the > job at hand. That's fine. I was more pointing it out to the list as a thing to fix/not repeat.

Re: [Nmh-workers] Changes to new.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, .«-B-»«+BR+» new «+,+» in its default mode«+,+» produces a one«-\-»-line«-\-»-per«-\-»-folder listing of all folders «-containing-» «+which contain+» messages in the «-listed-» «+specified+» .IR sequences «+,+» or in the «-sequences-» «+sequence(s)+» listed

Re: [Nmh-workers] scan - Funky output with utf-8

2017-03-21 Thread Ralph Corderoy
Hi Valdis, > %body in a scan format goes pear-shaped if -width splits a UTF character. May we please have the output of scan -version locale > (Attaching a .png, cut-n-paste didn't quite get things right) A simple test here doesn't show the fault. $ scan -version scan -- nmh-1

Re: [Nmh-workers] Update .SH NAME for refile.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, > .SH NAME > -refile \- file message in other folders > +refile \- file message in other nmh folders Various commands work on one or more messages, etc. Some say singular `message' when they'll work on multiple, like refile(1) above. Some say `sequence(s)', which just seems over jarr

Re: [Nmh-workers] Updated diff for inc.man including .SH NAME

2017-03-21 Thread Ralph Corderoy
Hi Larry, > .SH NAME > -inc \- incorporate new mail > +inc \- incorporate new mail to an nmh folder `into'? The page uses `into' later on. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Nmh-workers mailing list Nmh-workers@nongnu.org

Re: [Nmh-workers] Update .SH NAME for fmttest.man

2017-03-21 Thread Ralph Corderoy
Hi Larry, > .SH FMTTEST > -fmttest \- test tool for the > +fmttest \- test tool for the nmh > .IR mh-format (5) > language > .SH SYNOPSIS That looks wrong, not due to your change. The line after .SH should be a single physical line with a `\-'. `man -k fmttest' gives nothing here, though `m

Re: [Nmh-workers] (possibly) Improving .SH NAME to improve apropos output

2017-03-20 Thread Ralph Corderoy
Hi Larry, > ali \- list *nmh* mail aliases > anno \- annotate *nmh* messages > comp \- compose an *nmh* message > mark \- manipulate *nmh* message sequences > > Is this just silly, or shall I proceed? +1, ignoring those where it's too awkward to shoehorn nmh in. -- Cheers, Ralph. https://plus.g

Re: [Nmh-workers] A suggestion for mh-alias.man

2017-03-20 Thread Ralph Corderoy
Hi Larry, > (I have no idea to what "In match, a trailing "*" on an alias will > match just about anything appropriate." applies. I actually don't know > what it means, either.) I've not used it before. $ printf 'foo*: bar\n' | ali -alias /dev/stdin -list foo*: bar $ printf 'foo*: ba

Re: [Nmh-workers] changes to mark.man

2017-03-20 Thread Ralph Corderoy
Hi kre, > > #! /usr/local/bin/dash > > ??? Why not /bin/sh I copied the original, but /bin/sh is bash on some systems so I guess this is to ensure something speedier, and that no bashisms are present. > > test $# -eq 0 && set cur > > You don't need that, repl will reply to cur if there a

Re: [Nmh-workers] changes to mark.man

2017-03-20 Thread Ralph Corderoy
Hi Larry, > #!/usr/local/bin/dash > > repl=/usr/local/bin/repl > repll="/usr/local/bin/repl -group" > > case $(folder -fast) in > lists|obsd|nmh) list=1 ;; > *) : ;; > esac > > if [ $# -eq 0 ] ; then > scan cur > /dev/null 2>&1 > err=$? > case "$err" in > 0) cur=

Re: [Nmh-workers] changes to mark.man

2017-03-19 Thread Ralph Corderoy
Hi Larry, > There appears to be three options - "name:n", "name:+n", or "name:-n", > yet they refer to the 'first or last `n' messages', respectively, i.e. > there are two respective explanations for three options It's `name:n' where n is a non-zero integer. If positive then it's the first n mes

Re: [Nmh-workers] protection vs mode in man pages

2017-03-19 Thread Ralph Corderoy
Hi Larry, > Only inc.man and rcvstore.man use the 'protection' construct. It's not a common Unix phrase in this context. > Thoughts? How about putting the simple default first? Refer to chmod. I guess the "filesystems" qualifier needs to remain. Is there any profile other than the user's? `nnn'

Re: [Nmh-workers] maildrop vs mail drop in man pages

2017-03-19 Thread Ralph Corderoy
Hi Larry, > Can I get a ruling, please, on the use of 'maildrop' vs 'mail drop' in > the man pages? > > A quick search shows 25 current instances of 'maildrop' (not counting > $MAILDROP), as against 19 for 'mail drop'. Google's Ngram's viewer clearly favours "mail drop". https://books.google.com/

Re: [Nmh-workers] mhshow -file /tmp (!)

2017-03-18 Thread Ralph Corderoy
I wrote: > I suspect Paul has a similar filesystem arrangement for /tmp to me. That's back to front. He must have a /tmp that returns a number big enough to truncate negative. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Nmh-workers m

Re: [Nmh-workers] mhshow -file /tmp (!)

2017-03-18 Thread Ralph Corderoy
Hi Ken, David's committed a directory test now, but I still think the underlying cause is interesting, and some mess remains. > mhshow calls parse_mime() > parse_mime() calls get_content() > get_content() decides it's a message with a single text/plain part > (default) > Then the MIME display rou

Re: [Nmh-workers] Changes to forw.man

2017-03-17 Thread Ralph Corderoy
Hi, > > I can see why the `(5)' is dropped on the second reference, so soon > > after the first, but why does it become bold instead of italic? For completeness, Larry replied, accidentally off list, to say that was just a simple mistake. And I agree with kre's comment on the `contains' v. `is'.

Re: [Nmh-workers] Changes to forw.man

2017-03-17 Thread Ralph Corderoy
Hi Larry, > Forms are processed via the > .B nmh > template system; see > .IR mh\-format (5) > for details. Components from the first forwarded message are available > as standard component escapes in the forms file. > .PP > In addition to the standard > -.IR mh\-format (5) > +.B mh\-form

Re: [Nmh-workers] Sequences in scan

2017-03-09 Thread Ralph Corderoy
Hi Johan, > Is there anyway to check if a message is in a specific sequence for > the scan output. I can check `unseen` and `cur`, would be nice if I > could do something like this in my scan format file: > > %<(seq{my-seq}) ! %| %> No, that I know of. I was thinking an environment variabl

Re: [Nmh-workers] nmh's Temporary Directory: ~/mail.

2017-03-06 Thread Ralph Corderoy
Hi David, > Not off hand. It looks like $MHTMPDIR was introduced between MH 6.8.5 > and the entry of nmh into CVS. MH 6.8.5 hard-coded the use of /tmp/. 6.8.5 was right; /tmp can be hardcoded. > The thread beginning at > https://lists.gnu.org/archive/html/nmh-workers/2014-01/msg00043.html > h

[Nmh-workers] nmh's Temporary Directory: ~/mail.

2017-03-04 Thread Ralph Corderoy
Hi, Just noticed my backups having a lot of temporary files matching mhshow??, mhfixmsg??, etc., in ~/mail. This is because m_mktemp() uses the first of $MHTMPDIR, $TMPDIR, ~/mail and I haven't bothered setting $TMPDIR because I'm happy with the rest of the world's default of /tmp. Anyon

[Nmh-workers] htmail-view and t-prot.

2017-03-02 Thread Ralph Corderoy
Hi, A couple of programs I came across recently that might be useful to nmh users, but I haven't had the chance to try them out. I thought I should still pass them on rather than sit on them forever. https://github.com/liske/htmail-view#readme Web page renderer based on WebKit. In contr

Re: [Nmh-workers] specifying SMTP server in mts.conf broken by TLS certificate changes

2017-02-20 Thread Ralph Corderoy
Hi Ken, > we have to decide how to parse that, assuming that you just want to > add something to the server hostname. As I've learned recently you > can't use a colon as a separator because that's a valid character in > an IPv6 address. The rule for URLs is to enclose the IPv6 address in bracket

Re: [Nmh-workers] Determining my draft folder

2017-02-18 Thread Ralph Corderoy
Hi, I wrote: > EXIT STATUS > mhparam returns the number of components that were not found. ... > $ mhparam `yes | sed 256q`; echo $? > 0 I've just pushed to git. http://git.savannah.nongnu.org/cgit/nmh.git/commit/?id=e8eb3afba50cbec8d1aeabcf85a06084977d54cd Limit mhpa

Re: [Nmh-workers] Determining my draft folder

2017-02-17 Thread Ralph Corderoy
Hi Ken, > % mhparam draft-folder > Does exactly that. And exits 1 if that isn't set. > > By the way, it would be nice if man mhparam listed the parameters it > > took. > > I think it does? It sure looks like it does when I run "man mhparam". > Or do you mean something else? Perhaps Norm means

Re: [Nmh-workers] specifying SMTP server in mts.conf broken by TLS certificate changes

2017-02-17 Thread Ralph Corderoy
Hi Ken, > other MUAs I'm familiar with only permit one server to be configured > and redundancy is handled via DNS. So the code is written to loop over all the addresses returned for the one DNS entry? Cheers, Ralph. ___ Nmh-workers mailing list Nmh-w

Re: [Nmh-workers] show MSG_SEQ_NAME ; : MessageName not shown, unless "-nocheckmime" added.

2017-02-08 Thread Ralph Corderoy
Hi Tom, > > $ folder;command show automount | egrep -i '^(messagename|X-Envelope-From)' > > |head -4 > > ipa+ has 4706 messages (1-4706); cur=4706; (others). > > X-Envelope-From: freeipa-users-boun...@redhat.com Fri Apr 29 16:01:46 2016 > > X-Envelope-From: freeipa-users-boun...@redhat.com Mon

Re: [Nmh-workers] show 1 3 5; : shows msg num ok; show MSG_SEQ_NAME ; : messagename not shown

2017-02-07 Thread Ralph Corderoy
Hi Tom, > > What behaviour do you get with this script run in an empty > > directory? > > Works OK: Hmm. You might want to try editing that script to use more of your normal set up until it fails again. It looks very similar to your command-line tests to me, other than unsetting PAGER. -- Che

Re: [Nmh-workers] show 1 3 5; : shows msg num ok; show MSG_SEQ_NAME ; : messagename not shown

2017-02-05 Thread Ralph Corderoy
Hi Tom, What behaviour do you get with this script run in an empty directory? $ cat try #! /bin/bash PATH=/usr/bin:/usr/bin/mh unset PAGER export MH=$PWD/mh echo path: $PWD >$MH printf '%s:\n' subject messagename >mhl.format mkdir -p inbox for f in 1 2; do

Re: [Nmh-workers] help me out with mime/base64/gpg please

2017-02-03 Thread Ralph Corderoy
Hi Ken, > normally for encrypted email you'd need to enter in your password to > unlock your private key and we don't really have a good mechanism for > that currently. There's a gpg-agent(1); it's kicked off as needed by gpg(1) these days AIUI. I've not used it, but I assume it works similarly

Re: [Nmh-workers] OT: Content-Type boundary Matching /^_av-/.

2017-02-03 Thread Ralph Corderoy
Hi Laura, > I have piles and piles of legitimate mail from Patreon that use this > boundary marker. Want me to send you some? Yes please, off list. If there's not enough of a clue in the rest of the headers, I can see if https://www.patreon.com/ can point to the source. Cheers, Ralph. ___

[Nmh-workers] OT: Content-Type boundary Matching /^_av-/.

2017-02-03 Thread Ralph Corderoy
Hi, I've noticed an increase in spam I get over the last couple of months. I normally get quite a bit, but it shot up for a good few weeks and has only recently come back down as, presumably, the bullet found its home. But what struck me as odd is the vast bulk of the spam received has a MIME boun

Re: [Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-19 Thread Ralph Corderoy
Hi Paul, > so it sounds pretty clearly like a bug which should be fixed. I opened https://savannah.nongnu.org/bugs/?50066 so I don't forget about it when I've more time. I've been doing that recently for things discussed on the mailing list, giving a link to the archive, so there's a bit of an i

Re: [Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-19 Thread Ralph Corderoy
Hi David, > I wonder if it was a reluctance to add another chdir. I would be. Me too. That's why I asked Jon if he remembered the reason. :-) > Without some careful investigation into all of the other chdir's, > I wouldn't be surprised if they could stomp on each other. Yep. Though that als

Re: [Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-18 Thread Ralph Corderoy
Hi Jon, > I do think that your example above is sort of bogus; whatnow does not > provide full shell functionality so you can't do things like that > anyway. It's not bogus as it happened to me in normal use, that's how I found the problem. whatnow isn't a full shell, but that doesn't matter. Ne

Re: [Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-18 Thread Ralph Corderoy
Hi David, > > $ comp -ed false > > whatnow: problems with edit--draft left in /home/ralph/mail/drafts/,42 > > I see your point but don't feel strongly about it. It looks like it > was intentional, and has been that way for nearly 27 years (though the > error message changed along the way)

Re: [Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-18 Thread Ralph Corderoy
Hi Jon, > David wrote: > > > It's very unintuitive, well, wrong, that a `cd' command at a > > > command's prompt doesn't change the current working directory as > > > far as all other commands are concerned. That's not how other > > > Unix commands that provide cd work. If it can't be fixed then

[Nmh-workers] whatnow(1)'s cd Doesn't Affect it's mime.

2017-01-17 Thread Ralph Corderoy
Hi, I tend not to use whatnow(1)'s new `attach', etc., preferring to specify more precisely a content-description, etc., as an mhbuild directive and asking whatnow to `mime'. Today, I started comp a directory too high. $ mkdir foo $ date >foo/bar $ comp -ed ed 227 /^MIME/;+2d

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-11 Thread Ralph Corderoy
Hi Ken, > From exmh's perspective, I suppose it would be easy to disable the > Content-ID caching. Or spot the duplicate and refuse to have anything more to do with the transgressor! :-) I heard yesterday from another producer of Quoted-Printable multipart/mixed that they were fixing their invo

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-09 Thread Ralph Corderoy
Hi Christer, > Personally, I filter out Content-ID in the mail header, and leave it > in Mime-part headers. Content-ID in the mail header breaks my exmh in > certain cases That's a shame. I tried poking around the exmh community a bit just now, but the Red Hat-hosted mailing lists have private a

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-09 Thread Ralph Corderoy
Hi Ken, > I was curious about pine, so I looked at that. It does generate them, > but you can turn that off. The comments are: > > * If requested, strip Content-ID headers that don't look like they > * are needed. Microsoft's Outlook XP has a bug that causes it to > * not show tha

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-08 Thread Ralph Corderoy
Hi David, > > > I'm not sure you can, in practice, guarantee that they are > > > globally unique. > > > > Ditto Message-ID? > > Right, nmh doesn't have a way to generate a globally unique message or > content ID. OK, but I think Ken was pointing out duff Content-IDs are seen in practice, I've rec

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-08 Thread Ralph Corderoy
Hi Ken, > I'm not sure you can, in practice, guarantee that they are globally > unique. Ditto Message-ID? > it occurs to me that if you really care what the content-id is (like > you're sending some HTML email that refers to images in the email) you > want to choose your Content-ID before the me

Re: [Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-07 Thread Ralph Corderoy
Hi Ken, > You know, this begs the question ... should we even bother to add a > Content-ID header by default? I am aware of their usefulness for > text/html parts and the cid: URL, but that's not really useful unless > you know what the Content-ID is going to be and right now you don't > really k

[Nmh-workers] Domain Leakage Despite -messageid random.

2017-01-06 Thread Ralph Corderoy
Hi, I've been experimenting with send(1)'s `-msgid -messageid random' invocation. If nmh is left to add the MIME headers, the default, then Content-IDs get whacked in that look an awful lot like a `-messageid localname', the default. Should -messageid random affect Content-ID too? Are there any

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-04 Thread Ralph Corderoy
Hi Paul, > the error it signals up-stack must tell its caller why it fails, so > that its caller can then try the next possible filename (message > number). only if it fails N times in a row (suggest 6 or 42, from the > prisoner and douglas adams) should comp then fail. That's a nice to have need

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-03 Thread Ralph Corderoy
Hi Ken, > - The file is created with creat(), which as you know does get called > with O_CREAT, but does not include O_EXCL. Could that be considered a bug? That's comp(1). I UTSL this time and repl(1) appears to fopen(..., "w") so it's no better off. > Really, the safest thing to do for Laura

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-03 Thread Ralph Corderoy
Hi Ken, > > never both plump for 42. > > Are you sure about that? I am pretty sure from looking at the code > that can absolutely happen. I didn't look at the code. :-) I just thought that surely 42 is open(2)'d with O_CREAT|O_EXCL so Unix annoints the race's winner. -- Cheers, Ralph. https:

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-03 Thread Ralph Corderoy
Hi Laura, > I had forgotten all about the automated script (not only that it > existed, but that it was running on the machine where I don't usually > read my mail, but was using at the time). Does that mean your nmh mail directory is on some network-shared filesystem? -- Cheers, Ralph. https:/

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-03 Thread Ralph Corderoy
Hi Ken, > I suspect what happened is that your digest bursting program overwrite > your draft file between "repl" and "send", and your "send" sucessfully > sent the digest. I agree that seems to match the symptoms... > it's generally not safe to run two nmh programs simultaneously (we do > some

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, Ken wrote: > It would be interesting to make sure that in your drafts folder there > exist a bunch of old messages with backup prefix. And that they linger, undisturbed. You could even deliberately create one with a high number that's unlikely to be used in practice to see it remains,

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, Another thought. You mention Emacs. Do you use the MH-E package or similar? Any other non-nhm MH programs? Could they be interfering with what we know of the normal flow? Is there any background job, perhaps relating to backups or disk cleaning, that would purge ,42? -- Cheers, Ra

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, > Alas. I was hoping that a smarter send could understand that the > hassle involved in removing an unwanted draft is minor, and so > cautiuously bump the draft number for subsequent messages so that > there was no chance of reusing the draft number if it ever detected a > problem That

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, > But my real query is about this 'apparently successful send'. Why > wasn't it apparent that the send wasn't successful? Shouldn't a check > of return codes have discovered the problem? What happens to successfully sent emails? Passed to a local MTA? A remote one? Does that leave

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, > emacs. > > > What does `mhparam draft-folder' give? > > drafts (which seems to be working just fine -- drafts are indeed being > created here) So emacs will have been editing drafts/42, say. > > Did repl die after you quit the editor and before the whatnow(1) > > prompt? > > Definite

Re: [Nmh-workers] nmh should be more careful about when it unlinks draft files

2017-01-02 Thread Ralph Corderoy
Hi Laura, > /usr/bin/mh/repl -group -format ... > I was replying to somebody and got: > *** Error in `/usr/bin/mh/repl': free(): invalid pointer: 0x08080547 *** > /u/lac/bin/ra: line 2: 5931 Aborted/usr/bin/mh/repl -group -format I get similar looking malloc corruptions with nmh 1.6-3 on Arc

Re: [Nmh-workers] Changes to rcvdist.man

2016-12-30 Thread Ralph Corderoy
Hi Larry, > +You may specify an alternate forms file with the > .B \-form > -.IR formfile . > +.IR formfile > +switch. It was You may specify an alternate forms file with the switch -form formfile. It's become the `> ' quoted above, You may specify an alternate forms file with the

Re: [Nmh-workers] .BR and .IR for program names in man pages

2016-12-23 Thread Ralph Corderoy
Hi Larry, > when referring to another program, as in > .BR dist , > or > .IR mh-draft (5) David's answered, but I'd also point out that mh-draft(5) is a file rather than a program. Another thing is if it's a case-sensitive concept, e.g. the program name inc, then it doesn't suffer no

Re: [Nmh-workers] Changes to flist.man

2016-12-18 Thread Ralph Corderoy
Hi Larry, > I'm afraid I don't follow you. Can you walk me through this, please? When a program is run it is given an "argument vector", a list of strings given when it was execve(2)'d. The first of these is conventionally taken as the name of the program. It doesn't have to match the name of t

Re: [Nmh-workers] mhfixmsg issue with ill-formed mail.

2016-11-19 Thread Ralph Corderoy
Hi Valdis, > 040 t a n n o u n c e d h e b \0 >20746e616f6e6e756563206465680062 > 060 031 s n o m i n a t i n g S e >73196e206d6f6e6974616e692067

Re: [Nmh-workers] I can't dist to myself

2016-11-16 Thread Ralph Corderoy
I wrote: > IIRC Mutt has a "bounce" command that does a dist; perhaps it already > handles the introduction of Delivered-To. 3.22. bounce_delivered Type: boolean Default: yes When this variable is set, mutt will include Delivered-To headers when bouncing messages. Postfix u

Re: [Nmh-workers] I can't dist to myself

2016-11-16 Thread Ralph Corderoy
Hi Norm, > Yes, that works. Though changing the original Email, violates the > spirt of dist. I agree. Delivered-To isn't covered by an RFC AFAIK. It's added by the MTA when it hits it "final" resting place. I'll report back Postfix's explanation/advice as to what an MUA should be doing. IIRC

Re: [Nmh-workers] I can't dist to myself

2016-11-16 Thread Ralph Corderoy
Hi Norm, > (expanded from ): mail > forwarding loop for n...@localhost.dad.org I get this error from Postfix on dist(1)ing to myself and have done for quite some time. It's because the email has a Delivered-To header with my address. Postfix spots that when dist hands it over a second time, th

[Nmh-workers] Why Does mh-tailor(5) Exist?

2016-11-14 Thread Ralph Corderoy
Hi, mh-tailor(5) documents /etc/nmh/mts.conf. As does mts.conf(5) that is just a .so to source the mh-tailor. Can mh-tailor get the chop if the references get switched over too? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Nmh-worker

Re: [Nmh-workers] Help: dist is not working for me

2016-11-14 Thread Ralph Corderoy
Hi Norm, > Why did I ignore your advice? I don't remember. But I would conjecture > that it was some combination of not understanding the advice, not > understanding its context, or not believing that its context was > relevant to me. If it's like me with most of the "do this for the new version"

Re: [Nmh-workers] Help: dist is not working for me

2016-11-11 Thread Ralph Corderoy
Hi Norm, > I don't have a distcomps in my nmh directory (~/Mail). So I'm getting > the default. Should I have a ~/Mail/distcomps ? If so what should it > be. As Ken implied in replying to me, Local-Mailbox in mh_profile(5) is another option. -- Cheers, Ralph. https://plus.google.com/+RalphCorde

Re: [Nmh-workers] Help: dist is not working for me

2016-11-11 Thread Ralph Corderoy
Hi Norm, Ken wrote: > But I am wondering if perhaps the problem is this: > > >=> MAIL FROM: I suspect it is. dist(1) gets this "wrong" for me here, too. $ fmttest -raw -forma '%(localmbox)' '' Ralph Corderoy $ -- Cheers,

Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6

2016-11-07 Thread Ralph Corderoy
Hi Tom, > Although now that I see David's mail, I think maybe it did have > -nodirectives active but the backslash removal happened anyway. -auto implies -nodirectives so perhaps that increases the odds it was in force. Cheers, Ralph. ___ Nmh-workers

Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6

2016-11-07 Thread Ralph Corderoy
Hi Tom, > In a different line of thinking: if mhbuild did take #define as a > directive, why didn't it barf on an unrecognized directive? What version of nmh is this that doesn't barf in the night? Cheers, Ralph. ___ Nmh-workers mailing list Nmh-worke

Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6

2016-11-07 Thread Ralph Corderoy
Hi David, > I committed a fix to disable erasing a trailing backslash-newline with > mhbuild -nodirectives. Has my fledgling git-fu failed me, or is test/mhbuild/test-mhbuild missing? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___ Nmh-w

Re: [Nmh-workers] Unexpected munging of outgoing message with nmh 1.6

2016-11-07 Thread Ralph Corderoy
Hi Ken, > You know, just out loud ... it wouldn't surprise me if it only happens > with lines that start with "#"; I bet even though directives are > turned off, it's seeing a backslash as the directive line continuation > character. Indeedy. But presumably Tom is running with -nodirectives or u

Re: [Nmh-workers] 1.7 release date

2016-10-30 Thread Ralph Corderoy
Hi David, > Not 100%, so your point is well taken, but higher than I expected. It occurs to me that it may be quicker to write tests that aim to increase coverage rather than test actual output against expected, etc. That would then give valgrind more to chew on. They could then be fleshed out s

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-29 Thread Ralph Corderoy
Hi Paul, > > What if benign truncations were trunccpy(), instead of the strncpy > > dance where the reader is unsure if it's benign or not > > as long as every trunccpy() result is checked, so that if truncation > does occur there is a different code path following the call They don't need to be

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-29 Thread Ralph Corderoy
Hi Ken, > > If this is what I think it is ... you know, I think this truncation > > is benign. What if benign truncations were trunccpy(), instead of the strncpy dance where the reader is unsure if it's benign or not, and then abortcpy() could be the strncpy() replacement that aborts on truncatio

Re: [Nmh-workers] 1.7 release date

2016-10-29 Thread Ralph Corderoy
Hi Lyndon, > This is code rewrite for religious purposes Here's a rewrite example. -size_t len = sizeof "user=" - 1 -+ strlen(user) -+ sizeof "\1auth=Bearer " - 1 -+ strlen(cred->access_token) -+ sizeof "\1\1" - 1; -free(cred->ctx->

Re: [Nmh-workers] Having configure Check for cc's -pedantic -ansi.

2016-10-29 Thread Ralph Corderoy
Hi David, > > An `rm *' in a clean-up is finding a directory has been produced!? > > Can you tell from config.log? Odd that it would do that on some > platforms and not others. But this is Mac OS X! For the "checking whether $CC understands -c and -o together" in configure it does rm -f co

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-29 Thread Ralph Corderoy
Hi Ken, > >strncpy(sm_reply.text, str, sizeof(sm_reply.text)); > >sm_reply.text[sizeof(sm_reply.text) - 1] = '\0'; > > If this is what I think it is ... you know, I think this truncation is > benign. Could be. I just picked one at random to show a typical call-site pattern. -- Cheers,

Re: [Nmh-workers] Having configure Check for cc's -pedantic -ansi.

2016-10-29 Thread Ralph Corderoy
Hi David, > > Cyrus SASL support [determined by configure]: > > TLS support [determined by configure]: ... > > The last two could do with something indicating what the answers can > > be if the default isn't wanted. > > build_nmh doesn't know without running configure, and I don't think

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-29 Thread Ralph Corderoy
Hi Paul, > > Perhaps a complainant could be told of the secret $NMHNOBARF to stop > > TRUNCCPY from aborting? Though it would still complain for the > > first N goes? > > replacing overrun with truncation is not a big enough improvement to > justify touching the code at all. I'm targetting the e

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-29 Thread Ralph Corderoy
Hi Steffen, > Therefore i think a function like the Linux strscpy() That was a new one to me. I found it, https://manned.org/strscpy.9 It's defined in the Linux kernel. ssize_t strscpy(char * dest, const char * src, size_t count); Does nothing if count is zero. Otherwise, it's dest's size

Re: [Nmh-workers] Having configure Check for cc's -pedantic -ansi.

2016-10-29 Thread Ralph Corderoy
Hi David, > I just committed a change to do this: > > By default (with_tls=''), enable TLS if header and libs were > found. > If TLS requested (--with-tls with_tls=yes), error if header/lib > not found. > If TLS disabled (--without-tls with_tls=no), don't enable it. Re

Re: [Nmh-workers] strncpy(3), die, die, die.

2016-10-24 Thread Ralph Corderoy
Hi Ken, > Although ... crud, I take your point that a small change is a lot > easier than a big change. Yes, as soon as a free() is needed then there's tracking the paths that exit the function, where the pointer gets copied to, etc. GC anyone? :-) > My concern there is our release cycles have

<    4   5   6   7   8   9   10   11   12   13   >