On 6 May 2012 at 14:23, Ken Hornstein wrote:
> I am pleased to announce to second release candidate (RC2) of nmh 1.5 is
> now available. You can find it for download here:
>
> http://download.savannah.gnu.org/releases/nmh/nmh-1.5-RC2.tar.gz
>
> Changes from RC1 include portability fixes f
On 6 May 2012 at 14:23, Ken Hornstein wrote:
> I am pleased to announce to second release candidate (RC2) of nmh 1.5 is
> now available. You can find it for download here:
>
> http://download.savannah.gnu.org/releases/nmh/nmh-1.5-RC2.tar.gz
On Mandriva 2007.0 I gett these errors from 'mak
On 6 May 2012 at 14:23, Ken Hornstein wrote:
> I am pleased to announce to second release candidate (RC2) of nmh 1.5 is
> now available. You can find it for download here:
>
> http://download.savannah.gnu.org/releases/nmh/nmh-1.5-RC2.tar.gz
On Mandriva 2010.2 'make check' reports:
./te
On 6 May 2012 at 15:00, Kevin Cosgrove wrote:
>
> On 6 May 2012 at 14:23, Ken Hornstein wrote:
>
> > I am pleased to announce to second release candidate (RC2) of nmh 1.5 is
> > now available. You can find it for download here:
> >
> > http://download.savannah.gnu.org/releases/nmh/nmh-1
>With my ~/.mh_profile from nmh 1.0 I tried 'comp' and got this result:
>
> comp: "/d>.cbKoUjQXLC2-C;%m": format compile error - component or function
> name expected
> comp:
So ... what does your component file look like? I assume you have a custom
one. Although ... that looks strange, not s
On 6 May 2012 at 18:35, Ken Hornstein wrote:
> >With my ~/.mh_profile from nmh 1.0 I tried 'comp' and got this result:
> >
> > comp: "/d>.cbKoUjQXLC2-C;%m": format compile error - component or function
> > name expected
> > comp:
>
> So ... what does your component file look like?
Attached.
>Attached. But, I did change my user name and real name in the
>file to throw off a spammer-bot or two.
That was just your mh_profile; I was talking about (I guess for you)
.components/components; if you prefer, you can send your components
file to me privately.
--Ken
__
On 6 May 2012 at 19:15, Ken Hornstein wrote:
> >Attached. But, I did change my user name and real name in the
> >file to throw off a spammer-bot or two.
>
> That was just your mh_profile; I was talking about (I guess for you)
> .components/components; if you prefer, you can send your components
>On Mandriva 2007.0 I gett these errors from 'make check'.
So, looking at those errors ...
>FAIL: test/bad-input/test-header
That _MIGHT_ be because you have a terminal wider than 80 characters; is
that true? Obviously we should fix that. Actually, if you want to try
fixing that yourself ... i
>But, once I get around the installation issue, why does 'inc'
>need special group ownership and SGID treatment? Would that
>reason be related to the 'inc' in Fedora's build of nmh-1.4
>asking me for a password when I want to 'inc' my email?
Those things are unrelated.
The issue is that "inc" wa
> comp: "/d>.cbKoUjQXLC2-C;%m": format compile error - component or function
> name expected
Just as a follow-up ...
It turned out Kevin's problem was that he had an X-Face line in his components
file. Now that all components files are processed with mh-format, you need
to escape % and \ by do
On 6 May 2012 at 19:19, Ken Hornstein wrote:
> >On Mandriva 2007.0 I gett these errors from 'make check'.
>
> So, looking at those errors ...
>
> >FAIL: test/bad-input/test-header
>
> That _MIGHT_ be because you have a terminal wider than 80 characters; is
> that true? Obviously we should fix
After a day of hacking on my email system is looks like exmh
CVS-2012-05-02 and nmh-1.5-RC2 have installed and are working on
three of my systems.
Nice.
Thanks!
--
Kevin
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org
>I made sure that my window is 78 characters and reran the test.
Well, it should actually be 80 character ... I suspect we get some of this
wrong. More to fix!
>I backed out the one change in ~/.mh_profile
>There are a number of one line changes in ~/Mail/.components/* all of
>them being the ad
On 6 May 2012 at 14:23, Ken Hornstein wrote:
> I am pleased to announce to second release candidate (RC2) of nmh 1.5 is
> now available. You can find it for download here:
>
> http://download.savannah.gnu.org/releases/nmh/nmh-1.5-RC2.tar.gz
I'm building and packaging this. This part of t
>I made sure that my window is 78 characters and reran the test. Now
>I get:
>
>FAIL: test/bad-input/test-header
>FAIL: test/format/test-myhost
>FAIL: test/format/test-mymbox
>FAIL: test/inc/test-deb359167
I fixed the test-header test to explicitly specify a width; that
fixed the problem for me.
I'm having a serious problem with 1.5 RC2. I'm using nmh 1.5 RC2 with
exmh 2.8.0 + CVS through May 2, 2012. My MTA is postfix 2.3.6.
The problem is when I 'inc' via exmh I've been getting multiple
messages mixed together into one file. This occured on 3 of 44
messages.
I think I'll have to b
>I'm having a serious problem with 1.5 RC2. I'm using nmh 1.5 RC2 with
>exmh 2.8.0 + CVS through May 2, 2012. My MTA is postfix 2.3.6.
>From looking at the message you provided ... I see no From header seperating
the messages. Does the spool file contain them? And did this work with the
previ
On 7 May 2012 at 13:57, Ken Hornstein wrote:
> >I'm having a serious problem with 1.5 RC2. I'm using nmh 1.5
> >RC2 with exmh 2.8.0 + CVS through May 2, 2012. My MTA is
> >postfix 2.3.6.
>
> From looking at the message you provided ... I see no From
> header seperating the messages.
Nor did I.
>> Does the spool file contain them?
>
>Impossible for me to tell after the 'inc' as the spool file is
>empty. When my email notifier (xlbiff*) pops up I'll have a look
>at the spool prior to 'inc'. At a rate of 3/44 with issues I
>ought to be able to catch this in a day or two.
Looking at the c
Hi Kevin,
Ken wrote:
> Kevin wrote:
> > Impossible for me to tell after the 'inc' as the spool file is
> > empty. When my email notifier (xlbiff*) pops up I'll have a look
> > at the spool prior to 'inc'.
Perhaps you could have a new `inc' earlier in PATH that copies the mail
spool file to somew
>It may well be it's inconsistent on the same spool file, or it's a
>boundary issue, e.g. `From ' cross a buffer-length boundary.
We have a specific test for that, so I _hope_ that's not the issue.
--Ken
___
Nmh-workers mailing list
Nmh-workers@nongnu.
On 7 May 2012 at 14:16, Ken Hornstein wrote:
> >> Does the spool file contain them?
I found one email in the spool just now where a LinkedIn email
doesn't start with a "From " line. One of the post-inc emails that
was concatenated also had trailing LinkedIn content. The other
concatenated em
On 7 May 2012 at 19:58, Ralph Corderoy wrote:
> Hi Kevin,
>
> Ken wrote:
> > Kevin wrote:
> > > Impossible for me to tell after the 'inc' as the spool file is
> > > empty. When my email notifier (xlbiff*) pops up I'll have a look
> > > at the spool prior to 'inc'.
>
> Perhaps you could have a
On 7 May 2012 at 12:52, Kevin Cosgrove wrote:
> On 7 May 2012 at 14:16, Ken Hornstein wrote:
>
> > >> Does the spool file contain them?
>
> I found one email in the spool just now where a LinkedIn email
> doesn't start with a "From " line. One of the post-inc emails that
> was concatenated al
On 7 May 2012 at 10:08, Ken Hornstein wrote:
> >I made sure that my window is 78 characters and reran the test. Now
> >I get:
> >
> >FAIL: test/bad-input/test-header
> >FAIL: test/format/test-myhost
> >FAIL: test/format/test-mymbox
> >FAIL: test/inc/test-deb359167
>
> I fixed the test-header t
>I did the localname change with a patch from my RPM spec file so that
>I wouldn't have to edit the mts.conf file by hand after installing it.
>If you can think of a better way to do this, I'm open to suggestions.
I just wanted to make sure there wasn't a problem with your installation;
it sounds
>Does 'inc' remove '^from .*' lines as it incorporates mail? If
>so, then I might have found nothing important.
Yes, it does; the mailbox delimiter isn't part of RFC-5822. If you're
getting this kind of mailbox corruption, then it sounds like inc isn't
using the same locking style that your loca
nmh 1.5 RC2 builds and runs fine on Red Hat Enterprise Linux 4 and 5.5.
It's also been quite solid on Mandriva 2007.0 for the last few days.
HTH
--
Kevin
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/list
Hi,
I'm not sure whether this is my trouble, nmh, or exmh. But, I can't
get it to work. One person I know sends me messages containing
Disposition-Notification-To: John Smith
exmh responds to that by displaying a message in the main window
allowing me to "Send confirmation", "Send denial"
>The reason for the error is that nmh 1.5 needs a "From: " line.
>I don't know how to communicate via ~/.mh_profile to send in such
>a way that it can pick up a -form to add it, as I do
>with 'comp'.
Wow, people actually _use_ disposition notifications? I'm shocked; haven't
seen one of those in
Earlier I reported an issue with multiple messages ending up in
the same mh message. We concluded, given that my spool file was
messed up, that this couldn't be nmh. That part stands.
I disabled my procmailrc file, and the problem went away. I've
put back in all but two rules by now, and every
> 2. To ask if there are new features in nmh or exmh that aid
>with today's proliferation of quoted-printable and base64
>messages.
Stupid question time ... did you happen to read a) my initial
announcement for the first release candidate for nmh, b) the release
notes to nmh, or c) my repl
On 14 May 2012 at 10:35, Ken Hornstein wrote:
> > 2. To ask if there are new features in nmh or exmh that aid
> >with today's proliferation of quoted-printable and base64
> >messages.
>
> Stupid question time ... did you happen to read a) my initial
> announcement for the first release ca
My $_ is bad, no lexicalization of $boundary is bad.
If you must do it all in one fell swoop w/o pre-declaring $boundary use:
local($_, $boundary) = ...
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nm
>My $_ is bad, no lexicalization of $boundary is bad.
Errr ... is "my $_" bad? Later version of perl are perfectly fine with
it. I had tested with perl 5.10 and perl 5.12.
--Ken
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu
$_ is a special global, you lexicalize these with local not my,
especially if you want to be backwards compatible ;-)
Although 5.8 is a bit old, it's still common and has good Unicode
support, therefore as long as the changes to support are minimal
I suggest it is well worth doing.
__
Sorry, by lexicalize I mean limit scope,
since lexical specifically refers to my and our.
FYI my($_) was introduced in 5.10
http://perldoc.perl.org/5.10.0/perldelta.html#Lexical-$_
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongn
>$_ is a special global, you lexicalize these with local not my,
>especially if you want to be backwards compatible ;-)
>
>Although 5.8 is a bit old, it's still common and has good Unicode
>support, therefore as long as the changes to support are minimal
>I suggest it is well worth doing.
Sounds g
39 matches
Mail list logo