Bug 103471 - Evolution reveals BCC field with local delivery
Evolution reveals BCC field with local delivery
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: evolution (Show other bugs)
9
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-08-31 12:44 EDT by Geoff Dolman
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-31 23:16:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Geoff Dolman 2003-08-31 12:44:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

Description of problem:
When mail is sent with local delivery and exim as the mta the BCC field is
visible to all of the recipients. This doesn't happen if smtp is the method of
delivery.

Version-Release number of selected component (if applicable):
evolution 1.2.2-5

How reproducible:
Always

Steps to Reproduce:
1.  send a mail with bcc
2.
3.
    

Expected Results:  BCC should not be revealed

Additional info:
Comment 1 Geoff Dolman 2003-08-31 13:06:18 EDT
I have posted the exim configuration file as
http://www-gene.cimr.cam.ac.uk/~geoff/configure
It (exim) is just forwarding to a smarthost - that's all it does, but when you
change evolution to use smtp direct to the smart host the BCC field behaves as
expected. It's only using "sendmail" as the means of delivery on the local
machine - which forwards to the smart host - that the BCC is visible to recipients.
Comment 2 Jeremy Katz 2003-08-31 23:16:07 EDT
Works just fine for me here with local sendmail, which is what we support.  This
is almost certainly exim's doing as evolution's pass off to sendmail is pretty
dead simple.

Note You need to log in before you can comment on or make changes to this bug.