"Host part" is pseudo, it's after the @ and can include most
ASCII printable characters.
Just read, say, 64 bytes from /dev/random and base64 encode it.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-
David Levine writes:
> I've been thinking more about Message-IDs. The way nmh,
> sendmail, and Fedora configure things by default, the host
> part is worthless, but I expect that's common in these
> halcyon days of NAT.
Agreed ... that's a problem ... but
> So I'm thinking of generating a Messa
I've been thinking more about Message-IDs. The way nmh,
sendmail, and Fedora configure things by default, the host
part is worthless, but I expect that's common in these
halcyon days of NAT. And on some hosts, I want the real
hostname to be masked, esp. when using a masqueraded From:
address. (I
Ken Hornstein writes:
Your draft file does not contain a From: header; this version of nmh
requires that all draft messages contain one. See the default
component templates for examples and insure that your draft contains
a valid From: header.
s/insure/ensure/
Insurance ensures you will recei
Ken Hornstein writes:
>Your draft file does not contain a From: header; this version of nmh
>requires that all draft messages contain one. See the default
>component templates for examples and insure that your draft contains
>a valid From: header.
s/insure/ensure/
Tet
>Well, I agree that it's long, but this isn't a transient error, it's an
>upgrade issue and that's a place where at least one person (me) doesn't
>expect things to break. So giving explicit instructions seems OK to me
>even if they're long.
Fair enough. Although technically the issue is more wit
Ken Hornstein writes:
> >A more user-friendly diagnostic might be:
> >
> > Your components files are not compatible with this version of nmh.
> > You have modified them so we were unable to automatically update them.
> > You need to go to /etc/nmh and merge in the changes to the compone
>A more user-friendly diagnostic might be:
>
> Your components files are not compatible with this version of nmh.
> You have modified them so we were unable to automatically update them.
> You need to go to /etc/nmh and merge in the changes to the components,
> forwcomps, re
Ken Hornstein writes:
> >I have a slightly modified version that removes the default Fcc stuff that
> >was
> >added some time ago and drives me crazy as I don't want that.
>
> So, yeah, that's the reason. I don't think there was ever a chance we
> could ever hope to modify user's components file
>I have a slightly modified version that removes the default Fcc stuff that was
>added some time ago and drives me crazy as I don't want that.
So, yeah, that's the reason. I don't think there was ever a chance we
could ever hope to modify user's components files in a sane manner. The
default one
David Levine writes:
> Jon wrote:
>
> > Well, no. I did a "yum update" and things stopped working. I did
> > not install from source. I would be unable to get any work done if
> > I had to read the release notes on every package upgrade.
>
> I sympathize, but the diagnostic message that you go
Jon wrote:
> Well, no. I did a "yum update" and things stopped working. I did
> not install from source. I would be unable to get any work done if
> I had to read the release notes on every package upgrade.
I sympathize, but the diagnostic message that you got seems
sufficient to me.
/usr/sha
Ken Hornstein writes:
> >Jerrad Pierce writes:
> >> It's not broken, read the diagnostics and follow the directions provided.
> >> You have to supply a From now
> >
> >I would have expected the upgrade to install the appropriate components
> >to not break things.
>
> That should have happened, act
>Jerrad Pierce writes:
>> It's not broken, read the diagnostics and follow the directions provided.
>> You have to supply a From now
>
>I would have expected the upgrade to install the appropriate components
>to not break things.
That should have happened, actually (and as far as I know, it does).
Ken Hornstein writes:
> >When I try to send it from whatnow I get:
> >
> > post: message has no From: header
> > post: See default components files for examples
>
> So ... you read the release notes, right?
>
> --Ken
Well, no. I did a "yum update" and things stopped working. I did
not
>I would have expected the upgrade to install the appropriate components
>to not break things.
In which case it would likely break things in other ways,
or not do the right thing for some individuals.
Making specific changes to a template of unknown content is fraught with peril.
Jerrad Pierce writes:
> It's not broken, read the diagnostics and follow the directions provided.
> You have to supply a From now
I would have expected the upgrade to install the appropriate components
to not break things.
Jon
___
Nmh-workers mailing l
>When I try to send it from whatnow I get:
>
> post: message has no From: header
> post: See default components files for examples
So ... you read the release notes, right?
--Ken
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://l
It's not broken, read the diagnostics and follow the directions provided.
You have to supply a From now
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Jon wrote:
> Just upgraded. Have a message that looks like this:
>
> To: gumby, djb
> cc:
> Fcc: ssc
> Subject: Mucho Chango
> X-MH-Attachment: /home/jon/cb/ssc/e2/embedded/io_board/ioboard.c
>
> OK, this still needs some inspection and testing
Just upgraded. Have a message that looks like this:
To: gumby, djb
cc:
Fcc: ssc
Subject: Mucho Chango
X-MH-Attachment: /home/jon/cb/ssc/e2/embedded/io_board/ioboard.c
OK, this still needs some inspection and testing but to use those
21 matches
Mail list logo
