From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: bad (i.e. serious) mail problems
Date: Tue, 30 Mar 1999 17:08:28 -0500 [thread overview]
Message-ID: <99Mar30.170612est.13945-2@gateway.intersys.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "30 Mar 1999 17:18:36 +0200"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Kai.Grossjohann@CS.Uni-Dortmund.DE on Tue, 30 Mar 1999
| Then pop3.el assumes such a file has been involved and just concatenates
| the messages retrieved from the POP server. IMHO this is wrong -- the
| program converting to mbox format should take care of escaping From_
| lines if necessary.
Read the POP3 specifications. POP clients perform no modification to the
mail spool or messages retrieved from it. Or if they do, they do as little
as possible. IN the case of pop3, I construct an RFC 821-style envelope
based on RFC 822 headers only if the POP server is stupid enough to strip
it *AND* there is no MMDF or Babyl delimiter (yes, pop3 is smart enough to
grok MMDF and Babyl messages).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE3AUtcgl+vIlSVSNkRAiZEAKCjNyYR7qhA8Yzp6SJ4nbKadwf3TwCeIbjJ
5TYlNYw17uAgjz5OHKGfMMc=
=4BIQ
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Caution: Happy Fun Ball may suddenly
Minion of Nathan - Nathan says Hi! \ accelerate to dangerous speeds.
PGP Key: at a key server near you! \
next prev parent reply other threads:[~1999-03-30 22:08 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-23 23:50 Dmitry Yaitskov
1999-02-26 8:32 ` Lars Magne Ingebrigtsen
1999-02-26 13:29 ` Dmitry Yaitskov
1999-02-26 16:44 ` Neil Crellin
1999-02-27 3:24 ` Dmitry Yaitskov
1999-02-27 13:07 ` Lars Magne Ingebrigtsen
1999-02-28 5:19 ` Dmitry Yaitskov
1999-02-28 5:32 ` Dmitry Yaitskov
1999-02-28 12:17 ` Lars Magne Ingebrigtsen
1999-03-01 16:58 ` Shane Holder
1999-03-02 15:08 ` Lars Magne Ingebrigtsen
1999-03-02 16:06 ` Shane Holder
1999-03-04 1:19 ` Lars Magne Ingebrigtsen
1999-03-04 17:10 ` Shane Holder
1999-03-04 20:24 ` Shane Holder
1999-03-04 20:50 ` Harry Putnam
1999-03-04 22:55 ` Shane Holder
1999-03-05 9:21 ` Kai.Grossjohann
1999-03-08 16:12 ` Shane Holder
1999-03-08 17:27 ` Shane Holder
1999-03-19 8:37 ` Simon Michael
1999-03-19 17:38 ` Shane Holder
1999-03-28 15:25 ` Lars Magne Ingebrigtsen
1999-03-28 18:16 ` Dmitry Yaitskov
1999-03-29 9:45 ` Kai.Grossjohann
1999-03-29 17:32 ` bad (i.e. serious) mail problems - solution, kind of Dmitry Yaitskov
1999-03-29 17:45 ` Dmitry Yaitskov
1999-03-29 20:37 ` Dmitry Yaitskov
1999-03-30 1:05 ` Stainless Steel Rat
1999-03-30 1:59 ` Dmitry Yaitskov
1999-03-30 15:25 ` Stainless Steel Rat
1999-03-30 1:04 ` bad (i.e. serious) mail problems Stainless Steel Rat
1999-03-30 1:56 ` Dmitry Yaitskov
1999-03-30 15:12 ` Stainless Steel Rat
1999-03-30 15:18 ` Kai.Grossjohann
1999-03-30 22:08 ` Stainless Steel Rat [this message]
1999-03-31 13:13 ` Kai.Grossjohann
1999-03-31 15:20 ` Stainless Steel Rat
1999-03-31 15:34 ` Kai.Grossjohann
1999-03-30 17:10 ` Dmitry Yaitskov
1999-03-31 0:30 ` Stainless Steel Rat
1999-03-31 1:17 ` Dmitry Yaitskov
1999-03-31 1:32 ` Stainless Steel Rat
1999-03-31 3:06 ` Dmitry Yaitskov
1999-03-31 15:34 ` Stainless Steel Rat
1999-03-31 15:47 ` Kai.Grossjohann
1999-03-31 3:23 ` Greg Stark
1999-03-31 3:37 ` Dmitry Yaitskov
1999-03-31 15:36 ` Stainless Steel Rat
1999-03-31 16:39 ` Dmitry Yaitskov
1999-03-31 12:35 ` Kai.Grossjohann
1999-03-31 14:47 ` Frank D. Cringle
1999-04-01 2:05 ` Russ Allbery
1999-03-31 15:11 ` Stainless Steel Rat
1999-03-31 15:36 ` Kai.Grossjohann
1999-03-31 20:29 ` Stainless Steel Rat
1999-04-01 9:06 ` Kai.Grossjohann
1999-03-31 16:21 ` Christopher K Davis
1999-03-31 20:35 ` Stainless Steel Rat
1999-03-31 21:24 ` Christopher K Davis
1999-04-01 1:07 ` Stainless Steel Rat
1999-04-01 3:27 ` Christopher K Davis
1999-04-01 9:03 ` Kai.Grossjohann
1999-04-01 9:23 ` Kai.Grossjohann
1999-04-01 22:06 ` Stainless Steel Rat
1999-04-02 6:54 ` Hans de Graaff
1999-04-02 10:18 ` Kai.Grossjohann
1999-04-02 17:51 ` Stainless Steel Rat
[not found] ` <99Apr2.124830est.13869-2@gateway.inters! ys.com>
1999-04-03 10:04 ` Kai.Grossjohann
1999-04-03 13:37 ` Stainless Steel Rat
1999-04-17 5:58 ` Lars Magne Ingebrigtsen
1999-04-02 13:39 ` Lars Magne Ingebrigtsen
1999-03-31 9:59 ` Kai.Grossjohann
1999-03-30 18:31 ` Dmitry Yaitskov
1999-03-31 0:31 ` Stainless Steel Rat
1999-03-31 1:19 ` Dmitry Yaitskov
1999-03-30 9:55 ` Kai.Grossjohann
1999-03-30 15:20 ` Stainless Steel Rat
1999-03-30 15:34 ` Kai.Grossjohann
1999-03-31 0:12 ` Stainless Steel Rat
1999-03-31 13:13 ` Kai.Grossjohann
1999-03-31 15:15 ` Stainless Steel Rat
1999-03-31 15:32 ` Kai.Grossjohann
1999-03-31 15:47 ` Stainless Steel Rat
1999-03-31 16:19 ` Kai.Grossjohann
1999-03-31 20:36 ` Stainless Steel Rat
1999-04-01 2:15 ` Russ Allbery
1999-04-01 8:59 ` Kai.Grossjohann
1999-03-31 16:24 ` Dmitry Yaitskov
1999-03-29 16:48 ` Shane Holder
1999-04-02 13:33 ` Lars Magne Ingebrigtsen
1999-03-09 20:11 ` Shane Holder
1999-03-09 20:47 ` bad (i.e. serious) mail problems (POSSIBLE culprit found) Shane Holder
1999-03-15 15:31 ` Shane Holder
1999-03-28 15:04 ` Lars Magne Ingebrigtsen
1999-03-09 21:54 ` bad (i.e. serious) mail problems Harry Putnam
1999-03-12 22:48 ` Shane Holder
1999-03-12 23:19 ` Kai.Grossjohann
1999-03-13 0:28 ` Shane Holder
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=99Mar30.170612est.13945-2@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).