Re: format and output all received: lines in an e-mail message
dear Big I Down Under, > It is this kind of thing that makes MH so nice. indeed!
Re: format and output all received: lines in an e-mail message
Date:Sat, 23 Nov 2019 20:26:27 +0530 From:Greg Minshall Message-ID: <374462.1574520...@apollo2.minshall.org> | combined with (new-fangled) bash "process substitution", If you're planning on using this much, I'd suggest avoiding making bash do all that work (and making things work with shells that don't have this) by simply creating a one line file in your $(mhparam path) directory, and using that file name (in that dir no path is needed) echo received:split,compress,nowrap > "$HOME/$(mhparam path)/received-only" (pick your own file name), just once, and then mhl -form received-only $(mhpath +inbox 794) (the switch from `` to $() is simply because the latter is in general better to use, though for a simple case like this it makes no difference really) and if you're going to do this often, put the one line in a script, ane replace "+inbox 794" there with "$@" (including the quotes), insert before that line case "$#" in 0) set -- cur;; esac (use an "if" instead of case if you prefer, and you can make it fancier by appending "cur" any time there are no message args, rather than only when there are no args at all if you want), and you end up with something that feels and acts just like any other MH command. It is this kind of thing that makes MH so nice. kre
Re: format and output all received: lines in an e-mail message
Thus said Ralph Corderoy on Sat, 23 Nov 2019 12:03:42 +: > Andy is correct. Mailman has a `nodupes' flag for every subscription > and it's set for Andy's subscription. Not any longer. :-) I didn't realize I had control over this. Andy -- TAI64 timestamp: 40005dd9a302
Re: format and output all received: lines in an e-mail message
Valdis Klētnieks wrote in <235182.1574454918@turing-police>: |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 is |> the real original thing, which i think is a value by itself. |> But the world does not seem to cherish this. | |A bigger issue is GMail's handling of Message-Id: | |If you post to a mailing list, it notes the Message-Id: on the way out, |and when the list sends its copy to you, it gets silently munched by the |duplicate suppressor. So unless you are careful with Fcc: and have |nmh save a copy in the appropriate folder, your comments in a thread |go poof. Poof also in use to spring out of existence. To me such situations happen regulary even without GMail ._. Before the upcoming release of my MUA i will have to add a reply-to-swapin variable so one can use the address in Reply-To: not only as an exclusive receiver override (as with M-F-T:), but only to replace the one address in From: (or Sender:) with it. This is the only idea i have to work with DKIM++ the way it is in use on those lists which use the "x via y" syntax. (Even if noone wants to hear just about any critics regarding DKIM / DMARC / ARC, neither here nor on other lists.) --End of <235182.1574454918@turing-police> --steffen | |Der Kragenbaer,The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
Re: format and output all received: lines in an e-mail message
thanks to everyone for all the replies! Ken suggested mhl. conveniently combined with (new-fangled) bash "process substitution", the following does exactly what i want: mhl -form <(echo received:split,compress,nowrap) `mhpath +inbox 794` cheers, Greg
Re: format and output all received: lines in an e-mail message
oof, ships crossing in the night -- thanks! (and for the "-nomoreproc".) > Hi Greg, > > > yes, awk and sed are in my repertoire, but, well, i was wondering if i > > could avoid those in this case. > > For list's archive's completeness, the nmh way, using mhl(1) as Ken > suggested, is > > /usr/lib/nmh/mhl -nomoreproc \ > -form <(echo received:compress,nowrap,split) \ > `mhpath .` > > -- > Cheers, Ralph. >
Re: format and output all received: lines in an e-mail message
Hi Ken, > Andy Bradford wrote: > > Curiously, the email you sent me appears to have never arrived via > > the MLM that nmh-workers uses---I suspect it has one of those fancy > > features that thinks an email that was sent to one address shouldn't > > be also sent to another address (i.e. if the address of the To/Cc > > recipient is also a member of the MLM exclude one of them). Andy is correct. Mailman has a `nodupes' flag for every subscription and it's set for Andy's subscription. Mailman says nodupes -- Does the member want to avoid duplicates of the same message? > I see double-replies of messages and my own messages sent to me on the > mailing list. That same nodupes flag is set for your subscription too, so that's odd. Only two subscribers do not have the flag set. -- Cheers, Ralph.
Re: format and output all received: lines in an e-mail message
Hi Greg, > yes, awk and sed are in my repertoire, but, well, i was wondering if i > could avoid those in this case. For list's archive's completeness, the nmh way, using mhl(1) as Ken suggested, is /usr/lib/nmh/mhl -nomoreproc \ -form <(echo received:compress,nowrap,split) \ `mhpath .` -- Cheers, Ralph.
