Re: [nmh-workers] Reply to Ralph Corderoy
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 the environment". Consider how *PATH variables work, and it's possible that none of the directories contain the file in question and it's still OK. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 (may hope to have it again). No problem; always happy to help a colonial. :-) -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 being read, or its getting trumped by >> something else. > > I wonder if the file got installed with wrong permissions? I've seen > installers screw the pooch because root's default umask was 077, and I'm > insufficiently caffeinated to suss out what nmh does. > > This works for me: > > > 12:24:12 0 [~] ls -l /usr/local/etc/nmh/mts.conf > -rw-r--r--. 1 root root 1778 Feb 13 14:52 /usr/local/etc/nmh/mts.conf > 12:24:15 0 [~] egrep -v '^$|^#' /usr/local/etc/nmh/mts.conf > mts: smtp > mmdfldir: /var/mail > mmdflfil: > servers: localhost > 12:24:36 0 [~] grep send .mh_profile > send: -nomime -msgid -server smtp.gmail.com -port 587 -tls -sasl -user > val...@vt.edu > > (I never added the proper server name to mts.conf because it was bouncing > all over the place, partly due to hysterical raisins, while my employer > was first drinking the Google kook-aid.) > > -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 the pooch because root's default umask was 077, and I'm insufficiently caffeinated to suss out what nmh does. This works for me: 12:24:12 0 [~] ls -l /usr/local/etc/nmh/mts.conf -rw-r--r--. 1 root root 1778 Feb 13 14:52 /usr/local/etc/nmh/mts.conf 12:24:15 0 [~] egrep -v '^$|^#' /usr/local/etc/nmh/mts.conf mts: smtp mmdfldir: /var/mail mmdflfil: servers: localhost 12:24:36 0 [~] grep send .mh_profile send: -nomime -msgid -server smtp.gmail.com -port 587 -tls -sasl -user val...@vt.edu (I never added the proper server name to mts.conf because it was bouncing all over the place, partly due to hysterical raisins, while my employer was first drinking the Google kook-aid.) -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] send fails
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 altered may also be being missed. Did that env(1) pipeline I suggest give any output? Are you running Linux? It provides some programs I know that might help diagnose the problem. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 line in .mh_profile-and send works. My mistake basically was after originally editing mts.conf as su I didn't change the permissions so wilson could read it. Please forgive me for overlooking that. I am very grateful for your help (may hope to have it again). Stewart On Sun, April 21, 2019 9:05 am, Ralph Corderoy wrote: > 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 LOGIN >> <= 250-AUTH=PLAIN LOGIN >> > ... > >> <= 250 2.0.0 Ok: queued as 2ECD314461D >> > > Great. So you need to edit your ~/.mh_profile to change send's -port > back to 2525, as it was when you started. You mentioned Verizon being a > problem in the past, and it looks like it still it, blocking your port 25 > connection to Eskimo. https://www.eskimo.com/support/mail/mail-settings/ > says they support 2525 to workaround this. > > > Once you've done that, you should find a plain > > > send -snoop > > fails because it tries to connect to localhost's port 2525, but a > > send -snoop -server mail.eskimo.com > > 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. > > Does `env | grep MTS' show anything? There are two environment > variables, MHMTSCONF and MHMTSUSERCONF, that can alter whence the mts.conf > settings are gathered. > > -- > Cheers, Ralph. > > -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] send fails
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 -snoop gives Trying to connect to "mail.eskimo.com" ... Connecting to 204.122.16.4:2525... <= 220 mail.eskimo.com ESMTP Postfix => EHLO localhost <= 250-mail.eskimo.com <= 250-PIPELINING <= 250-SIZE 5000 <= 250-ETRN <= 250-STARTTLS <= 250-AUTH PLAIN LOGIN <= 250-AUTH=PLAIN LOGIN <= 250-ENHANCEDSTATUSCODES <= 250-8BITMIME <= 250 DSN => MAIL FROM: <= 250 2.1.0 Ok => RCPT TO: <= 250 2.1.5 Ok => DATA <= 354 End data with . => . <= 250 2.0.0 Ok: queued as 51F00140894 => QUIT <= 221 2.0.0 Bye sw% This is called a successful hack. But what is really going on? You proposed that mts.conf was not being read. Could that still be the case? Stewart -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 LOGIN > <= 250-AUTH=PLAIN LOGIN ... > <= 250 2.0.0 Ok: queued as 2ECD314461D Great. So you need to edit your ~/.mh_profile to change send's -port back to 2525, as it was when you started. You mentioned Verizon being a problem in the past, and it looks like it still it, blocking your port 25 connection to Eskimo. https://www.eskimo.com/support/mail/mail-settings/ says they support 2525 to workaround this. Once you've done that, you should find a plain send -snoop fails because it tries to connect to localhost's port 2525, but a send -snoop -server mail.eskimo.com 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. Does `env | grep MTS' show anything? There are two environment variables, MHMTSCONF and MHMTSUSERCONF, that can alter whence the mts.conf settings are gathered. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] send fails
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 25 --- wrong, should be 2525 2) Something else, which accounts for the difference between plain send -snoop and send -snoop -mts smtp -server mail.eskimo.com -port 2525 Thanks again for your help. I see you are in England. Best, Stewart -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] send fails
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 timed out send: message not delivered to anyone > Was it the same directory that `mhparam etcdir' shows? Yes, /etc/nmh. But I edited it as shown in the mts.conf that I attached in the last message. Sorry I'm so slow. Now I'm just writing and replying on Eskimo's site. Also, nmh is great but very complicated. Lisp is much easier!! :) Looks like we are getting farther though, re the above error message. Please tell me your interpretation. Best, Stewart On Sun, April 21, 2019 7:35 am, Ralph Corderoy wrote: > 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 left it at 25. mhparam now shows: -port 25 -alias >> /home/wilson/.mh_aliases >> > >> I'm attaching mts.conf. >> > > Where did you find that? > Was it the same directory that `mhparam etcdir' shows? > > >> mts: smtp >> > ... > >> servers: mail.eskimo.com >> > > That suggests to me that nmh will try to talk SMTP to mail.eskimo.com to > send the email, > >> Also .mh_profile >> > ... > >> send: -port 25 -alias /home/wilson/.mh_aliases >> > > and that it will connect on port 25, the standard SMTP port. I can > connect from here. > > $ nc mail.eskimo.com 25 > 220 mail.eskimo.com ESMTP Postfix > quit 221 2.0.0 Bye > ^D > $ > > > But your original email to the list showed attempts to connect to > localhost. > > What now? send -snoop > > > Trying to connect to "localhost" ... > Connecting to ::1:2525... > Connection failed: Connection refused > Connecting to 127.0.0.1:2525... > Connection failed: Connection refused > > > so I'm thinking mts.conf isn't being found. > > At the `What now?' prompt, try > > > send -snoop -mts smtp -server mail.eskimo.com -port 25 > > and we'll see if that gets further. > > -- > Cheers, Ralph. > > -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 above??? Cheers, Stewart P.S. here is the trace from the optioned send: 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 => EHLO localhost <= 250-mail.eskimo.com <= 250-PIPELINING <= 250-SIZE 5000 <= 250-ETRN <= 250-STARTTLS <= 250-AUTH PLAIN LOGIN <= 250-AUTH=PLAIN LOGIN <= 250-ENHANCEDSTATUSCODES <= 250-8BITMIME <= 250 DSN => MAIL FROM: <= 250 2.1.0 Ok => RCPT TO: <= 250 2.1.5 Ok => DATA <= 354 End data with . => . <= 250 2.0.0 Ok: queued as 2ECD314461D => QUIT <= 221 2.0.0 Bye sw% On Sun, April 21, 2019 7:35 am, Ralph Corderoy wrote: > 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 left it at 25. mhparam now shows: -port 25 -alias >> /home/wilson/.mh_aliases >> > >> I'm attaching mts.conf. >> > > Where did you find that? > Was it the same directory that `mhparam etcdir' shows? > > >> mts: smtp >> > ... > >> servers: mail.eskimo.com >> > > That suggests to me that nmh will try to talk SMTP to mail.eskimo.com to > send the email, > >> Also .mh_profile >> > ... > >> send: -port 25 -alias /home/wilson/.mh_aliases >> > > and that it will connect on port 25, the standard SMTP port. I can > connect from here. > > $ nc mail.eskimo.com 25 > 220 mail.eskimo.com ESMTP Postfix > quit 221 2.0.0 Bye > ^D > $ > > > But your original email to the list showed attempts to connect to > localhost. > > What now? send -snoop > > > Trying to connect to "localhost" ... > Connecting to ::1:2525... > Connection failed: Connection refused > Connecting to 127.0.0.1:2525... > Connection failed: Connection refused > > > so I'm thinking mts.conf isn't being found. > > At the `What now?' prompt, try > > > send -snoop -mts smtp -server mail.eskimo.com -port 25 > > and we'll see if that gets further. > > -- > Cheers, Ralph. > > -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] [nmh-workders] send fails
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... > Connection failed: Connection refused That means there is no program listening on port 2525 to accept the mail from nmh to start its journey. Do you have a local mail server, like Sendmail, Postfix, Qmail, or Exim, that you expect to be used? 2525 is an odd port; it's normally 25 or 587. 2525 suggests you're trying to work around some network-traffic filtering of port 25, or your server doesn't have the privilege to listen on port 25. See if you've any parameters being given to send(1) by your ~/.mh_profile with `mhparam send'. And examine your system's /etc/nmh/mts.conf; that's the default mts.conf file unless you override it with send's -mts option. > but suggested for anything else I go to nmh-workers. Yes, good idea. Keep replying to the list, and we'll keep CCing you in our replies. -- Cheers, Ralph. 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. I'm attaching mts.conf. Also .mh_profile Thank you again for your help! Stewart P.S. Sorry if I am not responding correctly. You said reply to the list and I think I'm doing that. :) Sending is complicated since send doesn't work and this is from Eskimo. .mh_profile Description: Binary data # nmh mail transport interface customization file. # # Check the mh-tailor(5) man page for descriptions of available options. # # The delivery method to use, which must be one of the following: # smtp: nmh opens a socket connection to the appropriate port #on the servers listed below and speaks SMTP to the #first one that responds. This is the default. # sendmail/smtp: nmh pipes messages directly to the sendmail program, #speaking SMTP. Can be abbreviated to "sendmail". # sendmail/pipe: nmh pipes messages directly to the sendmail program, #using the -t option so that addresses are retrieved #from the message. mts: smtp # Name that nmh considers `local'. If not set, nmh will # query the system for this value (gethostname, etc...). localname: prediction-dynamics.com # Default location of mail drops. If this option is # set, but empty, the user's home directory is used. mmdfldir: /var/mail # The name of the maildrop file in the directory where maildrops # are kept. If this is empty, the user's login name is used. mmdflfil: # # The locking algorithm to use on the spool file. Valid settings are: # # fcntl Locking using the fcntl() function # dot "Dot" locking using an external lock file # flock Locking using the flock() function (if supported by OS) # lockf Locking using the lockf() function (if supported by OS) # # Locking algorithms supported on this installation are: # # fcntl dot flock lockf # # The default spool locking configured on this system is fcntl; # change the line below to get a different value spoollocking: fcntl # Hardcoded POP server name (prevents inc'ing from local mail spool). #pophost: localhost # A SINGLE SMTP server to use when using SMTP support servers: mail.eskimo.com-- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] Reply to Ralph Corderoy
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 left it at 25. mhparam now shows: > -port 25 -alias /home/wilson/.mh_aliases > I'm attaching mts.conf. Where did you find that? Was it the same directory that `mhparam etcdir' shows? > mts: smtp ... > servers: mail.eskimo.com That suggests to me that nmh will try to talk SMTP to mail.eskimo.com to send the email, > Also .mh_profile ... > send: -port 25 -alias /home/wilson/.mh_aliases and that it will connect on port 25, the standard SMTP port. I can connect from here. $ nc mail.eskimo.com 25 220 mail.eskimo.com ESMTP Postfix quit 221 2.0.0 Bye ^D $ But your original email to the list showed attempts to connect to localhost. What now? send -snoop Trying to connect to "localhost" ... Connecting to ::1:2525... Connection failed: Connection refused Connecting to 127.0.0.1:2525... Connection failed: Connection refused so I'm thinking mts.conf isn't being found. At the `What now?' prompt, try send -snoop -mts smtp -server mail.eskimo.com -port 25 and we'll see if that gets further. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] Send fails
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. I'm attaching mts.conf. Also .mh_profile Thank you again for your help! Stewart P.S. Sorry if I am not responding correctly. You said reply to the list and I think I'm doing that. :) Sending is complicated since send doesn't work and this is from Eskimo. .mh_profile Description: Binary data # nmh mail transport interface customization file. # # Check the mh-tailor(5) man page for descriptions of available options. # # The delivery method to use, which must be one of the following: # smtp: nmh opens a socket connection to the appropriate port #on the servers listed below and speaks SMTP to the #first one that responds. This is the default. # sendmail/smtp: nmh pipes messages directly to the sendmail program, #speaking SMTP. Can be abbreviated to "sendmail". # sendmail/pipe: nmh pipes messages directly to the sendmail program, #using the -t option so that addresses are retrieved #from the message. mts: smtp # Name that nmh considers `local'. If not set, nmh will # query the system for this value (gethostname, etc...). localname: prediction-dynamics.com # Default location of mail drops. If this option is # set, but empty, the user's home directory is used. mmdfldir: /var/mail # The name of the maildrop file in the directory where maildrops # are kept. If this is empty, the user's login name is used. mmdflfil: # # The locking algorithm to use on the spool file. Valid settings are: # # fcntl Locking using the fcntl() function # dot "Dot" locking using an external lock file # flock Locking using the flock() function (if supported by OS) # lockf Locking using the lockf() function (if supported by OS) # # Locking algorithms supported on this installation are: # # fcntl dot flock lockf # # The default spool locking configured on this system is fcntl; # change the line below to get a different value spoollocking: fcntl # Hardcoded POP server name (prevents inc'ing from local mail spool). #pophost: localhost # A SINGLE SMTP server to use when using SMTP support servers: mail.eskimo.com-- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] Reply to Ralph Corderoy
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. I'm attaching mts.conf. Also .mh_profile Thank you again for your help! Stewart # nmh mail transport interface customization file. # # Check the mh-tailor(5) man page for descriptions of available options. # # The delivery method to use, which must be one of the following: # smtp: nmh opens a socket connection to the appropriate port #on the servers listed below and speaks SMTP to the #first one that responds. This is the default. # sendmail/smtp: nmh pipes messages directly to the sendmail program, #speaking SMTP. Can be abbreviated to "sendmail". # sendmail/pipe: nmh pipes messages directly to the sendmail program, #using the -t option so that addresses are retrieved #from the message. mts: smtp # Name that nmh considers `local'. If not set, nmh will # query the system for this value (gethostname, etc...). localname: prediction-dynamics.com # Default location of mail drops. If this option is # set, but empty, the user's home directory is used. mmdfldir: /var/mail # The name of the maildrop file in the directory where maildrops # are kept. If this is empty, the user's login name is used. mmdflfil: # # The locking algorithm to use on the spool file. Valid settings are: # # fcntl Locking using the fcntl() function # dot "Dot" locking using an external lock file # flock Locking using the flock() function (if supported by OS) # lockf Locking using the lockf() function (if supported by OS) # # Locking algorithms supported on this installation are: # # fcntl dot flock lockf # # The default spool locking configured on this system is fcntl; # change the line below to get a different value spoollocking: fcntl # Hardcoded POP server name (prevents inc'ing from local mail spool). #pophost: localhost # A SINGLE SMTP server to use when using SMTP support servers: mail.eskimo.com .mh_profile Description: Binary data -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] send fails
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 https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] Ralph Corderoy I missed your message!!
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 -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] send fails
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... > Connection failed: Connection refused That means there is no program listening on port 2525 to accept the mail from nmh to start its journey. Do you have a local mail server, like Sendmail, Postfix, Qmail, or Exim, that you expect to be used? 2525 is an odd port; it's normally 25 or 587. 2525 suggests you're trying to work around some network-traffic filtering of port 25, or your server doesn't have the privilege to listen on port 25. See if you've any parameters being given to send(1) by your ~/.mh_profile with `mhparam send'. And examine your system's /etc/nmh/mts.conf; that's the default mts.conf file unless you override it with send's -mts option. > but suggested for anything else I go to nmh-workers. Yes, good idea. Keep replying to the list, and we'll keep CCing you in our replies. -- Cheers, Ralph. -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] send fails
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... Connection failed: Connection refused Connecting to 127.0.0.1:2525... Connection failed: Connection refused post: problem initializing server; [BHST] no servers available (use -snoop for details send: message not delivered to anyone Would someone please help me? I'd be happy to send copies of various dot files, etc. I talked to Kenh about earlier problems. He helped me a lot, but suggested for anything else I go to nmh-workers. Thanks for any ideas. Stewart Wilson wil...@eskimo.com prediction-dynamics.com -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
