Hi David,
> Ah, but it busts on Solaris:
>
> awk: syntax error near line 1
> awk: bailing out near line 1
>
> At least we know where the problem is.
Oh, line 1. `awk --posix' here suggests length would like parenthesis.
awk '!length() && e {next} {e = !length()} 1'
I wonder if `diff
Hi again David,
> I wonder if `diff -b' is the wrong approach as it's applying the -b to
> the whole file. Would using sed to canonicalise that one line to no
> spaces at start or end, and only one space in between be better?
Something like
sed '//n; /Need/!n; s/ */ /g; s/^ //; s/ $//'
I
Robert wrote:
> awk 'length($0) == 0 && e == 1 { next }
> { e = length($0) == 0 }
> { print }'
results in:
awk: syntax error near line 2
awk: illegal statement near line 2
Ralph wrote:
> Oh, line 1. `awk --posix' here suggests length would like parenthesis.
>
>awk '!length
Sorry if this is a repeat. I tried sending earlier, but I don't think it
got out.
Does anyone have an mts.conf setup that works with Fastmail.fm?
Ideally, I'd like to use their proxy server,
smtps-proxy.messagingengine.com, since my employer blocks outgoing
smtp connections.
I've tried using smtp
Rickard wrote:
> Forgive me for maybe being silly due to ignorance of Nmh internals, but
> 'elinks -dump' introducing leading whitespace might perhaps be remedied by
>
> > elinks -eval 'set document.browse.margin_width = 0' -dump [...]
Nice, I added that option to the elinks command used by
Hi David,
> > awk 'length($0) == 0 && e == 1 { next }
> > { e = length($0) == 0 }
> > { print }'
>
> results in:
> awk: syntax error near line 2
> awk: illegal statement near line 2
>
> > Oh, line 1. `awk --posix' here suggests length would like parenthesis.
> >
> >awk '!length(
Ralph wrote:
> Apparently, /usr/xpg4/bin/awk is POSIX compliant. Can build and
> test instructions for nmh on Solaris not state /usr/xpg4/bin needs
> to be up the front of PATH?
Yes, but then our buildbot provider, maintainer, and
gracious host would have to actually do that :-) But
seriously,
On Dec 8, 2013, at 11:03 AM, David Levine wrote:
>> Apparently, /usr/xpg4/bin/awk is POSIX compliant. Can build and
>> test instructions for nmh on Solaris not state /usr/xpg4/bin needs
>> to be up the front of PATH?
>
> Yes, but then our buildbot provider, maintainer, and
> gracious host woul
Peter wrote:
> Does anyone have an mts.conf setup that works with Fastmail.fm?
> Ideally, I'd like to use their proxy server,
> smtps-proxy.messagingengine.com, since my employer blocks outgoing
> smtp connections.
Are you using SSL and authentication? If not, I expect
that you'll have to. Your
Lyndon wrote:
> My preference would be for the configure script to detect it is
> being run on Solaris and fudge $PATH appropriately. That way we get
> consistent source builds on Solaris even when the person building
> doesn't have the XPG4 tools at the front of their path.
At some point, the p
>If you're using nmh 1.5, add -sasl -port 80 and
>-user to your send invocation, either at
>the whatnow prompt or in your ~/.mh_profile.
I don't know anything about fastmail.fm, but does it actually speak SMTP
on port 80?
You probably want -port 25, or -port submission (if, like you said, your
e
Ken wrote:
> I don't know anything about fastmail.fm, but does it actually speak
> SMTP on port 80?
Sure looks like it. This is through an ssh tunnel:
$ telnet localhost 80
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 mail.messagingengine.com ESMTP ready
>> I don't know anything about fastmail.fm, but does it actually speak
>> SMTP on port 80?
>
>Sure looks like it. This is through an ssh tunnel:
>
> $ telnet localhost 80
>[...]
Huh. Well, I can't speak to that ... when I try connecting to it remotely,
I get a web server on port 80.
According
Ken wrote:
> Huh. Well, I can't speak to that ... when I try connecting to it remotely,
> I get a web server on port 80.
See below, he's using a different server.
> You would want this in your .mh_profile:
>
> send: -server mail.messagingengine.com -port 587 -tls -sasl -user
> usern...@fastma
On Sun, Dec 8, 2013, at 04:10 PM, David Levine wrote:
>
> > You would want this in your .mh_profile:
> >
> > send: -server mail.messagingengine.com -port 587 -tls -sasl -user
> > usern...@fastmail.fm
>
> You'll want -server smtps-proxy.messagingengine.com instead. With
> that, you can use -po
Peter wrote:
> On Sun, Dec 8, 2013, at 04:10 PM, David Levine wrote:
> >
> > > You would want this in your .mh_profile:
> > >
> > > send: -server mail.messagingengine.com -port 587 -tls -sasl -user usernam
> e...@fastmail.fm
> >
> > You'll want -server smtps-proxy.messagingengine.com instead.
Thanks to all for the help, explanations and suggestions. I think it's
timing on on the attempt to connect to the server, which must be at
least partly due to not having the right options built in nmh. But ...
On Sun, Dec 8, 2013, at 04:59 PM, David Levine wrote:
> > If so, I guess I should just r
>mts/smtp/smtp.c:767:2: warning: 'BIO_free_all' is deprecated: first
>deprecated in OS X 10.7 [-Wdeprecated-declarations]
These warnings are benign. Is there an error here? I didn't see one.
What does build_nmh.log say? I run nmh on Mavericks, so it should compile
fine.
--Ken
On Sun, Dec 8, 2013, at 05:37 PM, Ken Hornstein wrote:
> >mts/smtp/smtp.c:767:2: warning: 'BIO_free_all' is deprecated: first
> >deprecated in OS X 10.7 [-Wdeprecated-declarations]
>
> These warnings are benign. Is there an error here? I didn't see one.
> What does build_nmh.log say? I run nm
Peter wrote:
> Looks like one of the post-build tests failed:
We of course want to figure that out, but in the mean time
you should be able to "make install" and then try to send.
David
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists
>./test/inc/test-pop: "inc -file
>/Users/peterdavis/nmh/test/testdir/inc.mbox -truncate" expected:
>[...]
That should be fixed now, if you do a "git pull".
--Ken
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listi
On Sun, Dec 08, 2013 at 05:56:26PM -0500, David Levine wrote:
> Peter wrote:
>
> > Looks like one of the post-build tests failed:
>
> We of course want to figure that out, but in the mean time
> you should be able to "make install" and then try to send.
Yes! It's working.
When I did the build,
>When I did the build, the final message just said "build failed."
>Really, it was just a verification test that failed, and that appeared
>to be due to some line truncation or something.
Other way, actually (looks like you're running on a terminal greater than
80 columns wide). I thought I had -
On Sun, Dec 8, 2013 at 6:22 PM, Ken Hornstein wrote:
> >When I did the build, the final message just said "build failed."
> >Really, it was just a verification test that failed, and that appeared
> >to be due to some line truncation or something.
>
> Other way, actually (looks like you're running
>So I guess the goal is to put everything in .mh_profile, and leave
>mts.conf alone. Is that right? If so, I guess I should just restore the
>default mts.conf. In particular, should I have mts set to smtp vs
>sendmail?
I know your problem is solved, but I wanted to explain this a bit further.
The
On Sun, Dec 8, 2013 at 9:28 PM, Ken Hornstein wrote:
> >So I guess the goal is to put everything in .mh_profile, and leave
> >mts.conf alone. Is that right? If so, I guess I should just restore the
> >default mts.conf. In particular, should I have mts set to smtp vs
> >sendmail?
>
> I know your p
26 matches
Mail list logo
