From: jpff <jpff@codemist.co.uk>
To: charles@aurox.ch (Charles A. Roelli)
Cc: 25891@debbugs.gnu.org
Subject: bug#25891: 25.2; Reply inRMAIL sometimes fails
Date: Tue, 19 Sep 2017 21:34:26 +0100 [thread overview]
Message-ID: <9774-Tue19Sep2017213426+0100-jpff@codemist.co.uk> (raw)
In-Reply-To: <m2efr2mqu1.fsf@aurox.ch> (charles@aurox.ch)
[-- Attachment #1: Type: text/plain, Size: 2786 bytes --]
Attached is a mailfile (set rail-mode) with one message. Typing "r" to
reply I see
------------------------------------------------------------------
From: jpff <jpff@codemist.co.uk>
To: Steven Yi <stevenyi@gmail.com>
CC: Victor.Lazzarini@mu.ie
In-reply-to:
<CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com>
(message from Steven Yi on Tue, 19 Sep 2017 08:39:00 -0400)
Subject: Re: Next release
BCC: jpff@codemist.co.uk
References: <9c571770-2e28-4b78-95c6-baad81925043@codemist.co.uk> <63268264-9DE9-4EDE-AE92-BC3236D5A1FF@mu.ie> <CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com>
--text follows this line--
==John ffitch
------------------------------------------------------------------------
(that is my automatically inserted signature)
Adding text `"test" to this and sending the message I get (my BCC) is
------------------------------------------------------------------------
Date: Tue, 19 Sep 2017 21:13:14 +0100
From: jpff <jpff@codemist.co.uk>
To: Steven Yi <stevenyi@gmail.com>
Cc: "Victor.Lazzarini@mu.ie"
<CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com>
Subject: Re: Next release
test
==John ffitch
------------------------------------------------------------------------
which is clearly ill formed -- and indeed I also get the message
------------------------------------------------------------------------
Date: Tue, 19 Sep 2017 21:13:51 +0100
From: Mail Delivery System <Mailer-Daemon@codemist.co.uk>
To: jpff@codemist.co.uk
Subject: Mail delivery failed: returning message to sender
Parts/Attachments:
1 Shown 8 lines Text
2 Shown 161 bytes Message, "Delivery Status"
3 Shown 1.2 KB Message, "Re: Next release"
3.1 Shown 3 lines Text
----------------------------------------
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com
Unknown user
[ Part 2: "Delivery Status" ]
Reporting-MTA: dns; codemist.co.uk
Action: failed
Final-Recipient:
rfc822;CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com
Status: 5.0.0
[ Part 3: "Included Message" ]
Date: Tue, 19 Sep 2017 21:13:14 +0100
From: jpff <jpff@codemist.co.uk>
To: Steven Yi <stevenyi@gmail.com>
Cc: "Victor.Lazzarini@mu.ie"
<CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com>
Subject: Re: Next release
test
==John ffitch
------------------------------------------------------------------------
Experiments suggest that if I move the I-reply-to lines to the end of
the headers it works
Hope that is clear?
==John ffitch
[-- Attachment #2: ~/MAIL/broken --]
[-- Type: text/plain, Size: 4920 bytes --]
From stevenyi@gmail.com Tue Sep 19 13:39:11 2017
Return-path: <stevenyi@gmail.com>
Envelope-to: jpff@codemist.co.uk
Delivery-date: Tue, 19 Sep 2017 13:39:11 +0100
Received: from mail-qk0-f176.google.com ([209.85.220.176])
by codemist.co.uk with esmtp (Exim 4.89)
(envelope-from <stevenyi@gmail.com>)
id 1duHnw-0003CK-0F
for jpff@codemist.co.uk; Tue, 19 Sep 2017 13:39:11 +0100
Received: by mail-qk0-f176.google.com with SMTP id u73so3381121qkl.12
for <jpff@codemist.co.uk>; Tue, 19 Sep 2017 05:39:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-transfer-encoding;
bh=8MuFyT7LUs5SX5yq6pTgOzsE10Bne0HSUCLixuvD1uw=;
b=IzVdP3t2tJi6tMPQMVFY+X3b3e3rASEE0OebZPXSj5YJjvgRN5pfpoRiJ7VNf+VcPg
6djP+y2hqBEpnQxNO/rXRZhKXqgiG8pGx/Jipmi2JaWQp2CjWENE8s5bbZqn4Vxw4MdD
UXkV89VWKJQgfFCRmK7NDyBx+tmhFaPDQkL1ZOQQ6XStQzgfLCEDjU6Urb0KCTCGYCNw
U5jV2wSFAFGMm4dcf2nV3p+oHkR1o3PAFG57013KwMSNYwBRGxMXJ320g/CxrEzRx36Y
Vb4DREZpvIoONlMJI9v3qefYScH5ImqfcGr4tgV8/Omp/P1nN3CLaoFzUuTCidKt8Zg9
P2lA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-transfer-encoding;
bh=8MuFyT7LUs5SX5yq6pTgOzsE10Bne0HSUCLixuvD1uw=;
b=has5CAbHtrDmSz8tNWeoBZIFiiyn5R4r2HEWSHaLKFcrAQuYvrf1n3gMealACyI2Cc
S5mF8Ccs34DsyNidA8PBUo+v7m7YQqestpZmr7/r07tVppijRyv08URQG7w9o+WtcNP4
C9RoU6OJkUNLBLcmq2QUgJ1z6G7cqtDF61arI0EKcZols5qo0hCAWy33pwFvhV3NOEON
jnkflnTbZ4iH6ktDgKltdI3hieI+nVW4GW799TrX6OlBjDCtqtL7Ase9YTVMogrJ/OzR
s1Ygnm05cOcrc5KchCaSWm/zB50Bpxa5846SvuBggf+eINxnqCJPCB9jBk+O2AHh2oEO
feUw==
X-Gm-Message-State: AHPjjUhqini2aBFhx6Tc7mt8BfFu8Ic8ijXHV72KD9ArztoVUYYKCkws
enJ9eAYcs3ZYqHE4VmpcyV5NeEpr25VFH8hVIbg=
X-Google-Smtp-Source: AOwi7QBFLmZtLwH9ADA4Jhgms92h3p8nHe5qjAFXlWR7F4jMuhfNs9sawI/gpouF7iyOn3h8iSnj63tS0TPEmIaaCNs=
X-Received: by 10.55.40.152 with SMTP id o24mr1657482qko.235.1505824741132;
Tue, 19 Sep 2017 05:39:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.108.98 with HTTP; Tue, 19 Sep 2017 05:39:00 -0700 (PDT)
In-Reply-To: <63268264-9DE9-4EDE-AE92-BC3236D5A1FF@mu.ie>
References: <9c571770-2e28-4b78-95c6-baad81925043@codemist.co.uk> <63268264-9DE9-4EDE-AE92-BC3236D5A1FF@mu.ie>
From: Steven Yi <stevenyi@gmail.com>
Date: Tue, 19 Sep 2017 08:39:00 -0400
Message-ID: <CANtcCs7-TwLw9PiOvQBYyertQbWurCsJ-i9B9JjGQTZxoaNesg@mail.gmail.com>
Subject: Re: Next release
To: Victor Lazzarini <Victor.Lazzarini@mu.ie>
Cc: John ff <jpff@codemist.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.9 (-)
Content-Length: 1831
Status: RO
X-Status:
X-Keywords:
X-UID: 8771
X-RMAIL-ATTRIBUTES: --------
Wow that is quite an upgrade adventure!
I think we still have the issue with reverting the changes for
if-then? (Or has that been done?) I've been a bit heads down
preparing for the conference and getting final changes done for a Blue
release. I still see changes coming in from Michael for the Appveyor
build so I suppose we need to coordinate with him on that.
On Tue, Sep 19, 2017 at 8:18 AM, Victor Lazzarini
<Victor.Lazzarini@mu.ie> wrote:
> I=E2=80=99d say a couple of things:
>
> 1) Menno=E2=80=99s issue
> 2) Eduardo=E2=80=99s PR
>
> and we should be OK.
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 19 Sep 2017, at 13:14, John ff <jpff@codemist.co.uk> wrote:
>>
>> Just checking back in. I have been having local problems. Printer stop=
ped working so lost a day failing to get the replacement to work. Eventual=
ly realised that I needed newer software which requires OS upgrade. Spent =
most of Sunday upgrading my server/firewall from Debian wheezy to Jessie, o=
n the way to stretch. Disaster struck when the Jessie failed to reboot. A=
s the computer is headless I had to dismantle it all, loose the internet, a=
nd find USB keyboard and dvi cable for screen. Eventually discovered that =
the kernel installed with Jessie did not load, but the previous kernel did.=
An hour or so thinking and I managed to get autobooting to work so re-ins=
talled with internet and hidden location.... , and eventually email resumed=
.
>>
>> What are the stoppers to release? I did look at Meno's ladspa problem b=
ut that is outside my current knowledge.
>>
>> z=3D=3DJohn
>> =E2=81=A3Sent from TypeApp
>
next prev parent reply other threads:[~2017-09-19 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 15:02 bug#25891: 25.2; Reply inRMAIL sometimes fails jpff
2017-02-28 7:22 ` Glenn Morris
2017-09-19 19:27 ` Charles A. Roelli
2017-09-19 19:58 ` jpff
2017-09-19 20:34 ` jpff [this message]
2017-09-20 19:16 ` Charles A. Roelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9774-Tue19Sep2017213426+0100-jpff@codemist.co.uk \
--to=jpff@codemist.co.uk \
--cc=25891@debbugs.gnu.org \
--cc=charles@aurox.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.