Re: [Nmh-workers] Sequences in scan

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

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

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 >

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

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.

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

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

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

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

Re: [Nmh-workers] Determining my draft folder

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

Re: [Nmh-workers] Determining my draft folder

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

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

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

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

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

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. --

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

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

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

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

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-/.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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.

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

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

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

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,

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

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

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

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

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? > >

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

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

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

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

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

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

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

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 >73196e206d6f6e6974616e69

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

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

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

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.

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

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

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

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 ___

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

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

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

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.

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

Hi Norm, Ken wrote: > But I am wondering if perhaps the problem is this: > > >=> MAIL FROM:<n...@nad.dad.org> I suspect it is. dist(1) gets this "wrong" for me here, too. $ fmttest -raw -forma '%(localmbox)' '' Ralph Corderoy <ra...@orac.inputplus.co.u

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

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

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

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

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 ___

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

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

Re: [Nmh-workers] 1.7 release date

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

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

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.

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

Re: [Nmh-workers] 1.7 release date

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; -

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

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

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

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.

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.

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

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

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

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

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: [Nmh-workers] strncpy(3), die, die, die.

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

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

Hi David, I hope this strncpy thread doesn't run on for ever and anon. It's delaying my brace-style email. > > I dunno, I think we'd need to think carefully if a particular use of > > strncpy() really warrants an abort vs a truncate. I mean, just > > crapping out on a really long line that

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

Hi Todd, > Paul Vixie wrote: > > Copy or die, as the default behavior. malloc! Or death! > Both snprintf() and strlcpy() make it fairly easy to detect whe the > buffer was too small, which is more than I can say for strncpy(). It > is up to the programmer to actually check the return value.

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

Hi Ken, > You know, somehow I had missed all of these years that strncpy() pads > out the rest of the buffer, which is certainly not ideal! Yes, I keep forgetting it and rediscovering. :-) > I can only say that on my Linux systems, I don't have strlcpy() or > -lbsd. Here it's provided by

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

Hi David, > Worked well on a machine where I hadn't built it before, but was > likely to have some of the optional development packages installed. The second time `sh build_nmh' is run the `git clone' fails because ./nmh exists and isn't empty. The user doesn't know that immediately though

Re: [Nmh-workers] Minor gripe about send man page

Hi Ken, > But to answer [Norm's] question ... the division of labor is kind of > like the division between show(1) and mhl(1); send(1) takes a message > and maybe does some minor processing on it (or splits it up), and then > passes the file off to post(8) to actually send it (post takes a >

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

Hi, David spotted some compile warnings that I didn't. I've since overridden configure's CFLAGS to add `-pedantic -ansi', but I wonder if m4/cppflags.m4 should attempt these and add them if they work? The risk is someone has a compiler that spots problems all of ours missed. That's probably

Re: [Nmh-workers] When a message goes only to me, as a cc

Hi Norm, > > It looks like it's always the first argument now; seems easy enough > > to keep that the way it is. > > Those two guarantees would make it easier to write a postproc that > would be robust against changes in post and the way it's called. So post(1) needs it -whom documenting to make

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi Tom, Twas you I saw mentioned. :-) http://git.savannah.gnu.org/cgit/nmh.git/commit/?id=82f1f1db8de7b833068a3ef0dc7d10759bb94941 That's just been updated to not be generated and use the single identity array I mentioned. It means a function call instead of probably a macro, but it

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi Tom, > I've never heard of an implementation not using -1, though. Me neither, and that's what the code's depending on thus the #error otherwise. (Would be quite interesting to find such a platform. :-) > > extern int ctype_identity[257]; /* [n] = n-1 */ > > #define isupper(c)

Re: [Nmh-workers] Development Questions. check Programs. register.

Sorry, me again. > Instead, each look-up table can be a private array with a pointer to > its second element, and index that. Sound OK? Thinking about this a bit more. The "generate C at compile time" can be dropped by #ifndef NDEBUG #if EOF != -1 #error "Please report this to

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi, I wrote: > Back to ctype.h, can we now assume POSIX ISTM that the sbr/ctype-checked.h versions assume, wrongly, that isdigit(EOF) and tolower(EOF) aren't valid, for example, and will index an array with -1. We can't increment all the indexes by one as that will promote a char to int before

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi Ken, > > and then a check or distcheck shows up problems from earlier edits. > > I kind of thought for efficiency's sake we shouldn't build things that > we don't need. It just seems wasteful to me build all of the test > suite programs when they're not used; I guess the thinking there is >

Re: [Nmh-workers] Hanging test test/install-mh/test-version-check

Hi Ken, > - The real problem isn't the tight loop for script(1); it's that when > this version of script gets an EOF on the "user" side (because the > input is set to /dev/null) I'm not sure why script(1) is run in the background and then immediately wait'd for; is it to just get

Re: [Nmh-workers] Hanging test test/install-mh/test-version-check

Hi, Ken wrote: > I noticed that test/install-mh/test-version-check is hanging for me on > MacOS X. Specifically, the "script" command on MacOS X seems to be > the problem; for reasons I don't understand quite yet when "script" is > run the input is set to /dev/null I've found a Mac Mini I can

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Tom, > All of these solutions presuppose that this is my problem and not the > software's. I respectfully disagree. Me too. :-) There's a mechanism for telling a hierarchy of programs their locale; environment variables. You're using it, but you're telling some of them a different locale

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Tom, If you just have one long-running Emacs then can't that be in the UTF-8 locale? Or is your C-needing ls(1) run from inside that? Have Emacs highlight non-ASCII characters in that mode wherever they come from, e.g. paste from web browser? Have a function that maps the common ones to

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi, Ken wrote: > And if we're voting ... I would rather have only one additional way to > specify a nmh-specific locale (well, I'd rather have ZERO additional > ways, but I think more than one way is overkill). I'd rather have zero. :-) Anything above that surely warrants an nmhlocale(1). >

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Ken, > > Valid UTF-8 and valid GB2312 can share the same sequences, > > especially if it's just the odd `£' or `拢` in ASCII text. > > It was just a suggestion, not one I was particularly crazy about ... > but not all arbitrary 8-bit sequences are valid UTF-8. Oh, agreed. > And it looks like

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi Ken, > Personally, I like it in the main repo, but I don't feel strongly > about it either. Maybe we could put it on a branch, with everything > else trimmed out of the repo? That way if anything else "historic" > showed up we could add it to the branch. Whatever would be most useful for

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Laura, > Just giving them utf-8 even though that wasn't what they asked for has > fixed a huge number of headaches when running mailing lists around > here. Does that mailing-list software check that what they're sending out is valid for the encoding they claim, UTF-8? Or when replying to an

Re: [Nmh-workers] Development Questions. check Programs. register.

Hi David, > > I've noticed things like test/fakepop only get built on a `make > > check' because that needs to use them. OTOH, it would be nice to > > see compilation succeeds along with everything else in the `all' > > target. > > Maybe add a phony target that would build the test programs?

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Tom, > But I don't really agree with the tradeoff that's been made of failing > when you can't be sure of that. I don't think nmh should be complicit to you putting an RFC-invalid email onto the wire; there's enough of them in the world already. :-) > Especially since, if you think you

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Ken, > I just have a hard time adding a switch to send (or really, any nmh > utility) when there's already OS-supported mechanism for overriding > the locale for individual commands by changing the environment > variable. I'm surprised whatnow(1) hasn't grown the ability to prefix the command

Re: [Nmh-workers] nmh 1.6: character set checks and exmh compatibility

Hi Ken, > > (3) assume charset=utf-8 (maybe allow this to be overridden in > > profile) > > We already do (1) and (2). (3) is the problem. Other people who have > thoughts on this topic are free to weigh in. Personally, I believe > that if you're doing LANG=C, you shouldn't be dealing with any

[Nmh-workers] Development Questions. check Programs. register.

Hi, Seems a bit odd to be mailing nmh-workers with actual "worker" content... I've noticed things like test/fakepop only get built on a `make check' because that needs to use them. OTOH, it would be nice to see compilation succeeds along with everything else in the `all' target. I've been

Re: [Nmh-workers] Changes to forw(1)

Hi David, > This message draft has In-Reply-To: and References: header lines, > introduced by the default replcomps. How would those lines get > through post? nmh would learn that those are in the directive set, like `To', and `Attach', and ideally something about their RFC format too so it can

Re: [Nmh-workers] Changes to forw(1)

Hi Paul, > i was starting to think i was done with this, but i guess i'm not. Rather that re-tread worn ground, how about a considered reply to my suggestion that all headers be known to nmh and the user having to add to that list, or pass it as the value of a `wire' header. :-)

Re: [Nmh-workers] Developing and Debugging a postproc

Hi Norm, > While developing and debugging a postproc, I want to use nmh to send > mail without using the postproc that I'm debugging, but to use it > sometimes when I do a send. Keep toggling the name of the postproc entry? sed -i '/^x*postproc:/!n; s/^x/y/; s/^p/xp/; s/^y//' .mh_profile

[Nmh-workers] Capitalisation in man pages.

Hi, I wondered if any thought has been given to capitalisation in man pages of commands, etc., that are case senstive. I think if a sentence starts with `send', for example, and is talking about send(1) rather than the English word, then it should be lowercase as /usr/bin/Send is a different

Re: [Nmh-workers] When a message goes only to me, as a cc

Hi Ken, > I don't think we talked about it, but way back when I first posted > that script there was general discussion about how that was a pain and > (I believe prompted by you, actually) I fixed that in commit > 4857e59b250f2. Rings a bell. Looking again at the script, it's the -whom

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi, David wrote: > See docs/README.developers. Thanks, that helped quite a bit. I've pushed a trivial fix to master. If I've done anything wrong, e.g. not configured my ID properly, then let me know. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy

Re: [Nmh-workers] When a message goes only to me, as a cc

Hi, Norm wrote: > Would you be willing to tell me how, in such a script, I could detect > the presence or absence of a specific header, say "Exception: norm"? So, thanks to the other replies, Norm's happy taking Ken's http://lists.nongnu.org/archive/html/nmh-workers/2016-10/txthpshEQcPNr.txt and

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi David, > Great! We'll get you to the bleeding edge yet. :-) Through a cunning bit of social engineering the other day, I did apparently gain access to nmh's git repository. Is there anything that documents conventions in using it for the project, e.g. whether to check in directly on master

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi David, > Might Ken's commit adfed5f72bc07ac7de8dfc62188338d4d4f25a38 have fixed > this? Yes, indeed. I get identical output from iconv(1) and mhshow(1) with the function from http://git.savannah.gnu.org/cgit/nmh.git/tree/uip/mhshowsbr.c. > + if (errno == EINVAL) { > + /*

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi again, > 1.6's mhshow(1) says > > mhshow: unable to convert character set to gb2312, continuing... I meant to draw attention to that. It was converting *from* gb2312 (to UTF-8). -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___

[Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi, I got an email recently, probably spam, its charset is gb2312. $ mhlist msg part type/subtype size description 8032 text/plain 10K charset="gb2312" $ 1.6's mhshow(1) says mhshow: unable to convert character set to

Re: [Nmh-workers] Changes to forw(1)

Hi, kre wrote: > Rather, I usually delete [X-Mailer] as I consider it no-one else's > business which software I use Yes, I'd want to turn it off from that point of view too. I use mail(1) for short internal emails, and here it's provided by package s-nail which had a series of different

Re: [Nmh-workers] Changes to forw(1)

Hi Ken > I admit I am not clear where Ralph stands on this particular issue; > perhaps the Marmite shortage is affecting things :-) Marmite's basic ingredient is yeast sludge, a waste product from brewing beer. Give me the beer. It's solely produced in Burton, which used to have a large

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