Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Eudora / December 2007



Tip: Looking for answers? Try searching our database.

How to omit sending attachments to CC address?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Martin S. - 17 Dec 2007 03:55 GMT
Hi there,

is there a way, perhaps in x-settings, to set Eudora to only send
attachments to the address in the To field, but omitting them from other
recipients listed in CC?

I often need to dispatch large print files to a service bureau, cc-ing
the client, so they know it's gone. However I would like to avoid
sending the files to the client as well.

Signature

Cheers  Martin

Bill Cole - 17 Dec 2007 04:28 GMT
> Hi there,
>
[quoted text clipped - 5 lines]
> the client, so they know it's gone. However I would like to avoid
> sending the files to the client as well.

You are wanting email to work in a way it does not work.

Attached files are an integrated part of a message. If you need to send
different messages (i.e. one with files and one without) to different
recipients, you need to actually send different messages.

Signature

Now where did I hide that website...

Martin S. - 17 Dec 2007 04:53 GMT
> You are wanting email to work in a way it does not work.

Perhaps and I can see the advantages of how this is being handled
currently.

What got me thinking about this issue, is how different email clients
seem to handle replies.

I often get replies that not only include my entire, original message,
but also all the attachments, which is rather annoying.

Other times the attachments are omitted as I would expect.

This lead me to assume, that there might be a way to somehow prioritise,
who to send attachments to in the first place. I certainly would
appreciate, if there was a setting somewhere.

Does that make sense?

Signature

Cheers  Martin

Kathy Morgan - 17 Dec 2007 07:39 GMT
> This lead me to assume, that there might be a way to somehow prioritise,
> who to send attachments to in the first place. I certainly would
> appreciate, if there was a setting somewhere.

You could set up a filter on outgoing mail that will sound an alert and
change the message status to timed queue for messages addressed to or
copied to certain addresses, so that at least you would be reminded if
you try to send a message with attachments to someone who shouldn't get
them. I think "Any header" contains "Content-Type: multipart/mixed"
should catch the messages with attachments.

I would definitely first test this with some messages sent to yourself,
to make sure the filter acts _before_ the message is sent rather than
after--I'm not sure when filtering takes place on outgoing messages.

Signature

Kathy - If you're reading this in your web browser from Google or
similar forum, NNTP "newsreaders" are a better way to access the
content. <http://www.aptalaska.net/~kmorgan/how-it-works.html>
Links to NNTP newsreaders at <http://www.newsreaders.com/>

Bill Cole - 18 Dec 2007 05:41 GMT
> > You are wanting email to work in a way it does not work.
>
[quoted text clipped - 8 lines]
>
> Other times the attachments are omitted as I would expect.

That's a demonstration that different email clients and different people
behave differently.

> This lead me to assume, that there might be a way to somehow prioritise,
> who to send attachments to in the first place. I certainly would
> appreciate, if there was a setting somewhere.
>
> Does that make sense?

It makes high-level conceptual sense, but since Internet email was
designed to conserve bandwidth at the expense of flexibility, it doesn't
really make sense as a natural feature for a mail client. When you
compose a message in Eudora, it is a single message with a single set of
recipients. In order to send different content to different recipients,
Eudora would have to split the one conceptual message into distinct
actual messages when actually sending it.  It's an interesting concept
for a mailer feature, but I'm not aware of any mailer that has that sort
of behavior.

Signature

Now where did I hide that website...

Kathy Morgan - 17 Dec 2007 07:39 GMT
> You are wanting email to work in a way it does not work.
>
> Attached files are an integrated part of a message. If you need to send
> different messages (i.e. one with files and one without) to different
> recipients, you need to actually send different messages.

For the OP: An easy way to do that in Eudora is to send the email, with
attachment, to the "To" recipient.  After it has gone, select the
message and choose "Send Again" from the Message menu. Drag the
attachment to the trash, then change the address to include all those
who should receive a cc without the attachment.

Signature

Kathy - If you're reading this in your web browser from Google or
similar forum, NNTP "newsreaders" are a better way to access the
content. <http://www.aptalaska.net/~kmorgan/how-it-works.html>
Links to NNTP newsreaders at <http://www.newsreaders.com/>

Martin S. - 17 Dec 2007 19:01 GMT
> For the OP: An easy way to do that in Eudora is to send the email, with
> attachment, to the "To" recipient.  After it has gone, select the
> message and choose "Send Again" from the Message menu. Drag the
> attachment to the trash, then change the address to include all those
> who should receive a cc without the attachment.

Thanks Kathy, for your thoughts.

This is in fact what I've been doing. I was hoping for a settings twaek
to avoid those extra steps.

Signature

Cheers  Martin

John H Meyers - 18 Dec 2007 09:53 GMT
On Sun, 16 Dec 2007 22:28:57:

Martin S:

>> I often need to dispatch large print files to a service bureau, cc-ing
>> the client, so they know it's gone. However I would like to avoid
>> sending the files to the client as well.

Bill Cole:

> You are wanting email to work in a way it does not work.

> Attached files are an integrated part of a message.
> If you need to send different messages
> (i.e. one with files and one without) to different recipients,
> you need to actually send different messages.

Just to elaborate, the basic protocol (SMTP) for sending internet mail
was developed even before attachments existed; in that protocol,
the client first tells the SMTP server the addresses of every
individual recipient -- not via "headers," but by sending one
command per address, making no distiction whatsoever
between what you think of as "To:" vs. "Cc:" vs. "Bcc:"

To the SMTP server, there is only one "class" of recipient
(very democratic, eh?) -- this also explains how "Bcc:" works,
in that it is simply those recipients who are never mentioned
in the headers, anyway; in fact, none of the headers
which you may fill in when composing is required at all.

Once all that is completed, the client then appends the "message,"
including all of what you think of as "headers," but which
does not need to be interpreted by the SMTP server
(servers may pay slight attention, perhaps supplying
a "Message-ID:" header if the client did not, for example).

Other than inserting its own "Postmark" (a "Received:" header)
in front of that entire "data" stream, the SMTP server otherwise
simply passes this uninteresting "data" along, in exactly the same way,
to the next appropriate server enroute, until it finally reaches
a server which "knows" a recipient,
which holds it for pickup via POP or IMAP,
much the same way a postal letter is handled,
enroute to a final P.O. Box for customer pickup.

The notion of "attachments" was developed simply by inventing
a header which defines a "boundary string" that the final recipient
will interpret upon receipt as separating sections of the message body,
with each section containing its own header(s) that describe itself.

Although snoopy "mail screeners" may dig into this and inspect more closely,
to sniff out spam and malware, for example, this is not the SMTP server's
basic job -- it just packs mail going to the same next place into bags,
and doesn't much care about what's inside each letter (or package).

This is the standard system which all email clients (and servers)
must adhere to, in order to participate in a global system.

So long as the entire content of a message is to be delivered
identically to all recipients, it can be transmitted just once
to the SMTP server, preceded by a list of all addresses;
otherwise it needs to be transmitted again, separately,
if even one word (or attachment) is to be varied.

Email clients used by spammers nowadays do just that,
to insert "Dear username@someplace" or random texts,
hoping to defeat spam scanners looking for identical messages,
and to avoid suspicion by one message being addressed to many recipients,
but personal email clients are already confusing enough to their users,
and probably don't want to become any more complex.

In fact, I'm beginning to suspect that the handwritten Christmas card
I just received from "The Edwards Family" (one of whom
is running for U.S. President, and currently focusing on our state)
may actually not have been written just for me,
particularly since so many other people have shown me their identical card :)

--
Tim Streater - 18 Dec 2007 10:24 GMT
> > Hi there,
> >
[quoted text clipped - 11 lines]
> different messages (i.e. one with files and one without) to different
> recipients, you need to actually send different messages.

I think the OP would like (as would I) *Eudora* to send different
messages, transparently. I could imagine an acc: line for those in "cc:"
whom you would like the attachment to go to (i.e. as well as to the To:
recipients).

I view it as the user-agent's business to organise that.

Clearly this cannot be done with existing Eudora but it's a feature we
should be pushing for in user-agents.
magdalena - 18 Dec 2007 16:26 GMT
> > > Hi there,
> > >
[quoted text clipped - 21 lines]
> Clearly this cannot be done with existing Eudora but it's a feature we
> should be pushing for in user-agents.

I'd like that feature to be added too. Make it like the traditional
paper letter method. The main recipient would of course get the
attachment. At the bottom of the letter we would type: cc: John Doe
(w/attachment), Mary Doe (w/o attachment); bcc: Sue Doe (w/attachment).
Martin S. - 18 Dec 2007 19:00 GMT
In article
<magdalenabung-3C97DD.11265718122007@comcast.dca.giganews.com>,

> > Clearly this cannot be done with existing Eudora but it's a feature we
> > should be pushing for in user-agents.
[quoted text clipped - 3 lines]
> attachment. At the bottom of the letter we would type: cc: John Doe
> (w/attachment), Mary Doe (w/o attachment); bcc: Sue Doe (w/attachment).

Exactly. I think it would be great to have a button like the one to
choose a signature, to toggle this behaviour.

Signature

Cheers  Martin

John H Meyers - 18 Dec 2007 20:53 GMT
On Tue, 18 Dec 2007 04:24:16 -0600:

> I think the OP would like (as would I) *Eudora* to send different
> messages, transparently. I could imagine an acc: line for those in "cc:"
> whom you would like the attachment to go to (i.e. as well as to the To:
> recipients).

So that it will by *default* NOT include any attachments to "Cc:"?

"Dear John, thanks for copying me the thrilling news about your new baby,
but the photos weren't actually included -- could you please re-send them?" :)

What if there are multiple attachments;
should each one have its own independent
"to Cc, or not to Cc" status?

Even HTML in body is, of course, actually an "attachment,"
and what about all other "in-line" content?
Who gets, and who doesn't get, each one?

Will there be different message-IDs on each message sent
with a different combination of attachments?
(standards do require unique IDs on the actual transmissions,
so it would actually be necessary
to save as independent messages anyway)

What if an SMTP server acknowledges the first of two required
independent messages, but can't complete the second?
What is then the status of a "half sent" message?
(and what will happen when you try to re-send it?)

> I view it as the user-agent's business to organise that.
>
> Clearly this cannot be done with existing Eudora
> but it's a feature we should be pushing for in user-agents.

Count me as pushing the other way :)
Martin S. - 18 Dec 2007 21:41 GMT
> Count me as pushing the other way :)

Why if it was optional?

Signature

Cheers  Martin

John H Meyers - 20 Dec 2007 02:16 GMT
On Tue, 18 Dec 2007 15:41:42 -0600:

JHM
>> Count me as pushing the other way :)

Martin S:
> Why, if it was optional?

The tendered proposition appeared to mean
assuming _by_default_ that normal "Cc:" recipients
do not get attachments, and _that_ struck me
as something worthy of a remark (or a rant :)

In any case, the nature of email transport (SMTP)
requires separate messages to be sent,
whenever content differs,
as I think everyone realizes and acknowledges,
so what next to consider
is what sort of user interface
might facilitate the creation of such extra messages,
perhaps saving a step from just using the existing "Send again."

To be a worthy thing, it should really save more effort than it takes,
should be flexible enough to easily be varied between users,
and even between one message and the next, for that matter,
and also should not "weigh down" the interface for all those others
who haven't any interest in this sort of thing;
it should also not create a pitfall to be fallen into,
by anyone who doesn't realize the consequences,
or who might readily forget to turn it off when not wanted.

The design of human interfaces with technology is quite an art,
even if called "Human Factors Engineering,"
and I wanted to stir some thoughts about it, using this example.

It's like all fields in life -- we have our personal perspective,
others have their own.  To devise the finest way
for all to achieve, as much as possible,
their diverse desires, weighted with appropriate values,
with adverse effects as few as possible,
is the great balancing act of civilization,
requiring the broadest awareness.

--
Tim Streater - 18 Dec 2007 23:04 GMT
> On Tue, 18 Dec 2007 04:24:16 -0600:
>
[quoted text clipped - 4 lines]
>
> So that it will by *default* NOT include any attachments to "Cc:"?

or the other way around if you prefer. Personally I don't see why *any*
cc: person should get the attachments. If they were supposed to get
them, they'd be in the To: line.

This would also have the salutary effect of making folks pay attention
to the difference between To: and Cc:. To me, being on a cc: means I
should be peripheral. But then some bugger does this:

From: John Doe
To:   John Doe
Cc:   Tim Streater and others

WTF am I supposed to make of this?

> "Dear John, thanks for copying me the thrilling news about your new baby,
> but the photos weren't actually included -- could you please re-send them?" :)

Well that'll learn him, won't it? See above.

> What if there are multiple attachments;
> should each one have its own independent
> "to Cc, or not to Cc" status?

I'd group them all together for this purpose.

> Even HTML in body is, of course, actually an "attachment,"
> and what about all other "in-line" content?
> Who gets, and who doesn't get, each one?

To me an attachment is distinct from the mail body. How it's handled
internally doesn't concern or interest me at this point.

> Will there be different message-IDs on each message sent
> with a different combination of attachments?
> (standards do require unique IDs on the actual transmissions,
> so it would actually be necessary
> to save as independent messages anyway)

I don't care, d'ye see? I've never paid attention 'em anyway. If there
need to be two messages then so be it.

> What if an SMTP server acknowledges the first of two required
> independent messages, but can't complete the second?
> What is then the status of a "half sent" message?
> (and what will happen when you try to re-send it?)

Let the agent sort that out. If it has to send two messages it can treat
them independently for this purpose.

We're in this situation now anyway. From time to time I get mail
returned because I mistyped one out of several addressees. I never yet
have been told whether the mail was delivered OK to *everyone else*, so
in practice I resend the whole damn thing.

> > I view it as the user-agent's business to organise that.
> >
> > Clearly this cannot be done with existing Eudora
> > but it's a feature we should be pushing for in user-agents.
>
> Count me as pushing the other way :)

John, you disappoint me. I have lost count of the number of times I
receive attachments I don't want, because I am in the cc: of a thread I
am mildly supposed to follow, by order. They're a bloody nuisance and a
waste of bandwidth.

Much better if the sender has options about whom should receive the
attachments.
Martin S. - 19 Dec 2007 02:43 GMT
> Much better if the sender has options about whom should receive the
> attachments.

Thanks Tim, that was a very thorough reply and I agree on all accounts.

Signature

Cheers  Martin

John H Meyers - 20 Dec 2007 01:45 GMT
>> So that it will by *default* NOT include any attachments to "Cc:"?

> or the other way around if you prefer.

It would _have_ to be a special "Cc (without attachments):"
because the world is already completely accustomed
to the fact that _everyone_ addressed normally,
in one single message, receives exactly the same content,
as has always been the case, as long as there has been email.

> Personally I don't see why *any* cc: person should get the attachments.
> If they were supposed to get them, they'd be in the "To:" line.

You certainly "hear a different drummer"; what "Cc:" means
derives from history, general usage, and convention
(perhaps even office manuals and "style" manuals in some cases),
and I believe that to most people,
it denotes other people who should see something as an "FYI,"
whereas "To:" means either persons more directly concerned,
or simply whoever sent you a message to which you are replying
("Cc:" then signifying your widening the audience
to others who were not originally included),
but has never meant that they should get only the text,
and be automatically excluded from receiving all attachments
(heaven forbid!)

> This would also have the salutary effect of making folks pay attention
> to the difference between To: and Cc:. To me, being on a cc: means
[quoted text clipped - 3 lines]
> To:   John Doe
> Cc:   Tim Streater and others

> What am I supposed to make of this?

That's a matter of an annoying behavior, as you see it,
between you and the sender; no email client
will settle personal issues for you,
and attempts to fix such things by adding
equally annoying contradictory behaviors to software
will only compound the problems, much as does
the ever popular "let's quick-fix this by adding a new law"
(or by throwing out the folks in office,
to get new ones whose results may be just as unsatisfactory).

>> Will there be different message-IDs on each message sent
>> with a different combination of attachments?
>> (standards do require unique IDs on the actual transmissions,
>> so it would actually be necessary
>> to save as independent messages anyway)

> I don't care, d'ye see? I've never paid attention 'em anyway.
> If there need to be two messages then so be it.

>> What if an SMTP server acknowledges the first of two required
>> independent messages, but can't complete the second?
>> What is then the status of a "half sent" message?
>> (and what will happen when you try to re-send it?)

> Let the agent sort that out. If it has to send two messages
> it can treat them independently for this purpose.

That's exactly what would have to be done -- the nature of SMTP
(and then of unique Message IDs and individual "status" per message)
necessitate creating separate messages for any distinct content,
each of which must be sent (and tracked) separately.

Eudora's "Send again" is ideally simple (and flexible) for this,
allowing any conceivable variation of content
per separate group of addressees,
so I perceive the "marginal utility" of a highly rigid
"don't send attachments to anyone but 'To:' list" option
to be very low (or should "Bcc:" get the attachments, after all,
because some people BCC *themselves*, in order to save
"sent" messages on separate computers that are used
with the same POP account :)

This could be done -- just round up anyone versed in writing "plugins,"
and have more tool buttons added within the message composition window,
for every sort of gimmick which one wants to add
(the plugin will still have to create multiple messages for you,
whenever messages having different content are created,
because each message must be independently transmitted via SMTP,
and each will consequently have its own fate, its own history and status).

The plugin's own options could even offer a checkbox for each recipient
field (To, Cc, Bcc), indicating exactly which ones get attachments,
allowing both you and other people of differing personal needs
to get some use out of the same plugin,
as well as not need to uninstall the plugin to disable it :)

> We're in this situation now anyway. From time to time I get mail
> returned because I mistyped one out of several addressees. I never yet
> have been told whether the mail was delivered OK to *everyone else*,
> so in practice I resend the whole damn thing.

That isn't necessary -- thanks to internet standards about the
behaviors of every agent (Eudora, intermediate and final SMTP servers),
there is absolutely no ambiguity about this.

A message not accepted from Eudora by your _own_ SMTP server
(and marked "error, not sent") is delivered to NO ONE,
so you should indeed re-send those, after correcting bad addresses,
while a message that is accepted and marked "sent" by Eudora
has had ALL its addresses accepted, so you should assume delivery to all,
except those from whom you subsequently receive "undeliverable" notices.

For any initially _accepted_ addresses that subsequently "bounce,"
the forwarder is obliged to notify you by separate return mail,
listing every address that was undeliverable;
messages addressed to scattered domains may thus receive independent
"bounce" responses, but all refused addresses from any one domain
are usually grouped into one "undeliverable" return message --
the same grouping, in general, as in the originally sent message.

To recapitulate, if your _own_ SMTP server already detects
any illegally formatted addresses, or if it recognizes a "local domain"
address that isn't valid, it will immediately tell Eudora,
during the preliminary phase, and Eudora will abort that message,
never proceeding to transmit the content at all, hence in that case,
and only that case, NO ONE is sent anything,
and Eudora immediately indicates the error to you directly,
as well as indicating that the message remains UNSENT (to anyone).

If your own SMTP server accepts everything, however, then Eudora
marks the message as SENT (to everyone); just as with paper mail,
you assume it will get there, or else a *copy* will come back to you,
in your Inbox, marked "undeliverable, return to sender."

The initial conversation with your own SMTP server is always
an "all or nothing" deal -- does that simplify things?

> I have lost count of the number of times I receive attachments I don't want,
> because I am in the cc: of a thread I am mildly supposed to follow, by order.
> They're a bloody nuisance and a waste of bandwidth.

> Much better if the sender has options
> about who should receive the attachments.

They DO have the option, BUT, because of the very nature of mail,
it requires extra attention from them, exactly the same as
when stuffing envelopes, if you don't want everyone
to get the same enclosures, you have to decide for yourself
whose envelopes will get which enclosures,
and issue detailed instructions to those who will stuff your envelopes,
with a separate list of recipients for each distinct "manifest" of contents.

No email program, with "one choice for everybody,"
is going to be able to customize for the needs of diverse users;
if they do exactly what you prefer, it will be what someone else does not.

I think that the "plugin" idea, with some flexible options,
could suit you (and others), without simultaneously "breaking" the product
for everyone else who would *not* want any existing behavior to change;
it would also not unnecessarily create more complexity for existing
"mainstream" users who like what already exists.

It may be a good thing that we can all propose ideas to developers,
but that developers can (hopefully) probe more deeply,
and perhaps find something even better for all.

As with what our kids request of us, perhaps :)

--
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.