From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: forwarded mail problems
Date: 18 Jun 1999 12:18:20 -0700 [thread overview]
Message-ID: <x7g13p5ncz.fsf@homestyle.dcn.davis.ca.us> (raw)
[-- Attachment #1: Type: text/plain, Size: 28 bytes --]
A note from my co-worker:
[-- Attachment #2: Type: message/rfc822, Size: 455 bytes --]
To: wjhardaker@ucdavis.edu
Subject: mail problems
Date: Fri, 18 Jun 1999 09:13:03 -0700
Message-ID: <199906181613.JAA22983@clover.ece.ucdavis.edu>
Hi Wes,
Have you changed something in your outgoing mail settings? The last couple
of forwards I've gotten from you generate the following error when I
attempt to read them with vanilla show:
% show
(Message inbox:4643)
mhn: "message/rfc822" type in message 4643 should be encoded in 7bit, continuing...
[-- Attachment #3: Type: text/plain, Size: 180 bytes --]
So, uh, ??? Should the encoding be different for outgoing
message/rfc822 messages?
--
Wes Hardaker
Distributed Computing Analysis and Support
University of California at Davis
next reply other threads:[~1999-06-18 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-18 19:18 Wes Hardaker [this message]
1999-06-18 19:26 ` Colin Rafferty
1999-06-18 20:14 ` Bruce Stephens
1999-06-21 15:56 ` Wes Hardaker
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=x7g13p5ncz.fsf@homestyle.dcn.davis.ca.us \
--to=wjhardaker@ucdavis.edu \
/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).