From: Eli Zaretskii <eliz@gnu.org>
To: Olivier <Olivier.Nicole@cs.ait.ac.th>
Cc: 31590@debbugs.gnu.org
Subject: bug#31590: 25.1; malformed email address in RMAIL
Date: Fri, 25 May 2018 11:26:02 +0300 [thread overview]
Message-ID: <83d0xk9m5h.fsf@gnu.org> (raw)
In-Reply-To: <wu7fu2g1jbt.fsf@banyan.cs.ait.ac.th> (message from Olivier on Fri, 25 May 2018 10:54:14 +0700)
> From: Olivier <Olivier.Nicole@cs.ait.ac.th>
> Date: Fri, 25 May 2018 10:54:14 +0700
>
> When trying to read the new messages in RMAIL, I get the error
> "Malformed email address" on one message (it did happen in the past,
> once every 2 years maybe). As a consequence, messages following the
> malformed one cannot be read and no message is deleted from the INBOX,
> resulting in reading the same messages over and over again.
>
> This time I managed to identify and keep a copy of the
> concerned message.
>
> I am reading my mail through POP3, with movemail installed as part of
> mailutils-3.1.1_3.
>
> Emacs installation is pretty standard, build from FreeBSD ports.
>
> Trying to read the same message with Thunderbird (POP3 and IMAP) did not
> give any error message.
>
> I have been using Emacs for over 30 years and I have always been
> completely happy with it, but that bug bugs me.
>
> Attached is a copy of the message.
Thank you for your report.
Trying to read the message you attached gave me a different error:
Invalid mbox file
If I use the 'C-u g' command in Rmail to get new mail messages from
that file, I get this error message:
Message is not a valid RFC2822 message
The message you attached is indeed invalid for the mbox format: it
doesn't start with a "From <address>" line, which is mandatory for the
mbox format used by Rmail. Once I fixed that (by adding the missing
"From" line manually), Rmail could read and display that message just
fine.
When some email message in the received mbox file is invalid, Emacs
cannot continue processing email, because doing so could completely
ruin your inbox. Emacs expects you to manually repair the incoming
mbox file, and then try again. So I think Emacs does TRT in this
case.
So the problem with malformed email address cannot be reproduced with
this message. I tried both Emacs 25.1 and the current release
candidate of Emacs 26.1, and they both show the error messages
described above, not the one you reported. From your bug report, I
see that the "Malformed email address" message comes from the movemail
program, not from Emacs. I don't find such a message in the version
of movemail we distribute with Emacs, and since you say you have
Mailutils installed, I guess you should report this problem to the
Mailutils developers.
next prev parent reply other threads:[~2018-05-25 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 3:54 bug#31590: 25.1; malformed email address in RMAIL Olivier
2018-05-25 8:26 ` Eli Zaretskii [this message]
[not found] ` <CA+g+BviCUeq1p0202bstKvjPCQiR__CR2LCyYyVd9wR4h6ys7g@mail.gmail.com>
2018-05-25 8:51 ` Eli Zaretskii
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=83d0xk9m5h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31590@debbugs.gnu.org \
--cc=Olivier.Nicole@cs.ait.ac.th \
/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.