On 7/23/2012 8:55 AM, MaryL wrote:
[...]
In all this discussion, we have no evidence
of what you inserted into your "To:" field,
and of what anything inserted into your "To:" field
actually became when sending your message.
We also heard that people to whom you want to write
did not receive your messages, but did we ever hear
what became of the non-received messages? Did you
ever receive them back, as "undeliverable," say?
How do you know what addresses were really sent out?
How do you know that your messages are not stuck
in a "spam" quarantine somewhere, or discarded?
Did you add a "Bcc" to yourself, to see whether
you even received a copy back to your own "In" mailbox?
Why don't we stop guessing and start getting some concrete info?
To begin with, how about making this setting:
Menu: Tools > Options
Category: Miscellaneous
Setting: Automatically expand nicknames [yes]
When you now select recipients from your address book,
your To/Cc/Bcc fields will not remain showing only "nicknames,"
but those nicknames will be immediately "expanded"
(replaced with the actual header info which will be sent).
You will then be able to see whether the addresses you only
assume are being used are actually being substituted and used,
and if not, you'll see what your To/Cc headers actually look like
when the message is being sent.
An "all bytes sent" log of your connection to the outgoing (SMTP) server
would be even better, because it will contain one individual command
for every real address (including even Bcc), like this:
MAIL FROM: <your@address>
RCPT TO: <one@recipient>
RCPT TO: <next@recipient>
[...]
RCPT TO: <last@recipient>
DATA
[message to be delivered goes here, starting with its headers]
. <=== a line containing a single period is the end of "data"
Note that in all the lines before the DATA command,
the addresses are not cluttered up with names or punctuation,
as in the composed headers -- that is, if you composed
To: "Sally (My Dear Sister) Roberts" <
sa...@example.com>
then one of the "rcpt to" commands to the server would be simply
RCPT TO: <
sa...@example.com>
Servers actually pay no heed to the composed To/Cc headers
which follow the "DATA" command -- they route messages only to
the "raw" addresses given to them in the "RCPT TO" commands,
so that's the ultimate proof of whether or not
a message ever got out to a server
directed to the destination address(es)
that you intended it to go to.
Otherwise, mistakes such as bad punctuation or parentheses
could be causing an entry in an address book
to not actually mean what you were thinking when you typed it,
or could cause an entire line of "addresses" to be ignored,
"swallowed up" into a quoted string or (inside parentheses), say.
By the way, "SMTP" stands for Simple Mail Transfer Protocol,
and you can see, in the example above, how extremely simple it is,
consisting of telling the server the sender's plain address,
then every individual recipient's plain address,
then the "data package" which every recipient is to identically receive.
Each server then forwards messages to the next server "closer" to
each final recipient, using the exact same protocol, until, hopefully,
a copy arrives at each individual destination mailbox.
If you'd like to capture that level of explicit dialog going to the server,
to leave no doubt whatsoever as to whether your message starts out properly
on its journey, just turn on Eudora's excellent logging, which Eudora makes
easy while other programs leave you merely guessing and groping in the dark.
Logging instructions for "classic" Eudora:
Windows: <
http://eudorabb.qualcomm.com/showthread.php?t=476>
Mac: <
http://eudorabb.qualcomm.com/showthread.php?t=437>
<
http://eudorabb.qualcomm.com/showthread.php?t=1546>
When I was a kid, I was told to stop mumbling and speak clearly,
or else no one will understand what I want or need,
and that's pretty much the same as my perpetual message on forums --
replace vague talk with explicit and clear details and settings,
specific actual steps you tool and data you entered,
specific and precise error messages, use screen images and logs --
a doctor can't transform a vague "I'm not well" into a diagnosis and cure,
but after using a thermometer, blood pressure gauge,
sending a blood sample for lab analysis, seeing what the nose, throat and ears
actually look like under bright light, hearing actual chest sounds,
getting an X-ray/CAT scan/MRI, etc., only then can (s)he make an accurate
diagnosis, followed by direct and effective treatment and relief.
Similarly, our collective self-government is ineffective
unless we have access to all the details of who influenced whom,
did what, paid for what, etc., with institutions collectively known as
"press" and "media" reporting complete details, to a public
which pays sufficient time and attention, and educates itself
to understand what is going on, which seems to barely happen at all.
--