Email Archiving Bcc recipient is empty

[timesurfer]

Hello,

The "Email Archiving" feature is great.

However, when a user (from the local domain) sends and email to Bcc recipients (to users outside the local domain), the archived local email don't show who those Bcc recipients are (as it does with To or Cc).

Could you please help me on achieving this?

We need all archived emails to have the To, Cc and Bcc recipients registered.

I have root access to the server, WHM and cPanel.

 

[cPanelLauren]

Hi @timesurfer

Would it be possible to show me an example of how you're viewing the archived mail?

 

[timesurfer]

Hi @timesurfer
Would it be possible to show me an example of how you're viewing the archived mail?

Sure. Here is what I see when I open the email message on a text editor.

If Email Archived messages are not meant to be read like this (using a text editor), please tell me the correct way.
I just extracted the tar.gz file and browsed through the hidden folders in search of the emails.
I know this isn't pratical, but I just wanted to see this functionality (Email Archiving) in action.

The email below was sent to several recipients, all in the Bcc field.
The fields To and Cc were left blank.

I changed the original elements to:
- "LOCALDOMAIN"
- "user001"
- "FQDN"
- "99.999.999.999"
All the rest is untouched.

========================================
Archived Email Message - Beginning
========================================

Return-path: <[email protected]"LOCALDOMAIN">
Envelope-to: "user001"@"LOCALDOMAIN"
Delivery-date: Mon, 15 Apr 2019 15:03:02 +0100
Received: from [127.0.0.1] (port=53628 helo="FQDN")
by "FQDN" with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.91)
(envelope-from <[email protected]"LOCALDOMAIN">)
id 1hG2CE-0008Pd-GG; Mon, 15 Apr 2019 15:02:59 +0100
Received: from ["99.999.999.999"] (["99.999.999.999"]) by "FQDN"
(Horde Framework) with HTTPS; Mon, 15 Apr 2019 15:02:54 +0100
Date: Mon, 15 Apr 2019 15:02:54 +0100
Message-ID: <[email protected]"FQDN">
From: Suporte 2 "COMPANY" <[email protected]"LOCALDOMAIN">
To:
Subject: =?utf-8?b?Rm9ybWHDp8Ojbw==?= Regular de
=?utf-8?b?TWVkaWHDp8OjbyBJbW9iaWxpw6FyaWEgTWFpb3DDp8Ojbw==?= - 09h30,
16-Abr-2019, =?utf-8?b?M8KqLWZlaXJh?=
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-OutGoing-Spam-Status: No, score=-1.0
X-Archive-Type: incoming
X-Archive-Recipient: "user001"@"LOCALDOMAIN"


Dear Sirs,

We inform that [...]
[...]
[...]
[...]
[...]
[...]
[...]


Regards,
Support Team
"COMPANY"

========================================
Archived Email Message - End
========================================

 

[cPanelLauren]

Hi @timesurfer

This is essentially the header of the email and blind carbon copies (BCC) aren't going to be shown in the header. Is there a separate mail transaction listed for the BCC?

 

[timesurfer]

Hi @timesurfer
Is there a separate mail transaction listed for the BCC?

No, there isn't. At least, I can't find any.
I opened the email on the cPanel link "Acess Webmail", on the Email Archiving area, and opened the email in Horde in the "outgoing" folder, and in the "To" field there was only the text "Undisclosed Recipients" and there isn't any Bcc field showing at all.

 

[timesurfer]

Hi @timesurferIs there a separate mail transaction listed for the BCC?

Does this usually happens in Email Archiving: to have a separate mail transaction listed for the Bcc?

bump

bump

 

[cPanelLauren]

Hi @timesurfer

Can you please open a ticket using the link in my signature for this? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.


Thanks!

 

[timesurfer]

Hi @timesurfer
Can you please open a ticket using the link in my signature for this? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved.
Thanks!

Thank you for your help.
I tried opening a ticket, but after I introduce my support access ID I got the message that (1) this support should be taken care of by my Vps hosting company and (2) only proceed if I want cPanel to handle the issue.
So, I'm going to contact them first, and see if they can solve this. If not, I will then follow option (2).
Regards