[
https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122564#comment-13122564
]
elan commented on OFBIZ-3379:
-----------------------------
# handle BCC via another connection
In RFC, the BCC shall be handled at MX (SMTP server). SMTP server will remove
the BCC header while deliver the mail.
As a client, it has no need to handle BCC via another connection.
# failure notification
SMTP server will send failure message to client, client shall notice the
sender/from .
But for sender/from , BCC is not secret, so it will be sufficiently to handle
it the same as TO/CC .
> Email sending process using one connection for To/CC/BCC causing issues
> -----------------------------------------------------------------------
>
> Key: OFBIZ-3379
> URL: https://issues.apache.org/jira/browse/OFBIZ-3379
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: Release Branch 09.04, SVN trunk
> Reporter: Pranay Pandey
> Assignee: Scott Gray
> Fix For: SVN trunk
>
> Attachments: OFBIZ-3379-2.patch, OFBIZ-3379.patch, OFBIZ-3379.patch,
> OFBIZ-3379.patch
>
>
> Typically BCCs are handled via the sending mail client. That is, when the
> client sees a BCC in an email, it will open up two connections to the mail
> server, the first for the To/CC fields, the second for BCC fields, this way
> the addresses are masked from the headers and there is that layer of
> anonymity that BCC is used for.
> What appears to be happening is that OFBiz is sending all of the information
> in one connection to the mail server and having the mail server sort out the
> details. So when sendTo encountering an invalid email, and then terminating
> the remaining execution of the outgoing process and no email sent to BCC
> address which is usually going to be a valid address from email settings for
> the company.
> To fix the issue, we need to send this via two connection to mail client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
