slrn Message-ID for email-only messages
Whiskers
newsgroup, no Message-ID is created.
This doesn't seem to be a 'fatal' problem; the recipient's email service
provider seems to allocate a Message-ID of its own.
A Message-ID is only a 'should' in RFC 5322, rather than a 'must', but I
think it would be preferable for slrn to generate a suitable email
Message-ID, if only to facilitate identification of the message and
conventional threading.
Ideally, the email Message-ID should be capable of having a different FQDN
from newsgroup articles; some of us use FQDNs for newsgroups for which we
do not have permission to use for other purposes - eg the FQDNs permitted
for customers of Individual.net are for newsgroup use only.
Has anyone else noticed this - or found the settings that will make slrn
do it, or a suitable workaround? Is there a patch or macro I haven't been
able to find?
I have looked at the changelogs for slrn and of course the manual, but
haven't found any mention of email Message-IDs other than for 'courtesy
copy' emails of newsgroup posts.
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
Whiskers
> When slrn sends an email 'Reply' without also posting a followup to the
> newsgroup, no Message-ID is created.
>
> This doesn't seem to be a 'fatal' problem; the recipient's email service
> provider seems to allocate a Message-ID of its own.
>
> A Message-ID is only a 'should' in RFC 5322, rather than a 'must', but I
> think it would be preferable for slrn to generate a suitable email
> Message-ID, if only to facilitate identification of the message and
> conventional threading.
[...]
I've contrived a work-around that seems to work: using a Perl program
called "perl-Email-MessageID" I've written a little shell script that can
(to quote the man file) "Generate world unique message-ids". Here's my
gem of a script (actually pasted from the man file!):
#v+
#!/usr/bin/perl
#
#-- generate Message-ID for email
use Email::MessageID;
my $mid = Email::MessageID->new;
print "Message-ID: $mid\x0A\x0D";
#v-
My preferred editor (mcedit) can 'paste the output of a shell command' so
I can put MIDs of the form
Message-ID: 1259276211....@tavy.mobile.private
into the 'headers' space of the outgoing message. The Perl program looks
as though (once one has worked out what the man file means) it can be
given settings or parameters to customise the MIDs created, but the
default output looks fine to me for email use.
andrew
> When slrn sends an email 'Reply' without also posting a followup to the
> newsgroup, no Message-ID is created.
My apologies if I have misunderstood your post but I replied via email
to this post (directing to my own email address) and the resulting
email carried a _duplicate_ of the original MID from slrn:
#v+
Message-ID: <200911271...@skamandros.andrews-corner.org>
Date: Fri, 27 Nov 2009 18:12:38 +1100
User-Agent: slrn/pre1.0.0-17 (Win32)
#v-
Admittedly I am using Troy's create_msg_id.sl and the Windows fake
sendmail but I suspect the result is the same on my Linux copy of slrn
where I use mutt and msmtp.
Andrew
--
Do you think that's air you're breathing?
andrew
> On 2009-11-25, Whiskers <catwh...@operamail.com> wrote:
>
>> When slrn sends an email 'Reply' without also posting a followup to the
>> newsgroup, no Message-ID is created.
>
> My apologies if I have misunderstood your post but I replied via email
> to this post (directing to my own email address) and the resulting
> email carried a _duplicate_ of the original MID from slrn
And I duplicated the test on my Linux slrn (yes I know it is a little
crazy) with mutt and msmtp and again the MID was preserved:
#v+
Subject: Re: slrn Message-ID for email-only messages
Message-ID: <200911271...@skamandros.andrews-corner.org>
#v-
Whiskers
Interesting. When I do that without supplying a Message-ID in my editor,
the message arrives in my Operamail inbox with
Message-Id: <200911271420...@spf5-2.us4.outblaze.com>
and the Bcc in my GMX inbox has
Message-ID: <20091127141...@mx045.gmx.net>
while the copy saved by slrn in ~/News/Replies has no Message-ID.
(Articles posted to newsgroups by slrn are saved in ~/News/Posts with
slrn's Message-ID headers).
So it looks to me as though either your more recent version of slrn, or
the Message-ID macro you are using, is responsible for the different
behaviour.