Include a way for developers to see BCC addresses for testing
SMTP servers forward mail on to BCC recipients while at the same time stripping that field. Because Mailtrap is serving as the SMTP server, it can record the original data in the BCC header.
The default Mailtrap view should continue to hide the BCC header to provide a Client-like view, but the BCC header should be made available in either the RAW view or another view "As Received".
I agree! It is also useful to see the "SMTP envelope" that was used in transacting with the receiving SMTP server. For example, I can send an email where the email headers show "From: God <firstname.lastname@example.org>" and "To: Jesus <email@example.com>" but during the SMTP transaction with your servers, the "MAIL FROM <firstname.lastname@example.org>" is the envelope from, and "RCPT TO <email@example.com>" is the envelope to. Would be nice to be able to see those somewhere as it's part of what I'm troubleshooting with my app!
AdminMailtrap (Mailtrap, Mailtrap) commented
Thank you, everyone, for your requests and contributing to Mailtrap development process!
We took each your suggestion into account, and the feature is planned for implementation pretty soon this year. We can't provide exact eta so far, but we'll make sure to notify you guys when this functionality is implemented.
What is the status of this issue? I need to debug BCC somehow
Jack Ryon commented
This would be extremely helpful if implemented. Please toss us a bone, Mailtrap!
I need this functionality.
Patrick Chokron commented
I urge Mailtrap to reconsider this request. As a business customer that relies on Mailtrap to test transactional emails on a regular basis, I need a mechanism to verify that BCC email recipients are included on outgoing emails. This is an essential function that is, as the votes here indicate, also quite popular amongst your users.
Technically, there is no reason it cannot be done, as clearly, your SMTP server must receive this information.
Jonathan F commented
Major red herring not knowing that CC/BCC is not implemented....
Common, implement this feature will make mailtrap perfect in the mail testing service.
Brendan Asselstine commented
Yes; I just encountered this deficiency. We are sending out an email to a group of people who should not see who else has received the email. It's difficult to confirm that the feature works without seeing it in MailTrap.
It would be really interesting to see this information. :(
James Seigel commented
At least show what email received the email?
Alexander Lehmann commented
I was thinking the same thing for the bounce address (MAIL FROM), which would be useful to display in some cases. Maybe it would be possible to collect additional data in addition to the mail text and display that along with the message (MAIL FROM, RCPT TO, maybe also the TLS cypher that was used and the client IP address)
Nick Spacek commented
Looks like I got it a little bit wrong. Below is a good link on how SMTP servers work, but regardless of the mechanic it would be impossible for the SMTP server to send a message without being told where to send it, so Mailtrap's SMTP server has the BCC addresses somewhere.
Quoted from another comment:
According to this StackOverflow post: http://stackoverflow.com/questions/2750211/sending-bcc-emails-using-a-smtp-server, Mailtrap's SMTP server should be receiving a list of all of the destination addresses from the RCPT TO command. It seems like the BCC addresses could be determined by comparing the headers of the received message and the RCPT TO.