|
|
| Author |
Message |
| 25 new of 170 responses total. |
other
|
|
response 125 of 170:
| 
Nov 17 21:39 UTC 2001 |
Well, as to why it wasn't separated, I'd guess pine can parse messages in
html, and since the content-type header said it was html, that's how pine
treated it (displayed inline).
|
gelinas
|
|
response 126 of 170:
|
Nov 17 21:56 UTC 2001 |
"X-Sender:" Is used by *many* mail packages, not just Microsoft.
(It gained popularity because of one particular person, who refused to fix
his very well distributed software, when desktop mail clients were first
being written. He refused to use the "From:" header over the "Sender:"
header, so people had to use "X-sender:" instead. All of the X- headers
are defined as "non-standard".) The "X-Mailer:" header is *much* more
useful for identifying the originating mail client.
I'll just give up on "attachment" versus "message". It's not really
accurate, but I guess it's as informative as any other description.
The whole thing is a "message" with several "parts". Some parts look
like the enclosures that are fairly common in business correspondence,
functioning much the same way, so they get called "attachments", even
though they are just part of the message text. The only reason I care is
instances like this, when the parts are not properly identified by the
originating software. Understanding the difference can help debug the
problem.
|
rcurl
|
|
response 127 of 170:
|
Nov 17 22:01 UTC 2001 |
Now we may be getting somewhere. If a message is sent in html to pine, it
just displays it as a text message (OutlookExpress would recognize it is
html and display it that way). In this case, the message is not explicitly
html - there is just a touch of html in it after decoding. Pine would not
know to decode it because it wasn't an attachment, but if it is true that
pine reads that content-type literally, then this would happen. Voila?
|
gelinas
|
|
response 128 of 170:
|
Nov 17 23:52 UTC 2001 |
Rane, Pine can decode Base64. So it decoded the message and displayed it
to you, as text/html. Unfortunately, the message was NOT a "text/html"
document; it was a Microsoft Word document. I suspect that, had
you scrolled down, you would have eventually gotten through the Word
formatting stuff to the text; that's what happens when I use other editors
to display Word documents, anyway.
Why would a corporation use software that would generate this kind of
mistake? I don't know; I can only suggest asking them.
|
mdw
|
|
response 129 of 170:
|
Nov 18 01:50 UTC 2001 |
Wait, this is an *automated* response to mail? This was almost
certainly not generated by a real mail client, but was probably
generated by some sort of script (perhaps written in vbs or perhaps
perl) very likely written by an expensive consultant, who may have been
in a hurry to get off to his next golf appointment.
|
rcurl
|
|
response 130 of 170:
|
Nov 18 02:45 UTC 2001 |
Yes, it was an automated response.
Joe, the "message" had the heading (I showed that) and ca. 20 lines
of Base64 encoding - nothing further down. MacLinkPlus recognized it
as a MIME encoded archive for a PC file. Decompressing it with MLP
gave a PC MS-WORD document, but with an imbedded link. The link
works at this stage. So it is both an MS-WORD and an html document.
It does open in a "frame" format, although there is nothing in the
left-hand frame.
|
gelinas
|
|
response 131 of 170:
|
Nov 18 05:46 UTC 2001 |
Oh, well. The only such message I can find right now Pine displays. As it
happens, though, it is an application/octet-stream, so Pine can't display
it all. It does seem to decode the Base64, though.
|
keesan
|
|
response 132 of 170:
|
Nov 18 22:54 UTC 2001 |
Last time I tried to access my phone bill any time I got a new page it would
blink somewhere between 2 and 5 times (with the new lynx).
|
russ
|
|
response 133 of 170:
|
Nov 23 04:15 UTC 2001 |
utmp is messed up: it doesn't have ttyp1 in it, according to amin.
amin is also screwed up: if the user's tty isn't in utmp, it fails
to run the command it's supposed to, breaking things that don't need
to be broken.
|
carson
|
|
response 134 of 170:
|
Nov 28 22:26 UTC 2001 |
I have frequently encountered a problem where my mail here ceases to exist.
It returns in later sessions without explanation of its previous whereabouts.
|
jhudson
|
|
response 135 of 170:
|
Nov 28 22:30 UTC 2001 |
I would assume mail.local had blocked for a time.
|
carson
|
|
response 136 of 170:
|
Nov 28 22:32 UTC 2001 |
I see now that my inbox path varies between ~/carson and ~/c/a/carson.
I have not seen a reason for either selection, and assume the decision
of the various mail clients which I use is arbitrary, although I also
predict said assumption runs contrary to the intuition of those more
closely attuned to the behaviour of various operating systems.
|
gelinas
|
|
response 137 of 170:
|
Nov 29 06:18 UTC 2001 |
Hmmm . . . ~carson is a short form of /a/c/a/carson Do you have sub-directory
named "carson"?
Which mail clients do you use?
|
carson
|
|
response 138 of 170:
|
Nov 29 06:50 UTC 2001 |
I suspect I should not have been so lazy in posting response #136.
The actual variance was between /var/spool/mail/carson and
/var/spool/mail/c/a/carson. I have since specified settings in pine
to seek the longer address. I frequently use either mail or !mail,
which to my understanding access slightly different programs. I also
use pine on occasion, as implied by an earlier sentence.
To my knowledge, I do not have an eponymous subdirectory. I also use
"bbs" as my shell, which periodically creates manageable inconveniences.
|
rcurl
|
|
response 139 of 170:
|
Nov 29 06:57 UTC 2001 |
This isn't much of a problem but.... when I log out, I originally used
control-C at the re-login prompt, and my connection dropped. Then some
months ago that stopped working, so I went to control-D-return. I
now find that control-C is working again for dropping the connection.
What was changed that caused this change in logout behavior?
|
gelinas
|
|
response 140 of 170:
|
Nov 29 07:02 UTC 2001 |
Carson, here is something you might find interesting:
Respond, pass, forget, quit, or ? for more options? !ls -l /var/spool/mail
total 31
drwx------ 2 root daemon 512 Feb 25 2000 HOLD
-rw-r--r-- 1 root wheel 105 Mar 24 1998 README
. . .
Respond, pass, forget, quit, or ? for more options? !less
/var/spool/mail/README Mail now lives in:
/var/spool/mail/X/Y/LOGINID
where X and Y are the first two letters of your loginid.
|
carson
|
|
response 141 of 170:
|
Nov 29 07:07 UTC 2001 |
I do not mean to sound rude or unappreciative, but I already had figured
that much out. I find it more curious that the mail clients do not always
remember the change.
|
gelinas
|
|
response 142 of 170:
|
Nov 29 07:21 UTC 2001 |
OK. I was thinking that one client was consistently using one form, while
a different client was consistently using the other form, which would indicate
that the configuration of the ailing client was set before the change-over.
I don't know when the directory structure was changed, but it was certainly
before 24 Mar 1998. Often, config files live in our home directories, where
sysadmins shouldn't be mucking with them.
|
mdw
|
|
response 143 of 170:
|
Nov 29 08:17 UTC 2001 |
Pine and sshd are both "problems" for mail. sshd doesn't set MAIL (it
should). Pine has opaque logic. We mostly got it to work with $MAIL,
but there are a few rough edges we never completely sorted out. For
various reasons, we need to update sshd soon; it's on my "todo" list.
|
gelinas
|
|
response 144 of 170:
|
Nov 29 13:26 UTC 2001 |
I note that I do not set $MAIL in my "dot" files; I also see that it is set
in /usr/local/etc/global.login and /usr/local/etc/global.profile, but with
a comment indicating it was added because ssh wasn't getting right. Where
is that variable normally set?
|
ea
|
|
response 145 of 170:
|
Dec 3 04:58 UTC 2001 |
Logged in tonight, via Backtalk. In the area where it displays my
conference hotlist, next to the Sports Conference, there was text
(conference does not exist) (yes, the parens were there too). What
happened to Sports? I didn't see any announcements.
|
gelinas
|
|
response 146 of 170:
|
Dec 3 05:18 UTC 2001 |
It's available through picospan right now.
|
ea
|
|
response 147 of 170:
|
Dec 3 12:42 UTC 2001 |
I can get to the conf if I type the name in the box, but in the
"hotlist" it says it does not exist.
|
janc
|
|
response 148 of 170:
|
Dec 3 23:56 UTC 2001 |
Interesting. I'm noticing a variety of tiny bits of flakiness on parts
of Backtalk I didn't think I'd changed. I'll look into it.
|
janc
|
|
response 149 of 170:
|
Dec 4 00:04 UTC 2001 |
OK, ea's .cflist has "Sports" in it, rather than "sports". Backtalk
doesn't like the upper case letter. I'll put it on the list of things
to fix.
|
