Posted by Dane Powell on May 14, 2009 at 11:36pm
| Project: | Messaging |
| Version: | 6.x-2.x-dev |
| Component: | PHPMailer |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I would be interested in seeing BCC support implemented, so that (for instance) one can use Messaging as part of a mailing list, and the messages can be addressed to mailinglist@example.com while actually being distributed to everybody on the mailing list via BCC.
I am happy to work on this myself if you can point me in the right direction. I think basically you would just have to be able to specify an addressee type for each addressee (To, CC, or BCC).
Comments
#1
I am currently investigating how to implement this on a messaging-method-specific basis - i.e., a checkbox on the PHPMailer settings page for "Send messages to multiple recipients as BCCs". It sounds like PHPMailer might not have good BCC support, however :(
#2
Check out http://drupal.org/node/260595 to see if this can be incorporated there.
David
#3
I figured out how to arrange this with PHPMailer. I don't know if it's possible to incorporate this with the other issue, I just made it an option at admin/messaging/settings/method/phpmailer
#4
#5
Sorry, I forgot to fix the directory tree in that patch...
#6
Very very minor change to fix formatting
#7
The patch was failing for me so here's an updated version.
I made some minor changes to the wording but the otherwise, the code looks good.
#8
#9
I notice this didn't make it into the latest dev release, any particular reason?
#10
Can we go ahead and get this committed so we can port to 4.x?
#11
@Dane,
As a general policy we are not adding new features for 2.x branch.
However if you want some of these small features in 2.x please go ahead (you have cvs access), let me know when you think we should put out a new release.
#12
Thank Jose- I didn't want to be too cavalier about committing to a project that's not really mine. This will be committed to both 2.x and 4.x.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.