You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   317-341   342-365     
 
Author Message
24 new of 365 responses total.
mcnally
response 342 of 365: Mark Unseen   Dec 19 22:04 UTC 2000

  Unfortunately after consulting the OpenBSD release notes for a second time,
  I discovered a discouraging comment that I'd missed the first time around
  (or perhaps it was a clarification added recently..)  Anyway, apparently
  OpenBSD only currently boots on machines that have Open Firmware *AND*
  "New World" ROMs.  I'm pretty confident I do have Open Firmware, but I'm
  positive that my machine predates the "New World" ROMs..
scott
response 343 of 365: Mark Unseen   Dec 19 22:10 UTC 2000

See www.salon.com for an article about how Apple routinely changes/adds new
and backwards-incompatible things to their products... :(
gull
response 344 of 365: Mark Unseen   Dec 19 22:33 UTC 2000

It's all part of Apple's whole "we hate our customers" thing...
n8nxf
response 345 of 365: Mark Unseen   Dec 19 23:12 UTC 2000

Glad there's Microsoft!
mcnally
response 346 of 365: Mark Unseen   Dec 20 00:06 UTC 2000

  Indeed.  It's much more appropriate for the customers to hate the company!
keesan
response 347 of 365: Mark Unseen   Dec 20 03:46 UTC 2000

Uudecode worked perfectly on my mystery file.  How might this file have gotten
placed into the message encoded?  I am sure it was an accident.
gelinas
response 348 of 365: Mark Unseen   Dec 20 03:59 UTC 2000

No, it probably wasn't an accident.  It is *possible* that some mail
client may be configured to use uudecode for attachments, but it doesn't
seem likely to me.

The uu-programs (uuencode, uudecode, uucp) come from a long time ago, when
the the Internet was still small and most unix boxes were "networked" by
dial-up modems.  They probably pre-date SMTP; at best, they arose at the
same time.  (I'd guess they influenced one another, actually.)  But this
means that MIME, which came along MUCH later, wouldn't have much use for
uuencode/uudecode.
carson
response 349 of 365: Mark Unseen   Dec 20 04:49 UTC 2000

resp:341

(the song is called "Welcome Christmas."  it can be found on the Rhino
Records release _Original Television Soundtracks: Dr. Seuss' How The
Grinch Stole Christmas/Horton Hears A Who_, and maybe even on this year's
movie soundtrack.  the lyrics for both the first time the song is sung and
the reprise can be found at 
<http://www.seuss.org/seuss/welcome.xmas.html>.   they're longish, else I'd
type/paste them in.) 

keesan
response 350 of 365: Mark Unseen   Dec 20 16:11 UTC 2000

The uuencoded file was not an attachment but part of the message itself.
Arachne browser has an e-mail program that offers the choice of mime or
uuencode for attachments.    The same person who sent this also did not
realize that he could set Outlook Express not to send his 10-word message as
both ASCII and HTML (the extra 20K of HTML made the e-mail over 100K and it
was rejected - he could not see why since he was sending only an 84K file and
one line of text).  Possibly Outlook got set wrong.
jep
response 351 of 365: Mark Unseen   Dec 20 17:48 UTC 2000

re #349: Thanks!
ea
response 352 of 365: Mark Unseen   Dec 21 02:02 UTC 2000

Re #339 - The easiest way to get AOL'ers to stop sending HTML e-mail is 
to get em to switch to a better ISP *grin*  Seeing as how this solution 
is probably not feasible, I can tell you that there must be some option 
somewhere, but I don't know what it is.  AOL is a pain in the butt.
keesan
response 353 of 365: Mark Unseen   Dec 21 02:36 UTC 2000

The HTML mail was sent with Outlook Express, where it is the default, just
like it is with Netscape 4.  The ISP is not at fault here.  Netscape receives
attached uuencoded files in the body of the message, at least in a forwarded
mail.  
cmcgee
response 354 of 365: Mark Unseen   Dec 21 03:13 UTC 2000

No, Sindi, this is not an Outlook Express problem.  

This is a new problem that is not solved by changing the Outlook Express
settings.  We have worked around Outlook Express for years.  The ISP is most
certainly at fault, and a tech person at AOL said as much.  

What I'm looking for is access to an AOL technical person who can exchange
emails with me, and either a) provide a work around for all of us who have
majordomo list servers or b) leverage the AOL system to 'fix' their problem.
drew
response 355 of 365: Mark Unseen   Dec 21 03:25 UTC 2000

I know that AOL has been a bit wierd with regard to just about everything.
But I thought I heard that they were doing straight PPP..? Can't they just
use a different mail client, like Eudora? Something that doesn't do HTML?
mcnally
response 356 of 365: Mark Unseen   Dec 21 05:10 UTC 2000

  I'm sure that what cmcgee is talking about here are AOL users sending
  e-mail using AOL's software, which includes a mail client, etc..

  Yes, people with an AOL account can use AOL just as their IP provider,
  using open protocols to connect to mail servers, etc, provided by other
  entities, but the vast majority just uses the software that starts up
  when they click the AOL icon.. <shudder>
cmcgee
response 357 of 365: Mark Unseen   Dec 21 16:18 UTC 2000

Yep, mcnally's summed up the problem.  Many of our subscribers are so new to
email and the internet that talking them through the Outlook issue was a slow
process.  And now we have th AOL problem on top of it.
mdw
response 358 of 365: Mark Unseen   Dec 21 16:22 UTC 2000

Instead of fighting AOL (probably a losing proposition) why not teach
majordomo to reformat those troublesome messages?  It should be easy
enough to run them through a filter that looks for mime multi-part
messages, creates a plaintext version from the html if there's no
plaintext, and discards anything but the plaintext.
tpryan
response 359 of 365: Mark Unseen   Dec 21 17:48 UTC 2000

        
        Boycott all things AOL: AOL, Time, Warner, CNN....etc. and let
them know it.
mooncat
response 360 of 365: Mark Unseen   Dec 21 19:34 UTC 2000

Why?
keesan
response 361 of 365: Mark Unseen   Dec 21 20:42 UTC 2000

Does AOL own Netscape now?  I just learned that my ISP (account purchased in
August), which was shortly after bought out by Onemain.com, has now finished
merging with Earthlink.  So I have had three different ISPs in only a few
months, all with the same email address but different home pages.  I liked
the old one, which had links to very candid explanations of all the hardware
problems due to broken air conditioning, etc., and a members' classified
section.
cmcgee
response 362 of 365: Mark Unseen   Dec 22 00:40 UTC 2000

re 358.  Ok, sounds like a great idea.  I'll have to see if the folks who run
our server can teach me how to teach those tricks to majordomo.
keesan
response 363 of 365: Mark Unseen   Dec 22 01:04 UTC 2000

Someone working at Sprint just informed me that Sprint owns Earthlink (but
they are not owned by AOL).
scg
response 364 of 365: Mark Unseen   Dec 22 01:25 UTC 2000

Sprint owns part of Earthlink, I think.
gull
response 365 of 365: Mark Unseen   Dec 22 05:38 UTC 2000

Re #358: I took care of most of these problems on my egroups list by just
disabling all attachments.
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   200-224 
 225-249   250-274   275-299   300-324   317-341   342-365     
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss