From Newsgroup: comp.mail.pine

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard. Now, I realize that the right part of the Message-ID
can be set in .pinerc. How can alpine be set to allow the News server to provide Message-ID and not alpine? For archiving purposes, during NNTP,
can alpine, in injecting the proto article, receive Message-ID from the
server and add it to the headers for archiving locally?
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

Now, I realize that the right part of the Message-ID can be set in
.pinerc. How can alpine be set to allow the News server to provide Message-ID and not alpine?

Alpine always generates the Message-ID header, so there is no way to avoid this.

For archiving purposes, during NNTP, can alpine, in injecting the proto article, receive Message-ID from the server and add it to the headers
for archiving locally?

Alpine does not edit messages this way.
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

According to Eduardo Chappa <chappa@washington.edu>:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

You're right, it's funky but OK to have a single component after the @ sign.

Not to whine and change the topic or anything, but alpine hasn't compiled on MacOS since they added VisionOS support to xcode a couple of years ago. I suspect the fix is a line or two turning VisionOS off the same way it doesn't support iOS or iPadOS or WatchOS, but I haven't been able to figure out where. --
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Eduardo Chappa <chappa@washington.edu> wrote:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

USEFOR RFC 5536

The right part is commonly derived from a domain. Fine, that's not a
MUST.

Now, I realize that the right part of the Message-ID can be set in >>.pinerc. How can alpine be set to allow the News server to provide >>Message-ID and not alpine?

Alpine always generates the Message-ID header, so there is no way to avoid >this.

Ok.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

USEFOR RFC 5536

The right part is commonly derived from a domain. Fine, that's not a
MUST.

Right, however, the release notes for version 2.24 say:

+ Alpine uses the domain in the From: header of a message to generate
a message-id and suppresses all information about Alpine, version,
revision, and time of generation of the message-id from this header.
This information is replaced by a random string.

Would upgrading to a more current version of Alpine help you? (see the message-id of this message to see it in action).
--
Eduardo

Now, I realize that the right part of the Message-ID can be set in
.pinerc. How can alpine be set to allow the News server to provide
Message-ID and not alpine?

Alpine always generates the Message-ID header, so there is no way to avoid >> this.

Ok.

--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Eduardo Chappa <chappa@washington.edu> wrote:

Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

USEFOR RFC 5536

The right part is commonly derived from a domain. Fine, that's not a
MUST.

Right, however, the release notes for version 2.24 say:

+ Alpine uses the domain in the From: header of a message to generate
a message-id and suppresses all information about Alpine, version,
revision, and time of generation of the message-id from this header.
This information is replaced by a random string.

Would upgrading to a more current version of Alpine help you? (see the >message-id of this message to see it in action).

I'm not the O.P. I asked here because I saw the Message-ID and thought
it was nonstandard. Since I reread USEFOR, I know it's not.

I am using a DEB package too. I see that it's version 2.26. The left
part is a random string. I've long had the feature set for ROT-13 of the
domain used for the right part. Doesn't that go back to pine?

If I see the O.P. posting again, I'll suggest that he might install a
more recent package or build the latest version himself.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

USEFOR RFC 5536

The right part is commonly derived from a domain. Fine, that's not a
MUST.

Right, however, the release notes for version 2.24 say:

+ Alpine uses the domain in the From: header of a message to generate
a message-id and suppresses all information about Alpine,
version, revision, and time of generation of the message-id from
this header. This information is replaced by a random string.

Would upgrading to a more current version of Alpine help you? (see the
message-id of this message to see it in action).

I'm not the O.P. I asked here because I saw the Message-ID and thought
it was nonstandard. Since I reread USEFOR, I know it's not.

We never saw that message here, so from our perspective, this was your question. Keep that in mind as we talk to you.

I am using a DEB package too. I see that it's version 2.26. The left
part is a random string. I've long had the feature set for ROT-13 of the domain used for the right part. Doesn't that go back to pine?

The ROT-13 part is from the time of Pine, yes. What I am talking about is
that since version 2.24 the part to the right of the @ character in the message-id is an actual domain. In previous versions of Pine/Alpine it
might be a machine name, not a domain name. Since version 2.24 it is the domain from the From: field, not related in any way to the machine you are using. The message-id you posted in your first post did not have a domain
in that place. An upgrade would change that.

If I see the O.P. posting again, I'll suggest that he might install a
more recent package or build the latest version himself.

Great! I appreciate that!
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Eduardo Chappa <chappa@washington.edu> wrote:

On Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

Tue, 28 Apr 2026, Adam H. Kerman wrote:

Eduardo Chappa <chappa@washington.edu> wrote:

On Mon, 27 Apr 2026, Adam H. Kerman wrote:

In a test newsgroup, a user's News article had this Message-ID.

Message-ID: <alpine.DEB.2.22.394.2604262138340.794162@XPS13>

That's nonstandard.

What standard is the one you are referring to?

USEFOR RFC 5536

The right part is commonly derived from a domain. Fine, that's not a >>>>MUST.

Right, however, the release notes for version 2.24 say:

+ Alpine uses the domain in the From: header of a message to generate >>> a message-id and suppresses all information about Alpine,
version, revision, and time of generation of the message-id from
this header. This information is replaced by a random string.

Would upgrading to a more current version of Alpine help you? (see the >>>message-id of this message to see it in action).

I'm not the O.P. I asked here because I saw the Message-ID and thought
it was nonstandard. Since I reread USEFOR, I know it's not.

We never saw that message here, so from our perspective, this was your >question. Keep that in mind as we talk to you.

It was absolutely my question, not the O.P.'s. I was the one who cared
about how the right part of the Message-ID was set in his test News
article. Since you provide excellent user support, this is the right
newsgroup in which to ask.

Thank you as always.

I am using a DEB package too. I see that it's version 2.26. The left
part is a random string. I've long had the feature set for ROT-13 of the >>domain used for the right part. Doesn't that go back to pine?

The ROT-13 part is from the time of Pine, yes. What I am talking about is >that since version 2.24 the part to the right of the @ character in the >message-id is an actual domain. In previous versions of Pine/Alpine it
might be a machine name, not a domain name. Since version 2.24 it is the >domain from the From: field, not related in any way to the machine you are >using. The message-id you posted in your first post did not have a domain
in that place. An upgrade would change that.

If that were a host name, I simply assumed that he didn't have domain
set in his Debian configuration where alpine could find it and he left User-Domain unset in .pinerc.

In my .pinerc, I must set User-Domain because the host itself is in a
different domain that I do not use on From.

. . .

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Mon, 27 Apr 2026, John Levine wrote:

Not to whine and change the topic or anything, but alpine hasn't
compiled on MacOS since they added VisionOS support to xcode a couple of years ago. I suspect the fix is a line or two turning VisionOS off the
same way it doesn't support iOS or iPadOS or WatchOS, but I haven't been able to figure out where.

I am sorry I took so long to reply to this. I do not own a mac to test
this. If you, or anyone, would like to submit a patch, I would be happy
to take a look at it.

If you want me to take a look at the error message when compilation fails,
I will be glad to do so too. Either send it to me via email, or post it
here. If the error is in the configure stage, please send me the file config.log via email.

See below for information on contact information through email.

Thank you.
--
Eduardo
https://alpineapp.email/alpine/contact.html (email address) https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21f-Linux NewsLink 1.2