> Hi Cyber,
>
> Do you know your email to the list had three `from' headers?
>
> From: =3D?UTF-8?B?zrs=3D?=3D
> From: Ruben de Bruin
> From: Cyber
>
Yes I had already seen that. It was an accident. Sorry.
> I can tell it meant a lot of list subscribers didn't receive your email
>
Hi Cyber,
Do you know your email to the list had three `from' headers?
From: =?UTF-8?B?zrs=?=
From: Ruben de Bruin
From: Cyber
I can tell it meant a lot of list subscribers didn't receive your email
due to rejections pointing at RFC 5322.
--
Cheers, Ralph.
Hi Norm,
> The same. But I assumed that the message had more content that I'm not
> smart enough to access. I also tried mhshow and mhlist.
No, it's not there. You're seeing everything.
Ask your correspondent if they know they sent an `empty' email.
--
Cheers, Ralph.
David Levine writes:
>> What worked for me just making your message the current message
>> and then typing
>> mhstore
>>
>> When I did that nmh automatically saved part 1 and 2 in the
>> current directory and part 2 (which you care about) in my inbox.
>
>Just using "show" on the message works for
> What worked for me just making your message the current message
> and then typing
> mhstore
>
> When I did that nmh automatically saved part 1 and 2 in the
> current directory and part 2 (which you care about) in my inbox.
Just using "show" on the message works for me. What does it
produce for
What worked for me just making your message the current message
and then typing
mhstore
When I did that nmh automatically saved part 1 and 2 in the
current directory and part 2 (which you care about) in my inbox.
> --- =_aa0
> Content-Type: text/plain; charset="us-ascii"
>
Ralph wrote:
> I was listing `the email you've attached'. :-)
Oh, yes :-] I get the same output from mhlist as you on that email.
> I took that as being Norm's outgoing email, that we didn't see, and the
> correspondent replied, quoting Norm, but added nothing other than the
> top-posting
Hi David,
> > The email you've attached has little in it.
...
> > 8711 multipart/alternative 2616
> > 1 text/html 1118
> > 2 text/plain 451
>
> Odd, I get:
...
> 4681 multipart/mixed 9200
> 1
Ralph wrote:
> The email you've attached has little in it.
>
> $ mhlist -nov
> msg part type/subtype size description
> 8711 multipart/alternative 2616
> 1 text/html 1118
> 2 text/plain 451
> $
Hi Norm,
> Would some kind soul please tell me how to read the attached.
The email you've attached has little in it.
$ mhlist -nov
msg part type/subtype size description
8711 multipart/alternative 2616
1 text/html 1118
2
hymie wrote:
> But it seems like there is something I'm missing, that will enable
> mhshow to say "Oh, base64 and pgp-encrypted. I should use the
> 'gpg2 -d %F | less' command to show this part"
Here are some pieces, in addition to gpg-agent, that might help:
1) I think you're looking for this
>> normally for encrypted email you'd need to enter in your password to
>> unlock your private key and we don't really have a good mechanism for
>> that currently.
>
>There's a gpg-agent(1); it's kicked off as needed by gpg(1) these days
>AIUI. I've not used it, but I assume it works similarly
Hi Ken,
> normally for encrypted email you'd need to enter in your password to
> unlock your private key and we don't really have a good mechanism for
> that currently.
There's a gpg-agent(1); it's kicked off as needed by gpg(1) these days
AIUI. I've not used it, but I assume it works
Norm wrote:
> David Levine writes:
> >
> >> I wonder if, for 1.7, that simple syntax and semantics could be guaranteed?
> >> That way, it would be possible for *proc commands to be always uptodate.
> >
> >I'm not sure how. For example, if a new switch is added, its mere
>
David Levine writes:
>Norm wrote:
>
>> I observe that, ignoring all lines not beginning with exactly two ' '
>> characters, the outputs of nmh's commands' -help, seem to be extremely
>> regular and simple.
>
>Yes, because they're generated from the switch definitions in the code
Norm wrote:
> I observe that, ignoring all lines not beginning with exactly two ' '
> characters, the outputs of nmh's commands' -help, seem to be extremely
> regular and simple.
Yes, because they're generated from the switch definitions in the code
of each program.
> I wonder if, for 1.7, that
>But I would like to humbly suggest a new man page, something like nmh-advice.
>It would contain a lot of advice which, right now is scattered over
>hundreds of Emails. It would, over the years, grow gradually. It
>would it be preferable to burdening already burdened existing
>man pages.
I hear
Hi Norm,
> Why did I ignore your advice? I don't remember. But I would conjecture
> that it was some combination of not understanding the advice, not
> understanding its context, or not believing that its context was
> relevant to me.
If it's like me with most of the "do this for the new
Ken Hornstein writes:
>>I don't have a distcomps in my nmh directory (~/Mail). So I'm getting the
>>default. Should I have a ~/Mail/distcomps ? If so what should it be.
>
>I've tried in the past to gently suggest to everyone that setting
Yes, you have; going back to at least
>I don't have a distcomps in my nmh directory (~/Mail). So I'm getting the
>default. Should I have a ~/Mail/distcomps ? If so what should it be.
I've tried in the past to gently suggest to everyone that setting
Local-Mailbox in your .mh_profile is vastly preferrable to modifying
individual
Hi Norm,
> I don't have a distcomps in my nmh directory (~/Mail). So I'm getting
> the default. Should I have a ~/Mail/distcomps ? If so what should it
> be.
As Ken implied in replying to me, Local-Mailbox in mh_profile(5) is
another option.
--
Cheers, Ralph.
Ralph Corderoy writes:
>Hi Norm,
>
>Ken wrote:
>> But I am wondering if perhaps the problem is this:
>>
>> >=> MAIL FROM:
>
>I suspect it is. dist(1) gets this "wrong" for me here, too.
>
>$ fmttest -raw -forma '%(localmbox)' ''
>Ralph Corderoy
>I suspect it is. dist(1) gets this "wrong" for me here, too.
>
>$ fmttest -raw -forma '%(localmbox)' ''
>Ralph Corderoy
Well, isn't that kind of your fault? :-) Single line setting in your
.mh_profile.
--Ken
___
Ken Hornstein writes:
>>When I do a dist, the message goes to a /dev/null somewhere. I don't
>>know if the problem is with my MH setup or somewhere else. Here is one
>>attempt to use dist:
>>[...]
>>Ken Hornstein never Emailed me. So he likely never got the Email. Nor
>>did
Hi Norm,
Ken wrote:
> But I am wondering if perhaps the problem is this:
>
> >=> MAIL FROM:
I suspect it is. dist(1) gets this "wrong" for me here, too.
$ fmttest -raw -forma '%(localmbox)' ''
Ralph Corderoy
$
--
Cheers, Ralph.
>When I do a dist, the message goes to a /dev/null somewhere. I don't
>know if the problem is with my MH setup or somewhere else. Here is one
>attempt to use dist:
>[...]
>Ken Hornstein never Emailed me. So he likely never got the Email. Nor
>did several others to whom I have tried to dist.
Norm wrote:
> When I do a dist, the message goes to a /dev/null somewhere. I don't know
> if the problem is with my MH setup or somewhere else.
I don't see why the message wouldn't have been delivered. The -snoop
output shows that your STMP server accepted it.
> Ken Hornstein never Emailed me.
>X-Authentication-Warning: shell1.rawbw.com: Host m206-54.dsl.tsoft.com
>[198.144.206.54] claimed to be nad.dad.org
I am personally skeptical that email providers really notice this line.
But hey, maybe they do.
>Usually, this does not cause a problem. But some recipients reject my
>Email. I
David Levine levin...@acm.org writes:
Norm wrote:
Now I am getting an infinite stream of messages like the attached.
How do I stop the stream. This happened to me once before.
Stop postfix?
http://lists.gnu.org/archive/html/nmh-workers/2013-02/msg00022.html
Would Fcc: instead of cc: norm
Ken Hornstein k...@pobox.com writes:
I will note preSend contains a bunch of NUL characters on the last line;
we probably do poorly with that (and are not valid in email).
In the unlikely event that anybody cares, the nuls were inserted by a bug in
norms-cool-editor. The bug was exercised by a
I am having a problem with one one particular correspondent. When I reply
to his messages, the beginning of the body of my messages is snipped off.
As an example, I am attaching:
[...]
preSend: My draft before I sent it.
afterSend: What get sent
These two ... do not seem to line
Ken Hornstein k...@pobox.com writes:
I am having a problem with one one particular correspondent. When I reply
to his messages, the beginning of the body of my messages is snipped off.
As an example, I am attaching:
[...]
preSend: My draft before I sent it.
afterSend: What get sent
(tls-decrypted) = 250-AUTH GSSAPI NTLM LOGIN
Do you want to use GSSAPI (really Kerberos), NTLM, or LOGIN?
Presumably you'd know if you were doing Kerberos; if you are using
Kerberos, you'd be running kinit and _not_ be putting a password in your
.netrc. That's failing because you don't have
Ken Hornstein k...@pobox.com wrote:
(tls-decrypted) = 250-AUTH GSSAPI NTLM LOGIN
Do you want to use GSSAPI (really Kerberos), NTLM, or LOGIN?
Presumably you'd know if you were doing Kerberos; if you are using
Kerberos, you'd be running kinit and _not_ be putting a password in your
That description would be a welcome addition to the currently terse
reference to -saslmech in the manual.
It's hard to balance the desire to provide a reasonably concise but
complete description of the options supported by send(1) to explaining
exactly how SASL negotiation works. In a normal
If you're trying to do LOGIN (which I suspect is most likely), then the
problem is that the cyrus-sasl library is picking out the mechanism to
use based on what the server is saying it prefers, which is (in order of
most preferred to least preferred) GSSAPI, then NTLM, then LOGIN.
No, the
That description would be a welcome addition to the currently terse
reference to -saslmech in the manual.
exactly how SASL negotiation works. In a normal world, you don't need
-saslmech (normally you only have one mechanism you care about) it but
The behaviour here has nothing to do with
No, the SASL mechanisms listed in the AUTH keyword in the EHLO response
are unordered.
You know, I could have sworn that the server mechanism list was ordered
from most preferred to least preferred ... but there's no standards document
that says that, is there? I stand corrected.
The choice of
Now I'm confused, befuddled, intimidated and overwhelmed.
So let me ask two, I hope, simple questions.
Is it reasonably safe for me to put characters (octets) greater than 127 in the
body, excluding any attachments, of a message?
If so, what encodings is it reasonably safe for me to use for
mhstore and mhlist have markedly improved the quality of my life.
I had seen references to mhstore over the years. But the notion that it had
to do with forwarding Email had somehow gotten into my head. So I never
explored it further.
Thank you all very much.
Norman Shapiro
You want mhstore, mentioned in the See Also of mhshow
mhstore (1) - store contents of MIME messages into files
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Jerrad Pierce belg4...@pthbb.org writes:
You want mhstore, mentioned in the See Also of mhshow
mhstore (1) - store contents of MIME messages into files
That's EXACTLY what I need. Thank you very much.
Norman Shapiro
798 Barron Avenue
Palo Alto CA 94306-3109
(650)
Norm wrote:
When try to run mhshow on it, it produces nothing useful
-- it doesn't even run unzip. I'm guessing that I ought to
have a configuration file somewhere, maybe
.../nmh/etc/mailcap, that tells nmh about zip files.
Just to note that you probably don't need any special
configuration.
David Levine levin...@acm.org writes:
Norm wrote:
When try to run mhshow on it, it produces nothing useful
-- it doesn't even run unzip. I'm guessing that I ought to
have a configuration file somewhere, maybe
.../nmh/etc/mailcap, that tells nmh about zip files.
Just to note that you probably
Hi Norm,
The Email you analyzied was not sent from the computer suffering the
bouncing problem.
But this Email will be so sent.
Do you have trouble following the Received headers, bottom to top? :-)
Received: from jad.dad.org (unknown [198.144.207.170])
by mailwash26.pair.com
Ralph Corderoy ra...@inputplus.co.uk writes:
Hi Norm,
The Email you analyzied was not sent from the computer suffering the
bouncing problem.
But this Email will be so sent.
Do you have trouble following the Received headers, bottom to top? :-)
Received: from jad.dad.org (unknown
Hi Norm,
It is:
servers: localhost
Exactly! You are running an SMTP server on localhost, that machine, and
it's Postfix. I am here, Ubuntu. Try this:
$ sudo lsof -i :25
COMMAND PIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME
master 1319root 12u IPv4 8455
Hi David,
You wrote off-list in a plane:
change your servers: localhost line in mts.conf to servers:
smtp.tsoft.net (without quotes). If they require authentication,
you'll find out when you try to send.
That alone is probably insufficient since Norm had that in the past and
found that
Ralph Corderoy ra...@inputplus.co.uk writes:
Hi David,
You wrote off-list in a plane:
change your servers: localhost line in mts.conf to servers:
smtp.tsoft.net (without quotes). If they require authentication,
you'll find out whenyou try to send.
That alone is probably insufficient since
I am trying the mst.conf change. But the test may take few days to complete,
because the problematic addressee is traveling, and hence slow to Email
respond.
I think you'd know right away if you get a bounce.
When you asked about this in February, the way we left things was:
- You'll set
Ken Hornstein k...@pobox.com writes:
So for this bounced email, was the email sent to localhost or your ISP?
My ISP.
Then to me that sounds like your ISP's problem. You could look at the
headers of your bounce message and see which host it's complaining about.
Well, maybe you could 'look at
Norm wrote:
Well, maybe you could 'look at the headers... and see which
host..,', but I can't. So I'm forwarding a typical bounce, in the
hope that you'll do it.
--- Forwarded Message
Date: Wed, 23 May 2012 05:50:36 -0700 (PDT)
From: mailer-dae...@jad.dad.org (Mail Delivery System)
Hi David,
Date: Wed, 23 May 2012 05:50:36 -0700 (PDT)
From: mailer-dae...@jad.dad.org (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: n...@dad.org
Message-Id: 20120523125036.e2663124...@jad.dad.org
This is the mail system at host jad.dad.org.
That bounce
Ralph wrote:
Is his local SMTP server on jad not involved with passing it onto
his ISP's smarthost then?
I don't think so, based on my possibly faded recollection
of the earlier discussion.
I read it as the other party, mail.eipye.com, rejected it
when jad tried to hand it over so the
On Wed, 23 May 2012 10:50:11 -0700, n...@dad.org said:
After I sent the attached Email, last February, Ken Hornstein solved the
dilemma it posed by telling me about the -server localhost option to send.
Until a few weeks ago, everything was fine. Then I started getting the same:
Received:
Ken Hornstein k...@pobox.com writes:
Well, maybe you could 'look at the headers... and see which host..,', but I
can't. So I'm forwarding a typical bounce, in the hope that you'll do it.
As others have mentioned ... you're submitting your email to the localhost
MTA, instead of your ISP smarthost.
Hi Ken,
That's what I do now. I only use 'send -server localhost', for
messages addressed to plain 'norm' and nobody else. If I
inadvertently attempt to use plain 'send' to send a message
addressed to plain 'norm', I get an error message. All this had
worked well, from February, sending
After I sent the attached Email, last February, Ken Hornstein solved the
dilemma it posed by telling me about the -server localhost option to send.
Until a few weeks ago, everything was fine. Then I started getting the same:
mar...@eipye.com: host mail.eipye.com[64.14.74.17] said: 421
Ken Hornstein k...@pobox.com writes:
After I sent the attached Email, last February, Ken Hornstein solved the
dilemma it posed by telling me about the -server localhost option to send.
Until a few weeks ago, everything was fine. Then I started getting the same:
mar...@eipye.com: host
So for this bounced email, was the email sent to localhost or your ISP?
My ISP.
Then to me that sounds like your ISP's problem. You could look at the
headers of your bounce message and see which host it's complaining about.
--Ken
___
Nmh-workers
Norm wrote:
Ken Hornstein k...@pobox.com writes:
So for this bounced email, was the email sent to localhost or your ISP?
My ISP.
I'd verify that by adding -snoop to your send command.
David
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
61 matches
Mail list logo