Print or Post BCC as Sender.

[Guest]

I have a user that will send out email messages to several vendors, we use
the BCC field for this. We also need to conduct an internal audit of the
messages sent, who they were sent too, and so on. Our user saves the message
in his SENT ITEMS folder, but unless he opens them from HIS mailbox, others
can not view the BCC field.
We have tried to print the messages, but the BCC field will not print on the
hard copy.

We'd like to have other users see these messages in a public folder with the
BBC header intact, is there a way to do this? We have created the folder,
but when we move the messages over the BCC field is NOT visible.

Is there a way we can print a copy of the sent email with the BCC header
intact as well?

Regards,

Thomas Curcio
Email replies welcome: (e-mail address removed)

 

[Guest]

Consider using a mail merge from a data source, e.g., Contacts, or an Excel
file. Each vendor would get their own individual copy of the same email. I
assume you may be sending a price and availability request, or RFP/RFQ. Run
an automated rule to handle the storage of the emails into a common folder.
You will be abe to store their responses as well.

P.

 

[SgtRich]

I have a user that will send out email messages to several vendors, we use
the BCC field for this. We also need to conduct an internal audit of the
messages sent, who they were sent too, and so on. Our user saves the message
in his SENT ITEMS folder, but unless he opens them from HIS mailbox, others
can not view the BCC field.
We have tried to print the messages, but the BCC field will not print on the
hard copy.

We'd like to have other users see these messages in a public folder with the
BBC header intact, is there a way to do this? We have created the folder,
but when we move the messages over the BCC field is NOT visible.

Is there a way we can print a copy of the sent email with the BCC header
intact as well?

No and no.

 

[Guest]

I like this suggestion, we'll give it a shot and see if we can make it happen.

Thanks for the reply.

 

[Guest]

We found a work around, just have the creator export messages to a PST, allow
the PST to be shared for other users and the creator can move the messages in
to the PST, with all headers in tact. Printing hard copies become
unnecessary since we can use this PST internally.

Thanks for the reply.