* uuencode
@ Adam Myrow
` uuencode David Poehlman
` uuencode Amanda Lee
0 siblings, 2 replies; 3+ messages in thread
From: Adam Myrow @ UTC (permalink / raw)
To: speakup
David Poelhman suggests setting Outlook to uuencode. This may work
because the concept of character sets is a MIME specification. However,
any attachments you send will be encoded with uuencode which is an ancient
ancestor of modern MIME that isn't handled by a lot of mailers anymore
including Pine. So, you're better off getting your character set set to
ISO8859-1 and leaving it alone. Just thought you all would like to know.
P.S. How does one customize Redhat's firewall scripts from the command
line? I can select high, medium, or off, but selecting custom just gives
me the setup menu again. I asked this yesterday, but never saw a reply in
all the flaming about Windows mailers.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: uuencode
uuencode Adam Myrow
@ ` David Poehlman
` uuencode Amanda Lee
1 sibling, 0 replies; 3+ messages in thread
From: David Poehlman @ UTC (permalink / raw)
To: speakup
I need someone to test this attachment thing with. It seems to allow
attachments in their original form.
----- Original Message -----
From: "Adam Myrow" <myrow@eskimo.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, February 02, 2002 12:27 AM
Subject: uuencode
David Poelhman suggests setting Outlook to uuencode. This may work
because the concept of character sets is a MIME specification. However,
any attachments you send will be encoded with uuencode which is an
ancient
ancestor of modern MIME that isn't handled by a lot of mailers anymore
including Pine. So, you're better off getting your character set set to
ISO8859-1 and leaving it alone. Just thought you all would like to
know.
P.S. How does one customize Redhat's firewall scripts from the command
line? I can select high, medium, or off, but selecting custom just
gives
me the setup menu again. I asked this yesterday, but never saw a reply
in
all the flaming about Windows mailers.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: uuencode
uuencode Adam Myrow
` uuencode David Poehlman
@ ` Amanda Lee
1 sibling, 0 replies; 3+ messages in thread
From: Amanda Lee @ UTC (permalink / raw)
To: speakup
Only choices for OE6 are mime and uuencode. I did uncheck that obnoxious >
replying format.
Amanda Lee
----- Original Message -----
From: "Adam Myrow" <myrow@eskimo.com>
To: <speakup@braille.uwo.ca>
Sent: Saturday, February 02, 2002 12:27 AM
Subject: uuencode
David Poelhman suggests setting Outlook to uuencode. This may work
because the concept of character sets is a MIME specification. However,
any attachments you send will be encoded with uuencode which is an ancient
ancestor of modern MIME that isn't handled by a lot of mailers anymore
including Pine. So, you're better off getting your character set set to
ISO8859-1 and leaving it alone. Just thought you all would like to know.
P.S. How does one customize Redhat's firewall scripts from the command
line? I can select high, medium, or off, but selecting custom just gives
me the setup menu again. I asked this yesterday, but never saw a reply in
all the flaming about Windows mailers.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
uuencode Adam Myrow
` uuencode David Poehlman
` uuencode Amanda Lee
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 read-only IMAP folder(s) and NNTP newsgroup(s).