-----BEGIN PGP SIGNED MESSAGE-----
At some point, Fu Bar had written:
On Tue, 31 Oct 1995, Tim 'pass the Prozac' Sailer wrote:
Is the Qualcom popper comercial or freeware? Where can I find it?
Free. ftp://ftp.qualcomm.com/
I just had to switch back to the pop3d that comes with Pine. We've been
using the Qualcomm popper for a few weeks, but tongiht I got a call from
someone who could not read his mail via POP3.
When I telnetted directly to the port and logged in as him, I got the
following:
Unable to process From lines (envelops), change recognition modes.
This message comes from pop_dropcopy.c, but I'm not quite sure what
causes it. The headers in his mail spool on several messages were pretty
strange:
From oyster::mrgate::"a1::lezotte, philip a."@oyster.monsanto.com Wed
Oct 18 14:21:51 1995
Return-Path: oyster::mrgate::"a1::lezotte, philip a."@oyster.monsanto.com
Received: from tin (tin.monsanto.com [137.35.4.90]) by yoda.fdt.net
(8.6.12/8.6.9) with SMTP id OAA26043 for
<lalezo(_at_)yoda(_dot_)fdt(_dot_)net>; Wed, 18
Oct 1995 14:21:49 -0400
From: oyster::mrgate::"a1::lezotte, philip a."@oyster.monsanto.com
Oct 18 14:21:51 1995
Return-Path: oyster::mrgate::"a1::lezotte, philip a."@oyster.monsanto.com
Received: from tin (tin.monsanto.com [137.35.4.90]) by yoda.fdt.net
(8.6.12/8.6.9) with SMTP id OAA26043 for
<lalezo(_at_)yoda(_dot_)fdt(_dot_)net>; Wed, 18
Oct 1995 14:21:49 -0400
From: oyster::mrgate::"a1::lezotte, philip a."@oyster.monsanto.com
Rec3 -0500
Date: Wed, 18 Oct 1995 13:21:32 -0500
Message-Id: <9510181821(_dot_)AA24008(_at_)tin>
To: "lalezo(_at_)yoda(_dot_)fdt(_dot_)net"@tin
Subject: stuff
I made a backup copy of the mail file, and then edited all the "From "
and "From: " lines, and then popper was able to handle the file.
Manually fixing people's mail isn't much of a solution though.
Pine had no trouble reading messages like this, so I decided to try Pine's
in.pop3d, and it worked as well. We had some problem many weeks ago with
in.pop3d, and that was the reason we switched to the Qualcomm popper...but
now I can't remember what the problem was.
Is this header "bad" or does it simply expose a bug in popper? Could an
/etc/procmailrc using formail perhaps be used to "clean up" headers on
incoming messages?
The real strange thing about this is you could have *no* pop3d running
and Pine will still read the mail, since it uses imapd... :)
Tim
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQB1AwUBMJbxZ13HzYfvLsqRAQFqbAMAljM2/clLGSHj3dxuOCtWq30jQo9HS+wb
6SrZUpv+H8WBJkwppvH5/n43qB33eWnA/ca5XyazeRFXk8tzaYMtli4Pitu6QiRP
9AMXjNfyOemneLpG3ynHFNdvUrxHZliS
=wt6X
-----END PGP SIGNATURE-----