According to RFC 2822 there are several acceptable methods of readers seeing or not to whom a BCC copy has been sent. Pegasus seems to use a method similar to this one:
" In the second case, recipients specified in the "To:" and "Cc:"
lines each are sent a copy of the message with the "Bcc:" line
removed as above, but the
recipients on the "Bcc:" line get a
separate copy of the message containing a "Bcc:" line."
i.e. In the case of Pegasus 4.51 and presumably 4.52 The BCC recipients see each of the addresses the BCC was sent to .
Would it be possible to change this method in a future version so that the addressed BCC readers do NOT receive the addresses of the others??
Similar to this perhaps: (Quoted From the RFC)
" In the first case, when a message containing a "Bcc:" field is
prepared to be sent, the "Bcc:" line is
removed even though all of
the recipients (including those specified in the "Bcc:" field)
are sent a copy of the message."
I imagine this would mean Pegasus would have be changed to send a copy to the server for each BCC address as well as a copy for the To: and CC: addresses, each with the BCC information removed.
I understand that a distribution list can achieve the anonymity being suggested here but for only few addresses it seems like overkill (unless, of course, the same people are addressed time after time).
Stuart
Montreal, Canada
Longtime Peg user (~15years.)
<p>According to RFC&nbsp; 2822 &nbsp;&nbsp;&nbsp; there are several acceptable methods of&nbsp; readers seeing or not to whom a BCC copy has been sent. Pegasus seems to use a method similar to this one:</p><p>" In the second case, recipients specified in the "To:" and "Cc:"
lines each are sent a copy of the message with the "Bcc:" line
removed as above, but the
recipients on the "Bcc:" line get a
separate copy of the message containing a "Bcc:" line."</p><p>i.e. In the case of Pegasus 4.51 and presumably 4.52 The BCC recipients&nbsp; see each of the addresses the BCC was sent to .</p><p>&nbsp;</p><p><b>Would it be possible to change this method in a future version so that the addressed BCC readers do NOT receive the&nbsp; addresses of the others??</b></p><p>&nbsp;Similar to this perhaps: (Quoted From the RFC)
</p><p>" In the first case, when a message containing a "Bcc:" field is
prepared to be sent, the "Bcc:" line is
removed even though all of
the recipients (including those specified in the "Bcc:" field)
are sent a copy of the message."</p><p>&nbsp;I imagine this would mean Pegasus would have be changed to send a&nbsp; copy to the server for each BCC address as well as a copy for the To: and CC: addresses, each with the BCC information removed.</p><p><b>I understand that a distribution list can achieve the anonymity being suggested here but for only few addresses it seems like overkill (unless, of course, the same people are addressed time after time).</b>
</p><p>&nbsp;</p><p>&nbsp;</p><p>Stuart</p><p>Montreal, Canada
</p><p>Longtime Peg user (~15years.)
</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>