gmane.mail.nmh.devel

Re: nmh dependence on metamail

Alexander Zangerl — 2013-05-19T02:36:44

in 2008 i modified exmh to try mimencode first (that's from metamail 
if you still have it), then fall back to recode and if that's unavailable
use the slow internal encoder. 

recode is present in debian and ubuntu, and is not hard to use: 
$ recode data..quoted-printable < whatever > otherthing
$ recode base64..data < encoded > raw

regards
az

nmh dependence on metamail

Dale Alspach — 2013-05-18T16:20:00

Ubuntu 12.04 includes a package for nmh but none for metamail. Someone
noted this in a bug report. Debian seems to have abandoned metamail.
In Ubuntu 10.xx I was able to make it work from source.
The source that I have for metamail 2.7 will not compile on my upgraded
system and I am not knowledgeable enough to try to fix it.

Are there any replacements for metamail  or an updated source?

exmh seems to work fine.

Dale Alspach

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: nmh dependence on metamail

Andy Bradford — 2013-05-18T19:39:51

Thus said Ken Hornstein on Sat, 18 May 2013 14:50:26 -0400:


There is another quoted-printable decoder  called qprint that might work
(not sure  if this is  what you  are thinking of,  but it is  in OpenBSD
ports).

I have no problems using metamail on OpenBSD from ports---works great.

Andy

Re: nmh dependence on metamail

Ken Hornstein — 2013-05-18T18:50:26

Dale,

There's no need to send something to nmh-workers, exmh-users, _and_ me,
because I'm on both lists :-)

Let me explain the state of the world as I know it:

- nmh has no dependencies on metamail.  Zero, zip, nada.  If a packaging
  system lists nmh as having a dependency on metamail, that's an error.
- exmh does have a dependency on metamail, sort of.  It uses mmencode to
  decode quoted-printable and base64.  It can use another program (which
  I forget the name of but comes on some Linux systems) instead.  It also
  has an internal decoder for those things, but in my experience that
  has a file descriptor leak (that may be fixed).

I really think exmh needs a new release that removes any mention of
metamail, because that package is really long in the tooth nowadays.

--Ken

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Date syntax

2013-05-18T16:16:58

Thank you, instead of RTFMing the man I just searched it for "rfc".

    Norman Shapiro
    798 Barron Avenue
    Palo Alto CA 94306-3109
    (650) 565-8215
    norm< at >dad.org

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Date syntax

Ken Hornstein — 2013-05-17T16:03:20

Looks like it's ... according to the man page for "pick" ... RFC-822, plus
a few extras.  In the case of sortm, it's just the RFC-822 parser that
we have.  We're talking about the "-before" and "-after" switches to pick;
the -date switch is just a pattern match.

I remember some non-obvious things about -before and -after ... in some
cases, if you saw things like "yesterday", it's 24 hours previous to
now, rather than the whole day of yesterday.  But anyway, if it's not
a "special" time as listed in the pick man page, it uses the RFC-822
date parser.

--Ken

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Date syntax

Jerrad Pierce — 2013-05-17T16:08:09

FTM

       In addition to 822-style dates, pick will also  recognize  any  of  the
       days of the week ("sunday", "monday", and so on), and the special dates
       "today", "yesterday" (24 hours ago),  and  "tomorrow"  (24  hours  from
       now).   All  days  of the week are judged to refer to a day in the past
       (e.g., telling pick "saturday" on a "tuesday" means "last saturday" not
       "this saturday").

http://www.ietf.org/rfc/rfc0822.txt

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Date syntax

2013-05-17T15:40:09

Would somebody please point me to a specification of the date syntax used by pick and sortm.

    Norman Shapiro

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Does maildrop work correctly with nmh?

2013-05-13T15:36:07

I looked into it seriously but stayed with procmail... I ended up automating
the creation of my procmailrc from a file that looks a whole lot like a
~/.maildelivery file.  That makes the configuration information far more
dense, easily grep'able and results in verbose logging.

steve

Re: Does maildrop work correctly with nmh?

Bill Wohler — 2013-05-13T04:26:05

One thing I have my todo list is to consider sieve as a replacement to
procmail. It would be great to hear from anyone who is actually using
sieve.

Martin McCormick <martin< at >dc.cis.okstate.edu> writes:

Re: Responding to calendar requests

Bill Wohler — 2013-05-13T04:18:23


Sometimes you want to add text to your reply, and sometimes you don't,
and sometimes you want to accept or decline without notifications at
all.

I'd therefore like to be able to say something like "cal
[-accept|-decline|-maybe] [-edit|-noedit] [-notify|-nonotify]"

However, MH doesn't natively handle any MIME parts, does it? If not, we
don't want to start now. However, we can pass the job on to an external
(contrib) program. Then create an .mh_profile alias to make use of it.
At least it would be built-in, if not native.

Re: Threads

Bill Wohler — 2013-05-13T01:57:15


Gotcha, thanks!

Still prefer the MH-E way (perhaps without the []/<> characters) as
well as the folded gnus way.

Happy to let the implementer have the last word though :-).

Re: extra and missing blank lines with replyfilter

David Levine — 2013-05-09T11:54:01


par on Fedora 18 and 19 includes the i18n patch.

Fedora users, this will update your par with Joel's patch:

  $ sudo yum install --enablerepo=updates-testing par

It should be out of testing in a week or so, then you'll be
able to:

  $ sudo yum update par

The version number of the update is 1.52-10.

David

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: extra and missing blank lines with replyfilter

Ken Hornstein — 2013-05-05T21:04:08

Just a note: Joel is being generous here.  My contribution essentially
consisted of suggestions from the sidelines; he did all of the real work.
I'm just glad it was finally tracked down!

--Ken

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: extra and missing blank lines with replyfilter

Joel Uckelman — 2013-05-05T19:58:11

Thus spake Joel Uckelman:

Follow-up for anyone playing along at home:

After quite a lot of faffing about, Ken and I figured out the problem.
There was nothing wrong with replyfilter, nor with my configuration on
my machine. The culprit was the i18n patch applied to my version of par,
which replyfilter calls. That patch converted many---but not quite all!
---of the string I/O functions in par from the narrow char versions to
the wide wchar_t versions. Mixing narrow and wide writes to the same
stream is a Bad Thing, but only produces bad output with par when its
stdout is one end of a pipe, as it is when called from replyfilter.

If you're using a stock version of par, this won't affect you, but if
you're using a par with the i18n patch, then you might want my patch for
the above problem. 

For more details (including my patch), see the bug I filed:

  https://bugzilla.redhat.com/show_bug.cgi?id=959794

Re: reason: 554 5.7.0 Message Size Violation

2013-05-05T14:12:51

3 megabytes



    Norman Shapiro

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: reason: 554 5.7.0 Message Size Violation

Ralph Corderoy — 2013-05-05T09:21:06

Hi Norm,


What's the size of the expanded contents?  Perhaps the MTA is sneaking a
peek whilst chatting and that's the limit being exceeded.

Cheers, Ralph.

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: reason: 554 5.7.0 Message Size Violation

David Levine — 2013-05-04T18:37:38


That's tiny, it shouldn't cause the problem.


Does your zip file have folders in it?  If so, I would try
just sending only files:

  https://discussions.apple.com/thread/4897781?start=0&tstart=0


I can't believe that's the problem.

Just for fun, if you want to see the size limit of your SMTP
server, try adding -snoop to your send command and looking
for a 250-SIZE line in the chatter.  But in this case, the
problem was with the SMTP server of mac.com.

David

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Setup help???

Bob Carragher — 2013-05-04T18:33:15


Got it.


Okay, I see.

Yeah, I would prefer to use the more integrated flows, so I'm not
likely to switch off of fetchmail in this case.

Thanks!

Bob

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: Setup help???

Bob Carragher — 2013-05-04T18:27:58


Nope, I use it at its most basic:  fetch email from the POP server
and dump it into /var/mail.

Bob

_______________________________________________
Nmh-workers mailing list
Nmh-workers< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers

Re: reason: 554 5.7.0 Message Size Violation

Ken Hornstein — 2013-05-04T18:14:52

That seems kinda small to me ... but see below.


AFAIK, no (I will note that there is stuff in nmh to do MIME-splitting properly,
but I don't know if the remote side will handle it properly; it's one of
those lesser-implemented corners of the MIME spec).


Well, in theory you'd connect to the server MX and ask for it.  So ...

% host -t mx mac.com
mac.com mail is handled by 10 mx5.mac.com.akadns.net.
mac.com mail is handled by 10 mx6.mac.com.akadns.net.
mac.com mail is handled by 10 mx1.mac.com.akadns.net.
mac.com mail is handled by 10 mx2.mac.com.akadns.net.
mac.com mail is handled by 10 mx3.mac.com.akadns.net.
mac.com mail is handled by 10 mx4.mac.com.akadns.net.

But if you do that:

% telnet mx1.mac.com.akadns.net 25
Connected to mx1.mac.com.akadns.net (17.172.34.9).
Escape character is '^]'.
220 st11p00mm-smtpin005.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012))
EHLO foo.com
250-st11p00mm-smtpin005.mac.com
250-8BITMIME
250-PIPELINING
250