From: dsg@mitre.org (David S. Goldberg)
Subject: non-ASCII chars getting into In-Reply-To
Date: 16 Jul 1999 13:08:35 -0400 [thread overview]
Message-ID: <m1bwvw01q0c.fsf@blackbird.mitre.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
I sent the attached bug report to the nnimap mailing list this
morning. While I still think nnimap needs to do a better job of
handling this error from the IMAP server, and I have asked my system
admin to upgrade, I think it is a bug in pgnus that non-ASCII char in
Kai's name was not q-p'd in the In-Reply-To header.
Thanks,
[-- Attachment #2: Type: message/rfc822, Size: 5061 bytes --]
Received: from smtpsrv1.mitre.org (smtpsrv1.mitre.org [129.83.20.101])
by linus.mitre.org (8.8.7/8.8.7) with ESMTP id JAA29646;
Fri, 16 Jul 1999 09:21:17 -0400 (EDT)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA18903;
Fri, 16 Jul 1999 09:21:07 -0400 (EDT)
Received: (from root@localhost)
by avsrv1.mitre.org (8.9.3/8.9.3) id JAA23193;
Fri, 16 Jul 1999 09:21:16 -0400 (EDT)
Received: from smtpproxy1.mitre.org (mbunix.mitre.org [129.83.20.100])
by avsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA23181;
Fri, 16 Jul 1999 09:21:15 -0400 (EDT)
Received: from vic20.globalcom.se (IDENT:majordomo@vic20.globalcom.se [195.84.148.62])
by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id JAA03744;
Fri, 16 Jul 1999 09:21:14 -0400 (EDT)
Received: (from majordomo@localhost)
by vic20.globalcom.se (8.8.7/8.8.7) id PAA02935
for nnimap-list; Fri, 16 Jul 1999 15:21:25 +0200
Received: from linus.mitre.org (linus.mitre.org [129.83.10.1])
by vic20.globalcom.se (8.8.7/8.8.7) with ESMTP id PAA02930
for <nnimap@extundo.com>; Fri, 16 Jul 1999 15:21:24 +0200
Received: from blackbird.mitre.org (blackbird [129.83.65.14])
by linus.mitre.org (8.8.7/8.8.7) with ESMTP id JAA29547
for <nnimap@extundo.com>; Fri, 16 Jul 1999 09:19:33 -0400 (EDT)
Received: (from dsg@localhost)
by blackbird.mitre.org (8.8.7/8.8.7) id JAA05216;
Fri, 16 Jul 1999 09:19:32 -0400 (EDT)
Mail-Copies-To: never
To: The Nnimap Mailing List <nnimap@extundo.com>
Subject: IMAP error not handled
X-Face: GUaHTH@nS>[7,ME@-gYZ4#Wl{z"99k@[[Y8AcP0x1paqu.,z9,XSV1WI>{q3f6^e5(zrit
<4fV&VHhmE`uidRqtmG27;si9&r;#KSF~E#$%W8w(xdp)H4tW=\2XOk~3=@oGqqpj;m4xf
Ow;y26396&,34@9#~4;@*S;E0cq"LM9N(us4P%F(Nxis'Vvfm9?KufH;:Q$dMa-QWGLR&K
d0`LJZE8xb*>^yN>b]_NcU:E=Zn\1=#/(OS2
From: dsg@mitre.org (David S. Goldberg)
Date: 16 Jul 1999 09:19:32 -0400
Message-ID: <m1bn1ww3f6j.fsf@blackbird.mitre.org>
Lines: 71
User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/20.4 (Emerald)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-nnimap@vic20.globalcom.se
Precedence: bulk
Using Pterodactyl Gnus v0.95 and nnimap 0.123.
I found that the following message:
To: Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Cc: nnimap@extundo.com
Subject: Re: Post to nnimap?
References: <vafzp0xv7r6.fsf@petty.cs.uni-dortmund.de>
From: Amos Gouaux <amos+lists.nnimap@utdallas.edu>
X-Envelope-Sender: amos+lists.nnimap@utdallas.edu
Date: 16 Jul 1999 01:29:35 -0500
In-Reply-To: Kai Großjohann's message of "16 Jul 1999 01:00:13 +0200"
X-Gnus-Mail-Source: directory:/afs/rcf/user/dsg/.Mail/incoming
Message-ID: <q6mzp0xrttc.fsf@spartacus.utdallas.edu>
User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.0 (20 minutes to Nikko)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-nnimap@vic20.globalcom.se
Precedence: bulk
Lines: 20
got filed by procmail into one of my nnml sources rather than properly
being passed through the deliver program to my IMAP server (where I
file this mailing list). I figured I got caught yet again by one of
my overly broad regexps in my .procmailrc. No big deal. I just B-m
the article to the IMAP group so I can read it in its proper thread
context.
To my surprise, the article never made it to the IMAP group. Upon
review of *imap-log* I see
1114 APPEND "INBOX.gnus-imap" {3193}
+ go ahead
[entire text of article ...]
1114 NO Message contains non-ASCII characters in headers
1115 EXAMINE "INBOX.gnus-imap"
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-dormant
gnus-expire gnus-save)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen
gnus-dormant gnus-expire gnus-save \*)]
* 18 EXISTS
* 0 RECENT
* OK [UNSEEN 16]
* OK [UIDVALIDITY 903716674]
1115 OK [READ-ONLY] Completed
and upon further review of my procmail log, I see a failure message
from deliver complaining about the non-ASCII header.
OK, so this message is probably a pathological case. Apparently my
imap server (Cyrus IMAP4 v1.5.10) can't handle it. However, because I
tried B-m to move the article, it is now nowhere to be found in any of
my mail areas (nnml or nnimap) and I can only read it in *imap-log*.
For this particular article, that's not so bad, but I wouldn't want to
lose an important message from my boss or my wife. I haven't looked
at the source for B-m yet, but I suspect it has some means of
detecting a failure on the receiving back end and doesn't do the remove
on the source if it detects it. nnimap should be able to detect this
sort of error and report it. Other than what I see in *imap-log*,
there's no indication in XEmacs that anything went wrong (e.g. nothing
in *Message-Log*).
Thanks,
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
From: dsg@mitre.org (David S. Goldberg)
To: The Nnimap Mailing List <nnimap@extundo.com>
Subject: IMAP error not handled
Date: 16 Jul 1999 09:19:32 -0400
Message-ID: <m1bn1ww3f6j.fsf@blackbird.mitre.org>
Using Pterodactyl Gnus v0.95 and nnimap 0.123.
I found that the following message:
To: Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Cc: nnimap@extundo.com
Subject: Re: Post to nnimap?
References: <vafzp0xv7r6.fsf@petty.cs.uni-dortmund.de>
From: Amos Gouaux <amos+lists.nnimap@utdallas.edu>
X-Envelope-Sender: amos+lists.nnimap@utdallas.edu
Date: 16 Jul 1999 01:29:35 -0500
In-Reply-To: Kai Großjohann's message of "16 Jul 1999 01:00:13 +0200"
X-Gnus-Mail-Source: directory:/afs/rcf/user/dsg/.Mail/incoming
Message-ID: <q6mzp0xrttc.fsf@spartacus.utdallas.edu>
User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) XEmacs/21.0 (20 minutes to Nikko)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-nnimap@vic20.globalcom.se
Precedence: bulk
Lines: 20
got filed by procmail into one of my nnml sources rather than properly
being passed through the deliver program to my IMAP server (where I
file this mailing list). I figured I got caught yet again by one of
my overly broad regexps in my .procmailrc. No big deal. I just B-m
the article to the IMAP group so I can read it in its proper thread
context.
To my surprise, the article never made it to the IMAP group. Upon
review of *imap-log* I see
1114 APPEND "INBOX.gnus-imap" {3193}
+ go ahead
[entire text of article ...]
1114 NO Message contains non-ASCII characters in headers
1115 EXAMINE "INBOX.gnus-imap"
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-dormant
gnus-expire gnus-save)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen
gnus-dormant gnus-expire gnus-save \*)]
* 18 EXISTS
* 0 RECENT
* OK [UNSEEN 16]
* OK [UIDVALIDITY 903716674]
1115 OK [READ-ONLY] Completed
and upon further review of my procmail log, I see a failure message
from deliver complaining about the non-ASCII header.
OK, so this message is probably a pathological case. Apparently my
imap server (Cyrus IMAP4 v1.5.10) can't handle it. However, because I
tried B-m to move the article, it is now nowhere to be found in any of
my mail areas (nnml or nnimap) and I can only read it in *imap-log*.
For this particular article, that's not so bad, but I wouldn't want to
lose an important message from my boss or my wife. I haven't looked
at the source for B-m yet, but I suspect it has some means of
detecting a failure on the receiving back end and doesn't do the remove
on the source if it detects it. nnimap should be able to detect this
sort of error and report it. Other than what I see in *imap-log*,
there's no indication in XEmacs that anything went wrong (e.g. nothing
in *Message-Log*).
Thanks,
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
[-- Attachment #3: Type: text/plain, Size: 133 bytes --]
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next reply other threads:[~1999-07-16 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-16 17:08 David S. Goldberg [this message]
1999-08-27 19:11 ` Lars Magne Ingebrigtsen
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=m1bwvw01q0c.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).