-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, May 16, 2000, 12:38:56 PM, Peter Steiner wrote:
It could be that one mail server on the way silently converts the
encoding of the sent messages. Look for this entry in the header
X-Mime-Autoconverted: from quoted-printable to 8bit
Greetings Nick!
On Wednesday, May 17, 2000 at 08:04:02 GMT -0700 (which was 8:04 AM where you think
I live) [EMAIL PROTECTED] typed:
NA On Tuesday, May 16, 2000, 12:38:56 PM, Peter Steiner wrote:
It could be that one mail server on the way silently converts the
encoding of the sent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, May 17, 2000, 8:22:25 AM, phil wrote:
Do you sign the keys after you import them? If not, then they will
look Invalid.
Yes I know Phil, but the problem is not that the keys are showing as
"Invalid", which only indicates that you
Greetings Nick!
On Wednesday, May 17, 2000 at 08:35:11 GMT -0700 (which was 8:35 AM where you think
I live) [EMAIL PROTECTED] typed:
NA On Wednesday, May 17, 2000, 8:22:25 AM, phil wrote:
Do you sign the keys after you import them? If not, then they will
look Invalid.
NA Yes I know
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm involved in an ongoing discussion as to why TB!, amongst other Mail
Clients, always reports a very high percentage PGP Signature generated via
Eudora, as "bad", indicating that the message content had been altered
sometime after the message was
Hello Nick
On Tue, 16 May 2000 09:41:11 -0700, Nick Andriash wrote:
Content-Transfer-Encoding: 7bit
as seen on TB's headers
Content-Transfer-Encoding: 8bit
as seen on the header from Eudora 4.3.2 Beta 6
Would that difference have anything to do with why TB! reports those PGP
signatures
6 matches
Mail list logo
