[nmh-workers] sndmail program with parameters?

2018-05-26 Thread Eduardo Alvarez
Hello, list,

I use msmtp as my sendmail program, and keep my configuration file in a
nonstandard place. I tried including this in mh_profile as follows:

send: -mts sendmail/pipe -sendmail "/usr/bin/msmtp -C /path/to/rc"

however, send is interpreting -C as an argument to istself, rather than taking
everything between quotes as the argument to -sendmail. Is this expected? Is
there a way to pass parameters to the sendmail program?

Kind regards,

Eduardo alvarez

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] sndmail program with parameters?

2018-05-26 Thread Eduardo Alvarez
Thank you Ralph. Sorry for missing that in the docs. 

-- 
  Eduardo Alvarez
  ealva...@fastmail.com

On Sat, May 26, 2018, at 11:42 AM, Ralph Corderoy wrote:
> Hi Eduardo,
> 
> > send: -mts sendmail/pipe -sendmail "/usr/bin/msmtp -C /path/to/rc"
> >
> > however, send is interpreting -C as an argument to istself, rather than 
> > taking
> > everything between quotes as the argument to -sendmail. Is this expected?
> 
> Yes, unfortunately.  mh_profile(5) says
> 
> Shell quoting conventions are not available; each token is separated
> by whitespace.
> 
> > Is there a way to pass parameters to the sendmail program?
> 
> No, you'd normally have a shell-script wrapper, perhaps in your
> `mhpath +' directory.
> 
> -- 
> Cheers, Ralph.
> https://plus.google.com/+RalphCorderoy

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


[nmh-workers] can comp return the filename of the newly created draft?

2018-06-15 Thread Eduardo Alvarez
Hello, list,

I've been toying with creating a vim frontend for nmh, taking as much advantage
of the existing toolbox as possible. The way I have currently envisioned the
process is to call comp within the editor (using -nowhatnow and -noedit), and
have the editor open a new buffer with the newly created draft. However, for
this to work I'd need to know the name of the newly created draft, specially if
there's more than one available draft. Is there a way to receive this
information from comp itself (or from any other nmh tool)?

Thanks in advance,

Eduardo Alvarez

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] can comp return the filename of the newly created draft?

2018-06-15 Thread Eduardo Alvarez
Hello, Ralph,

Thank you very much for your answer. While the whole process seems a bit
fiddly, as you said, using all with mhparam is very useful.

Regards,

Eduardo Alvarez

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] can comp return the filename of the newly created draft?

2018-06-15 Thread Eduardo Alvarez
Thanks, Hymie,

This would work, though I think Ken's approach is more suitable to what I had in
mind.

Regards,

Eduardo Alvarez

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] mmh-0.4 is released! (meillo's mail handler)

2019-01-14 Thread Eduardo Alvarez
Great news, and good job, team!

-- 
  Eduardo Alvarez
  ealva...@fastmail.com

On Mon, Jan 7, 2019, at 7:15 AM, Philipp Takacs wrote:
> Hi everyone
> 
> After more then a year I can announce the release of mmh-0.4
> 
>   http://marmaro.de/prog/mmh/files/mmh-0.4.tar.gz
> 
> The important changes are:
> - pick now has thread support
> - pick and scan merged into one binary
> - mhl globing support for filter out some header fields
> - mhl trim (ported from nmh)
> - whatnow2 is finished for replacing whatnow
> - whom supports message argument
> 
> Have a look at the NEWS file in the tarball for more information about
> the changes. The full changelog is in the ChangeLog file in the tarball.
> All changes and the current developer version can be found in the git
> at http://git.marmaro.de/mmh
> 
> mmh 0.4 has in total 33,072 SLOC. This is a bit more then then mmh 0.3
> which has 32,645 SLOC.
> 
>   SLOCChange  Directory   SLOC-by-Language (Sorted)
>   19159   (+100)  uip ansic=18320,sh=839
>   7061(+102)  sbr ansic=6987,awk=74
>   3236(+219)  testsh=3236
>   2753top_dir sh=2753
>   764 h   ansic=764
>   60  config  ansic=60
>   38  man sh=38
> 
> The most new code comes from new features in mhl and the scan/pick
> merge. On the other side the whole scan.c file is removed. Also whatnow
> is still in the count. (All numbers calculated by sloccount.)
> 
> Thanks to everyone who contributed to this release. Some of the work is
> ported from nmh. The commits:
> 
> 47  Philipp Takacs 
> 22  markus schnalke 
>  7  Dmitry Bogatov 
>  5  c_14 
>  4  Vasilii Kolobkov 
>  2  Larry Hynes 
>  1  David Levine 
>  1  mor0i...@gmail.com 
> 
> Further contributions on the mailing list by: Jan/subpath, and Link
> Satonaka.
> 
> Philipp
> 
> -- 
> nmh-workers
> https://lists.nongnu.org/mailman/listinfo/nmh-workers
>

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers


Re: [nmh-workers] archival and searching of nmh folders

2019-01-24 Thread Eduardo Alvarez
On Mon, Jan 21, 2019, at 2:00 AM, Robert Elz wrote:
> Date:Sun, 20 Jan 2019 21:35:00 -0500
> From:Paul Fox 
> Message-ID:  <20190121023500.21b935180...@grass.foxharp.boston.ma.us>
> 
>   | you're looking for "mairix".  i install it via debian/ubuntu package,
>   | but google will find you the sources quickly.  it's fantastic.
> 
> It is available in pkgsrc too (from NetBSD, though it also runs on
> lots of other systems) so I thought I would give it a try.
> 
> Easy to build and install, not difficult to configure, but after that,
> a bit of a nightmare...
> 
> While it supposedly understands mh format, it doesn't understand
> mh drafts (with the - separator between header and body, rather
> than the blank line) and complains about all of those.
> 
> It also complains about stuff it shouldn't really be looking at at all,
> if I read its doc correctly, like (non text attachmants encoded in
> formats it doesn't understand, like x-uuencode ... I have lots of very
> very old messages - my mh directory dwarfs the one mentioned
> in the question) and has not real idea (it seems) what to do with
> filenames for attachments which are not ascii (or something, I have
> lots of those as well.)
> 
> But the killer is that eventually the indexing operation simply dumped core.
> 
> kre
> 
> 
> -- 
> nmh-workers
> https://lists.nongnu.org/mailman/listinfo/nmh-workers
>

You might also like to look into notmuch if mairix is not to your liking. It 
also understands MH.

-- 
  Eduardo Alvarez
  ealva...@fastmail.com

-- 
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers