On Sun, 21 Apr 2019 18:29:57 +0100, Ralph Corderoy said:
> ISTM it's also a bug to ignore problems opening a file that exists, and
> to ignore a file given in an environment variable not existing.
I agree on the first. The second probably need to be more nuanced, and
"a *specific* file given in
Hi,
I wrote:
> Looks like a bug in nmh's Makefile; it produces mts.conf by
> re-directing the output of sed, but a umask of 077 would leave the
> file as 600.
ISTM it's also a bug to ignore problems opening a file that exists, and
to ignore a file given in an environment variable not existing.
Hi Stewart,
> /etc/nmh/mts.conf, owned by root, has mod 600.
Valdis guessed correctly in his email to the list then!
Looks like a bug in nmh's Makefile; it produces mts.conf by re-directing
the output of sed, but a umask of 077 would leave the file as 600.
> I am very grateful for your help
Clearly another great mind! See my last message. Thanks for your help.
Stewart
On Sun, April 21, 2019 9:35 am, Valdis KlÄtnieks wrote:
> On Sun, 21 Apr 2019 17:05:58 +0100, Ralph Corderoy said:
>
>> works. If so, then /etc/nmh/mts.conf's `servers' entry isn't being
>> obeyed. Either it isn't
On Sun, 21 Apr 2019 17:05:58 +0100, Ralph Corderoy said:
> works. If so, then /etc/nmh/mts.conf's `servers' entry isn't being
> obeyed. Either it isn't being read, or its getting trumped by something
> else.
I wonder if the file got installed with wrong permissions? I've seen installers
screw
Hi Stewart,
> send: -port 2525 -alias /home/wilson/.mh_aliases -server mail.eskimo.com
Yes, that would work, though only for you and not any other users.
> You proposed that mts.conf was not being read. Could that still be
> the case?
Yes, and it would mean other mts.conf settings you've
Ah, great minds do settle into the same groove. :)) as you must have
noted from my last message.
env | grep MTS returns nothing, under either wilson or root.
Oh oh, I'm embarrassed. /etc/nmh/mts.conf, owned by root, has mod 600.
I changed it to 644, and removed the -server option from the send
Dear Ralph,
I tried the optioned send, each time leaving out one of the options.
It only failed when I left out -server mail.eskimo.com
So, hoping to be lucky, I added that option to .mh_profile, thus:
mhparam send: -port 2525 -alias /home/wilson/.mh_aliases -server
mail.eskimo.com
Now send
Hi Stewart,
> I did your optioned send below, except I used -port 2525 and it went!
...
> What now? send -snoop -mts smtp -server mail.eskimo.com -port 2525
> Trying to connect to "mail.eskimo.com" ...
> Connecting to 204.122.16.4:2525...
> <= 220 mail.eskimo.com ESMTP Postfix
> <= 250-AUTH PLAIN
Ralph,
In 2010 I had a problem sending and now remember that it was solved
by moving from port 25 to port 2525, due to some policy of Verizon's
that made it not work on 25. I think the mail interaction is in
the nmh archives.
It seems that the present problem has two parts:
1) Sending to port
Ralph,
Here's the result of
send -snoop -mts smtp -server mail.eskimo.com -port 25
Trying to connect to "mail.eskimo.com" ...
Connecting to 204.122.16.4:25...
Connection failed: Connection timed out
post: problem initializing server; [BHST] Connection to "mail.eskimo.com"
failed: Connection
Ralph,
New data!
I did your optioned send below, except I used -port 2525 and
it went!
> send -snoop -mts smtp -server mail.eskimo.com -port 2525
I sent to myself and it came around.
So what is the difference between send with no options -- which
still doesn't work, and send optioned as
Hi Stewart,
> This week I installed nmh 1.7.1.
Do you know what version you were on before? Was it a 1.6?
> Trying to connect to "localhost" ...
> Connecting to ::1:2525...
> Connection failed: Connection refused
> Connecting to 127.0.0.1:2525...
Hi Stewart,
> The previous nmh was 1.4
That's a big jump. If you haven't already seen it, then the list of
per-release changes in NEWS could be useful.
http://git.savannah.nongnu.org/cgit/nmh.git/tree/NEWS
> I changed the port to 25 from 2525, but the connection there was also
> refused. I
Ralph,
The previous nmh was 1.4
I changed the port to 25 from 2525, but the connection there was also
refused. I left it at 25. mhparam now shows:
-port 25 -alias /home/wilson/.mh_aliases
Sendmail is installed, but according to ps it is not running.
Postfix, Qmail, and Exim are not installed.
Ralph,
The previous nmh was 1.4
I changed the port to 25 from 2525, but the connection there was also
refused. I left it at 25. mhparam now shows:
-port 25 -alias /home/wilson/.mh_aliases
Sendmail is installed, but according to ps it is not running.
Postfix, Qmail, and Exim are not installed.
Hi Stewart,
> Would you kindly send it again if you can?
...
> https://lists.nongnu.org/mailman/listinfo/nmh-workers
There's a copy in the archive of mailing-list emails:
http://lists.nongnu.org/archive/html/nmh-workers/2019-04/msg2.html
--
Cheers, Ralph.
--
nmh-workers
Ralph,
Thank you so much for answering my question about send failing.
Would you kindly send it again if you can? It came through
procmail to the "possible spam" list and, too quick, I erased it
by mistake. I added your name to the white list.
Best wishes and Happy Easter!
Stewart Wilson
--
Hi Stewart,
> This week I installed nmh 1.7.1.
Do you know what version you were on before? Was it a 1.6?
> Trying to connect to "localhost" ...
> Connecting to ::1:2525...
> Connection failed: Connection refused
> Connecting to 127.0.0.1:2525...
Hi, I've used nmh for years and love it. But I'm not an expert on its
internals. This week I installed nmh 1.7.1. It's apparently working
fine except that send fails with the message:
What now? send -snoop
Trying to connect to "localhost" ...
Connecting to ::1:2525...
20 matches
Mail list logo