>Right there you have cleared things up for me. When you say command line
>switch you're talking:
>
>comp -to person1 -to person2
>
>from the command line. I never knew you could do that. (But then Conrad
>didn't know about "new" and he knows a lot more than I do :-)).
Well, to be fair, that's a n
>
>I guess I was thinking that it was clear that this part of the man page
>was talking about the command-line switch "-to" and NOT the format of
>the draft file.
>
>But ... now that I think about it, most modern man pages start out
>explaining what each switch does, and we don't do that. So if yo
>How does one put into words what one finds confusing?
>
>When I read it I wasn't sure if it was:
>
>From: m...@email.net
>To: person1
>To: person2
>
>or To: person1, person2
>
>or To: person1 To: person2
>
>or To: person1 -to person2
>
>or To: person1
>-to person2
I guess I was thinking that it w
>>I just find the relevantsection of the comp man page:
>>
>>to be confusing. I'd appreciate an example as I have a serious aversion
>>to making a fool of myself.
>
>I wrote that section of the man page and I just re-read it now and I
>don't find it confusing, but obviously I am biased because I wr
>I just find the relevantsection of the comp man page:
>
>"By default the "To:" and "cc:" fields are empty. You may add addresses
>to these fields with the -to address and -cc address switches.
>You may give these switches multiple times to add multiple addresses."
>
>to be confusing. I'd apprecia
Hi Arthur,
> What I was trying to do was send email to both Conrad Hughes and
> Robert Elz thanking them for their help.
>
> I just find the relevantsection of the comp man page:
>
> "By default the "To:" and "cc:" fields are empty. You may add
> addresses to these fields with the -to address and
>Your email had two To fields. That's against RFC 2822 that states it
>may have none or one. Just pointing it out in case you had software
>create that problem instead of a human. :-)
>
>Some mailing-list subscribers bounced that email due to this problem.
>
>--
>Cheers, Ralph.
No, that was me
Hi Arthur,
> From: aalin...@riseup.net
> To: biz_nmh_work...@xrad.org
> To: k...@munnari.oz.au
> Cc: nmh-workers@nongnu.org
> Message-ID:
Your email had two To fields. That's against RFC 2822 that states it
may have none or one. Just pointing it out in case you had software
create that problem
>
On Dec 26, I asked:
>Is there any way to scan all folders at once to determine which have new
>unseen messages or am I reduced to going into each folder individually
>in which case I may scrap procmail and just have everything go into
>inbox?
I would just like to thank Conrad and Robert for tak
Robert> Try "new" ...
Dear oh dear. That's been in nmh for ten years and this is the first
I've heard of it? Ouch.
C.
Date:Thu, 26 Dec 2019 13:13:26 -0500
From:aalin...@riseup.net
Message-ID: <1da230645f410...@absalom.fios-router.home>
| Is there any way to scan all folders at once to determine which have new
| unseen messages
Try "new" ... of course using this assumes that the n
Hi aalinovi,
> Is there any way to scan all folders at once to determine which have new
> unseen messages or am I reduced to going into each folder individually
> in which case I may scrap procmail and just have everything go into
> inbox?
This might work for you:
flists -rec -noshowzero -sequ
It has taken the better part of 2 days for a non-technical person such
as I to get getmail, procmail and nmh all working together.
Is there any way to scan all folders at once to determine which have new
unseen messages or am I reduced to going into each folder individually
in which case I may scr
13 matches
Mail list logo
