Redmine

I'm seeing this too, from forum posts.

I don't think it's related to the application since I don't see them when I do tests on my local setup.

Hi JP,

I'm not quite sure what you mean here.

When I got your reply to this very message, I saw in the headers:

{{{
From: noreply@redmine.org
Bcc: edavis@...,
benjamin.d.oakes@...,
jgoerzen@...
}}}

I stripped the domain names here to prevent spam, but they sure were present on the message I got. They're also there on messages from forums.

The only possible reason the BCC line is there in the message I received is that Redmine (or Rails libraries under its control) put it there. BCC is somewhat of an odd beast. Lots of mail clients give the illusion that it's a header like every other, but in reality they are not putting a BCC line in the outgoing message. Rather, they just use the data entered there to give more recipients to the SMTP (or local sendmail) server. A BCC line should never enter the message body.

I know that there is a BCC setting. I haven't gone to play with it, so I'm not sure whether it enables or disables this behavior, or is a toggle between putting names on the BCC instead of To or CC lines.

I don't see the BCC in my mail client (Thunderbird 2.0) nor in the source of the mail message on the server.

From: noreply@redmine.org
Subject: [Redmine - Defect #752] Outgoing emails contain Bcc
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary=mimepart_47dd8960e0f3b_6933..fdbe3d37e11fb
Date: Sun, 16 Mar 2008 13:56:38 -0700 (PDT)
Message-ID: <47dd8986.0af5660a.47e5.ffffef94@mx.google.com>
To: undisclosed-recipients:;

--mimepart_47dd8960e0f3b_6933..fdbe3d37e11fb
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: Quoted-printable
Content-Disposition: inline

I also see the BCC addressees. Do the mail servers keep them when there is no "To:" header?

john wilson: I think it's related to the SMTP server I use (Google Apps).

Yes I looked into this problem once before and I also came to the conclusion that Google Mail was to blame!