[
https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794606#action_12794606
]
Scott Gray commented on OFBIZ-3379:
-----------------------------------
I've been thinking about this the last couple of days and here are thoughts.
I believe BCC handling is the responsibility of the underlying JVM
implementation and not of the API user. The BCCs are correctly blinded using
the current implementation and I don't think we need to change that.
At a high level, emails can fail in one of two ways:
- they can be rejected outright by the initial smtp server
- they can subsequently be bounced further down the chain after having been
initially accepted. At this point the message is bounced per failed recipient
and will still be delivered to any valid ones.
I think our issue is that if a message is rejected by the smtp server then
there is no feedback provided by the system (the comm event may be marked
failed, I haven't checked). With a regular mail client, direct feedback is
provided in the form of some type of error message and email remains in the
outbox or in draft state until the user rectifies the problem.
I would like to suggest that instead of sending the bcc regardless, we should
send a failure message to the "from" email address with the reason for the
failure. If the comm event isn't marked as failed then we should also change
the logic to do so (we could possibly link to the comm event from the failure
notification to allow the user to rectify the situation easily). The failure
message logic should probably reside at a higher level than the sendmail
service so that it can be templated and even turned off if needed (an example
might be a webmail client where we have the ability to provide direct feedback).
If everyone feels this approach is suitable then I'll take a closer look at the
code tomorrow as see how we might go about implementing it.
> 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 9.04, SVN trunk
> Reporter: Pranay Pandey
> Assignee: Tim Ruppert
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
