From: Arcady Genkin <a.genkin@utoronto.ca>
Subject: Tab after From: causes (nobody) in summary buffer
Date: 15 Mar 2000 15:19:55 -0500 [thread overview]
Message-ID: <871z5c9eac.fsf@tea.thpoon.com> (raw)
Lately all incoming messages appear as coming from "(nobody)" in the
summary buffer. The only difference from the properly displayed
messages that I can find is that there is now a tab after the From: in
the headers:
From:[<--TAB-->]John Doe <john@doe.com
I am not sure if this is a bug or perhaps this is violation of some
RFC or other... The only thing that's changed in my setup (which
triggered the tab being inserted) is that I changed forwarding from my
school account to go straight to my mail server (instead of the ISP's
mail server, as it was before).
Any suggestions highly appreciated!
--
Arcady Genkin http://www.thpoon.com
Nostalgia isn't what it used to be.
next reply other threads:[~2000-03-15 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 20:19 Arcady Genkin [this message]
2000-03-16 6:34 ` Daiki Ueno
2000-03-16 8:18 ` Arcady Genkin
2000-03-16 10:55 ` Kai Großjohann
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=871z5c9eac.fsf@tea.thpoon.com \
--to=a.genkin@utoronto.ca \
/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).