Re: [Nmh-workers] ChangeLog file missing?

>While wrapping up nmh-git under a gentoo ebuild, I noticed that the default >src_install section ended up wanting to copy ChangeLog to the target >filesystem. A quick look in the git tree showed no ChangeLog file, so >either the misplaced need for the file is an effect of nmh's automake >magic,

Re: [Nmh-workers] gmail oauth2 howto

>Now over to dist and see how google treats it. Anyone know already? AFAIK, it should work fine. I do not believe that the webmail interface shows the Resent-From and Resent-To headers, though. --Ken ___ Nmh-workers mailing list

Re: [Nmh-workers] forw

>I don't recall when attachments first came into nmh, if I ever knew. But I >don't understand why the feature I talked about was not added to forw at that >time. Maybe it was because, for some reason I don't understand it is >difficult?? Weee ... it depends what you mean by "attachments".

Re: [Nmh-workers] gmail oauth2 howto

>Using normal smtp/port26 I managed to filre a nice bash loop over the >meesages sending them one bu one using dist, and '-whatnowproc send'. Works >fine, but how am I supposed to add the handlful of headers which seems to >be required for send using oauth? I think you can add the appropriate

Re: [Nmh-workers] forw

Ken Hornstein writes: >>This message is not a complaint, a request, or even a suggestion. It just >>represents my wanting to understand the design of forw better. It seems to >>me that there ought to be an option, indeed the default, for the new message >>to contain all the

[Nmh-workers] gmail oauth2 howto

Hi all, I'm trying to get the new oauth2 support working but find the documentation to be somewhat sparse and need some assistance. The overall goal is to be able to forward a bunch of messages to a gmail account using dist (so the 822 To/From headers will be intact as well as the mime

Re: [Nmh-workers] forw

>In September there were four Emails (forwarded below), from you and >David Levine, that seem to say that what I want to do is not built into >nmh. The -mime argument to repl, together with "mime" at the whatnow >prompt, does something apparently quite different. Let me try to explain it in

[Nmh-workers] ChangeLog file missing?

While wrapping up nmh-git under a gentoo ebuild, I noticed that the default src_install section ended up wanting to copy ChangeLog to the target filesystem. A quick look in the git tree showed no ChangeLog file, so either the misplaced need for the file is an effect of nmh's automake magic, or

Re: [Nmh-workers] Starting the final call for features for 1.7

Hi Laura, > But I get them in the order they arrived. I want them in the order > they were sent, which can be a whole lot different, before I read > them. Use sortm(1) on the sequence, e.g. `sortm .-last'. Or am I misunderstanding? (Don't run `sortm' without arguments by mistake as it

Re: [Nmh-workers] forw

>MIME broke all that. a lot of UI's can't cope with attachment trees >where one rfc822 includes another which has attachments. the way modern >graphical MIME UI's work is by iterating down through the forwarded >message's MIME tree and attaching each attachment to the top level of >the

Re: [Nmh-workers] forw

Ken Hornstein wrote: MIME broke all that. a lot of UI's can't cope with attachment trees where one rfc822 includes another which has attachments. the way modern graphical MIME UI's work is by iterating down through the forwarded message's MIME tree and attaching each attachment to the top

Re: [Nmh-workers] forw

>if it's a 100MByte attachment then i rather hate having to make a copy >in my local file system of each (or perhaps, all) attachments as i go >about destructively flattening things. far better to just include the >enclosing message as an rfc822 attachment and let the receiver see the >depth

Re: [Nmh-workers] forw

Paul Vixie writes: > i think what i'm suggesting is that forw needs a -auto option, which > ought to be made the default, which will detect that MIME was used > instead of RFC 934 on the message i'm forwarding, and DTRT ("do the > right thing") or perhaps even DWIM ("do what i mean").

Re: [Nmh-workers] Starting the final call for features for 1.7

Date:Sun, 09 Oct 2016 23:33:14 +0200 From:Laura Creighton Message-ID: <201610092133.u99lxea8000...@theraft.openend.se> | But I get them in the order they arrived. I want them in the order they | were sent, which can be a whole lot different,

Re: [Nmh-workers] forw

>what those of us who loved and used burst(1) in the RFC 934 era, and i >may be speaking for Norm here but i don't know, is that "f" "o" "r" "w" >"\n" at the shell prompt just does the right thing. telling me that i >have to pay attention to how the message i received was encoded toward >me so

Re: [Nmh-workers] gmail oauth2 howto

Also, you'll need to use mhlogin before using xoauth2. See the mhlogin(1) man page for instructions and example with Gmail. David ___ Nmh-workers mailing list Nmh-workers@nongnu.org https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: [Nmh-workers] forw

Ken Hornstein writes: >>In September there were four Emails (forwarded below), from you and >>David Levine, that seem to say that what I want to do is not built into >>nmh. The -mime argument to repl, together with "mime" at the whatnow >>prompt, does something apparently quite

Re: [Nmh-workers] forw

Norm wrote: > But what I don't understand is why isn't it? In fact, why isn't that > an option to forw, or even its default? I'm not sure what "it" is. Do you want to include attachments from more than one message? Do you want to always include all attachments from those one or more messages?

Re: [Nmh-workers] forw

>>1) You have asked to send someone all of the attachments from a particular >>message. That functionality is not native to nmh, but it is possible >>to script it. > >But what I don't understand is why isn't it? In fact, why isn't that >an option to forw, or even its default? Well, geez Norm

Re: [Nmh-workers] forw

David Levine writes: >Norm wrote: > >> But what I don't understand is why isn't it? In fact, why isn't that >> an option to forw, or even its default? > >I'm not sure what "it" is. Do you want to include attachments from >more than one message? Do you want to always include

Re: [Nmh-workers] gmail oauth2 howto

On Sun, Oct 9, 2016 at 8:12 PM, David Levine wrote: > Also, you'll need to use mhlogin before using xoauth2. See > the mhlogin(1) man page for instructions and example with > Gmail. > > David > Tried that, and adding -tls moved things forward a bit (strace shows STARTTLS and

Re: [Nmh-workers] Starting the final call for features for 1.7

>But I get them in the order they arrived. I want them in the order they >were sent, which can be a whole lot different, before I read them. > >I use my own filter for that. Be nice if nmh did that natively. as part >of folder? I think sortm can do that? Or am I not understanding what you are

Re: [Nmh-workers] gmail oauth2 howto

Ken wrote: > [Anders:] > >Trying to send a single message interactively...what's the mts.conf > >settings required? I tried server=smtp.gmail.com and strace suggests that > >it figures out to use port 587 itself (triggerd by the -sasl I guess), nmh (post(1) now defaults to using the submission

Re: [Nmh-workers] gmail oauth2 howto

>Is there a verbose switch to show e.g. which user/pwd its using? I've been >away from nmh for 15 years so memory is a bit rusty... The -snoop flag to send will show the complete network transaction, and includes decoding the base64 encoding. In this particular case, though, I believe it won't

Re: [Nmh-workers] forw

Ken Hornstein writes: >>>1) You have asked to send someone all of the attachments from a particular >>>message. That functionality is not native to nmh, but it is possible >>>to script it. >> >>But what I don't understand is why isn't it? In fact, why isn't that >>an option to

Re: [Nmh-workers] Starting the final call for features for 1.7

Laura wrote: > But I get them in the order they arrived. I want them in the order they > were sent, which can be a whole lot different, before I read them. > > I use my own filter for that. Be nice if nmh did that natively. as part > of folder? Sounds like a job for sortm(1). It defaults to