Re: [Evolution] Bcc exposes recipients



My mistake -- I hope.  In the event that there are no recipients in the
To: or CC: fields, Pegasus warns you that you have not designated a
recipient beyond the BCC, and asks if you want to send anyway.  If you
reply yes, it just sends one message.

What happens with Evolution and the exposing servers when there are
recipients in the "visible" to: or CC: fields?  Is the Apparently-to:
header added in that instance?

When you address a message in Pegasus offline, only one message is
visible in the outbox queue.  When you go online and send the queue, the
mailer generates separate messages for the visible recipients and for
the blind recipients.  I believe that all blind recipients get the same
message, and I never rely on a BCC recipient not knowing the other BCC
recipients, though that may be the case.  I believe that there is a
setting on whether the BCC field is displayed on the BCC copy, but its
been a long time since I checked that option.

Art

On Fri, 2003-04-18 at 13:11, Mark Gordon wrote:
Note that we're discussing the case in which there *isn't* anyone in the
To: or Cc: fields.  To whom does Pegasus send a second message in this
case?

-Mark Gordon

On Fri, 2003-04-18 at 13:04, Arthur S. Alexion wrote:
This is a bug with monstrous practical consequences.  That should never
be allowed to happen -- warning or not.

I know that Pegasus (Windows) actually generates two messages one for
the visible To's and cc's, and another separate one for the bcc's.  I
thought all mailers did this, and if servers otherwise betray
confidences, all mailers should.

This could be a reason to stop using Evolution for sensitive mail.

Art

On Fri, 2003-04-18 at 12:30, Mark Gordon wrote:
On Fri, 2003-04-18 at 10:48, John Schmidt wrote:
I was wondering if there's a good reason why Evolution
can not truly hide the list of Bcc recipients in a message?

If I send mail to a Bcc list and don't have recipients in the
To: or Cc: lines, then the message is sent but the
header info contains a list of who was in the Bcc line.

Is this a mail server issue, or an  evolution issue?

John

It's a mail server issue.  In the most recent 1.3.2.99 snaps, Evolution
will warn you that servers may add an Apparently-To header.  I'm not
sure how long that warning has been there.
 
-Mark Gordon

_______________________________________________
evolution maillist  -  evolution lists ximian com
http://lists.ximian.com/mailman/listinfo/evolution
-- 
Arthur S. Alexion <arthur alexion com>
Arthur S. Alexion LLC




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]