You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Pranay Pandey (JIRA)" <ji...@apache.org> on 2009/12/24 09:19:29 UTC
[jira] Created: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
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
Fix For: Release Branch 9.04, SVN trunk
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.
The 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Ruth Hoffman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794577#action_12794577 ]
Ruth Hoffman commented on OFBIZ-3379:
-------------------------------------
Tim,
The comment about BCC anonymity is valid. And for that reason I now agree using alternate connections to send BCCs is a good idea. But, let me remind you, that was not the original intent of this change. We were discussing failed email delivery and not BCC anonymity.
> 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795864#action_12795864 ]
Tim Ruppert commented on OFBIZ-3379:
------------------------------------
Ruth, this is a good example of there being a REAL problem and addressing that problem directly - which, in the real world, is how bugs are found and problems are solved - real customers, real problems - not just trying to think like someone else might be thinking.
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Ruth Hoffman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795867#action_12795867 ]
Ruth Hoffman commented on OFBIZ-3379:
-------------------------------------
Tim:
Really? And what was that problem? Email wasn't "broken". The process by which OFBiz sends notification - using email - does not work the way the original developers had intended.
On another note: Don't waste your time presuming to lecture me on problem solving techniques. I've been working with computers and software since before Al Gore invented the internet :-) if, on the other hand you feel compelled to vent because you don't agree with me, well then by all means - go for 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Gray closed OFBIZ-3379.
-----------------------------
Resolution: Fixed
Fix Version/s: (was: Release Branch 9.04)
Thanks all, fixed in trunk r896213
> 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: Scott Gray
> Fix For: SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (OFBIZ-3379) Email sending process
using one connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841185#action_12841185 ]
Pranay Pandey edited comment on OFBIZ-3379 at 3/4/10 11:13 AM:
---------------------------------------------------------------
Hi Scott,
Sorry for late reply.
Thanks for the patch. I tested the patch given by you and it worked well except one issue that I found while calling sendMailMultiPart(in sendFailureNotification method) with newContext in which missing bodyPart gives service validation error. This is from the last patch on the issue OFBIZ-3379-2.patch.
Please let me know if you have any questions.
was (Author: pandeypranay):
Hi Scott,
Sorry for late reply.
Thanks for the patch. I tested the patch given by you and it worked well except one issue that I found while calling sendMailMultiPart(in sendFailureNotification method) with newContext in which missing bodyPart gives service validation error.
Please let me know if you have any questions.
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794576#action_12794576 ]
Tim Ruppert commented on OFBIZ-3379:
------------------------------------
Ruth, read the comment above. It's from a senior engineer at one of the top hosting companies in the country - in response to a problem that has been reported by a customer who's really using OFBiz. Customers need to ALWAYS get their correspondence - especially for sales - regardless of what email address the customer puts in.
This does not mean that we shouldn't look at a better way of tracking what happens with the To and CCs - because those are visible to everyone that is receiving the email. BCCs are not and should be treated differently - with multiple connections.
> 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
> 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794784#action_12794784 ]
Tim Ruppert commented on OFBIZ-3379:
------------------------------------
Well, this doesn't solve the problem of the person who's on the BCC receiving the message regardless of the To/Cc - which I've checked with a number of different email programs and I ALWAYS get the BCC - even if the To and CC do not. I also get the message that Scott's talking about as well. So, I'm down with changing this to:
# Still sending it to the BCC person - since this is how all email sending programs seem to work.
# AND doing what Scott suggested and sending a failure message to the From.
This is how all email clients seem to work - as well as the fact that it improves the interface for the From message senders on all messages.
> 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805829#action_12805829 ]
Pranay Pandey commented on OFBIZ-3379:
--------------------------------------
Sure Scott, I will test it and will get back to you soon.
Thanks
--
Pranay Pandey
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795865#action_12795865 ]
Tim Ruppert commented on OFBIZ-3379:
------------------------------------
Scott, thanks for taking the extra time to abstract all of this so that everyone can have anything configured however they like. Please commit this fix so that the issues this has caused can be fixed for the entire community.
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Gray updated OFBIZ-3379:
------------------------------
Attachment: OFBIZ-3379-2.patch
Pranay, if you get a chance could you please test this patch which addresses Adam's concerns about using Sun's SMTP classes? No rush, whenever you have time would be great.
Thanks
Scott
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ruppert reassigned OFBIZ-3379:
----------------------------------
Assignee: Scott Gray (was: Tim Ruppert)
> 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: Scott Gray
> 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Ruth Hoffman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794814#action_12794814 ]
Ruth Hoffman commented on OFBIZ-3379:
-------------------------------------
Hello All:
IMO this issue is a great example of determining, in advance, what problem you are trying to solve. Or, if there is even a problem. What you "believe" and what happens to be true...well...may not be the same. Still looks to me like we shouldn't change the email service, just fix the notification process.
> 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: Scott Gray
> 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.
[jira] Assigned: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ruppert reassigned OFBIZ-3379:
----------------------------------
Assignee: Tim Ruppert
> 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841185#action_12841185 ]
Pranay Pandey commented on OFBIZ-3379:
--------------------------------------
Hi Scott,
Sorry for late reply.
Thanks for the patch. I tested the patch given by you and it worked well except one issue that I found while calling sendMailMultiPart(in sendFailureNotification method) with newContext in which missing bodyPart gives service validation error.
Please let me know if you have any questions.
> 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: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Gray updated OFBIZ-3379:
------------------------------
Attachment: OFBIZ-3379.patch
Attaching a patch which generates a delivery failure notification which along with r894236 should resolve this issue.
Pranay, I'm unable to test this patch because I couldn't reproduce the environment in which the SendFailedException occurs. Could you either test the patch for me or otherwise let me know (offline) how to setup my system in order to reproduce the problem?
Thanks
Scott
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pranay Pandey updated OFBIZ-3379:
---------------------------------
Description:
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.
was:
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.
The fix the issue, we need to send this via two connection to mail client.
> 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
> 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.
[jira] Reopened: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Gray reopened OFBIZ-3379:
-------------------------------
> 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: Scott Gray
> Fix For: SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795241#action_12795241 ]
Pranay Pandey commented on OFBIZ-3379:
--------------------------------------
Thanks Scott, I will test the patch uploaded by you and will post the results here.
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Gray updated OFBIZ-3379:
------------------------------
Attachment: OFBIZ-3379.patch
Updated patch for testing, prevents infinite recursion when the failure notification also fails to be sent
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795816#action_12795816 ]
Scott Gray commented on OFBIZ-3379:
-----------------------------------
If there are no objections I'll likely commit this patch in the next day or so, here's are summary of the changes in case anyone hasn't been following closely:
- Emails will now be sent to any valid recipients even if the SMTP server rejected any invalid ones. This can be turned off if desired in general.properties and also on a per service call basis.
- A failure notification will be sent to the email's "from" address, listing the failed recipients and the reason for each failure. The notification can be turned off by setting the sendFailureNotification parameter to false in the service context. If a failure notification is sent then the service will return success even if there were failures (this prevents async calls from retrying and multiple failure notifications being sent).
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Scott Gray (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Tim Ruppert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795868#action_12795868 ]
Tim Ruppert commented on OFBIZ-3379:
------------------------------------
Read the subject and description of the error - they describe EXACTLY what the real world problem was and provide a solution for it. Thru the community process, and as a result of one of your comments, the original fix was improved to have more flexibility to allow people to configure if they don't want to get emails addressed to them (if there are other issues). So, as I stated earlier, the way that OFBiz sends notifications WAS broken for the way many customers use it - and yes it has now been fixed.
On your other note - just because you've been doing it for a long time doesn't mean that you do it right - not now and no guarantee about then. But, at least you're now putting comments related to JIRA tasks in JIRA - instead of in email - so I guess we can all take that as a bonus and moving in the right direction together! Just follow the processes and be a part of intelligent communication in the projects and everyone will continue to be happy with your contributions.
> 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: Scott Gray
> Fix For: Release Branch 9.04, SVN trunk
>
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one connection for To/CC/BCC causing issues
Posted by Tim Ruppert <ti...@hotwaxmedia.com>.
Ruth - go try the use case mentioned below on any email client you can find and let me know the results. You will see:
1. That the From address gets an error receipt - something Scott has mentioned as what we need to do - and I agree.
2. That the BCC address ALWAYS gets the message
What this patch is about is #2 - we can attack #1 or if Scott has time to fix this in the system, then great. Regardless, this is about #2 - feel free to fix the process all you want, but please use real life as a measure of what should be done. Also, please use JIRA for future correspondence on this issue - this is mostly a reiteration of what I put there, but since you replied directly to the dev list, I wanted to make sure you got it.
Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Dec 25, 2009, at 6:51 PM, Ruth Hoffman wrote:
> Hi Tim:
> Please see my comments in line:
>
> Tim Ruppert wrote:
>> I won't dispute that there needs to be something in the system that better allows you to see whether or not emails are able to be sent - but are you really saying that, as someone who's focusing on users, if you put your email address, that you want to be notified on when orders are submitted, into the BCC field - for a silent copy of it (not the same as the To and CC), that you would want a customer's invalid email address to cause you not to be notified? That's the simple question here.
>>
> So the real problem is that when an order is placed, and the email notification fails, someone else (presumably the store owner) will not be notified of, what? The order? The order confirmation? The failed email delivery? Seems to me that the email service isn't broken, the process is.
>
> The change you are suggesting will cause a false sense of security. Since now someone is getting a "confirmation" via copy that this email went out. How will the copied recipient(s) even know that the original failed? What have I missed here?
>
> What you seem to be doing is increasing the complexity of the send mail code and introducing more potential points of failure.
>> I'll be happy to sit down and do a weeks worth of research into all of the different mail sending programs - and how configurable they are as to this particular issue - but please just start there. Is is better for the person who's requesting that they get a silent copy of this email - to not get it because of a user error?
>>
>>
> I say, in this case yes. If the email didn't go through, then as far as the sender is concerned, it did not get sent. In this case, the sender should get a notification that the email failed. Hence my original suggestion to modify the application.
>> There are too many people who don't use OFBiz for every part of their world - and this is limiting to them in a big way. We can make this configurable on To or CC, but since this isn't the bug or the fix that's provided - we can choose to talk about that when someone makes another JIRA issue and we can discuss it there.
>>
>>
> Well, I wouldn't be so picky about all this except that someone has done a really nice job changing the sendMail ECA all in the name of validating HTML. Such a nice job, that I have to disable it to use the sendMail service. So, all I'm suggesting is that when you make basic - seemingly innocuous - changes like this, consider the possibility of any unintended consequences.
>
>> Cheers,
>> Ruppert
>> --
>> Tim Ruppert
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>> o:801.649.6594
>> f:801.649.6595
>>
>> On Dec 25, 2009, at 3:44 PM, Ruth Hoffman wrote:
>>
>>
>>> Hi Tim:
>>> Where does the specification say that the existing OFBiz implementation is wrong? Where does it say that a CC and/or BCC of an email should be sent using a separate "connection"?
>>>
>>> Regards,
>>> Ruth
>>> ----------------------------------------------------
>>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>>> ruth.hoffman@myofbiz.com
>>>
>>> Tim Ruppert wrote:
>>>
>>>> The email behavior is wrong by the simple specification of the way that the messages are supposed to be sent - this shouldn't even be disputed. We need to fix out email sender to work the same way that email is supposed to work - we can do whatever we want to with the CSR application - but this is a no brainer and needs to be put into the project ASAP.
>>>>
>>>> Cheers,
>>>> Ruppert
>>>> --
>>>> Tim Ruppert
>>>> HotWax Media
>>>> http://www.hotwaxmedia.com
>>>>
>>>> o:801.649.6594
>>>> f:801.649.6595
>>>>
>>>> On Dec 25, 2009, at 9:14 AM, Ruth Hoffman wrote:
>>>>
>>>>
>>>>> Hi Pranay:
>>>>> Perhaps you should change the way the CSR application works instead of changing the email behavior? Maybe you could add some status indicators and status event notifications (using a separate email) in the CSR application to track the success or failure of an email notification. After all, that is why OFBiz keeps track of email events and the status thereof, isn't it?
>>>>>
>>>>> Regards,
>>>>> Ruth
>>>>> ----------------------------------------------------
>>>>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>>>>> ruth.hoffman@myofbiz.com
>>>>>
>>>>>
>>>>> Pranay Pandey wrote:
>>>>>
>>>>>> Hi Ruth,
>>>>>>
>>>>>> Thanks for looking into it and replying.
>>>>>> I imagine a case where customer is asking for the status of his order to Company CSR as he was successful in placing an order from ecommerce application with a wrong email address, which was syntactically correct. But company didn't receive any email because of email sending failure. I accept that there is a way for CSR to go to the order manager and find the appropriate order but usually CSR or Company executive logs in to the order manager only when they receive an email for an order. Also the general behavior of mail client.
>>>>>>
>>>>>> Also think of an organization where they don't want to login to the back office application and they manage their order in other systems based on the order email notifications. Then the only way to know about any order placed is the email notification that company receives as a BCC receiver.
>>>>>>
>>>>>> There may be other ways of handling this or as you said this can be a configuration setting. I would love to hear community opinion on this.
>>>>>>
>>>>>> Thanks & Regards
>>>>>> --
>>>>>> Pranay Pandey
>>>>>> HotWax Media | www.hotwaxmedia.com
>>>>>> Direct: +91 98260 35576
>>>>>> Ext: 442
>>>>>>
>>>>>>
>>>>>>
>>>>>> Ruth Hoffman wrote:
>>>>>>
>>>>>>> But, I would think in the normal business setting, if the original failed for some reason, you would not want to sent the BCC. Why send a copy if the original failed?
>>>>>>> Ruth
>>>>>>> Pranay Pandey (JIRA) wrote:
>>>>>>>
>>>>>>>> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>>>
>>>>>>>> Pranay Pandey updated OFBIZ-3379:
>>>>>>>> ---------------------------------
>>>>>>>>
>>>>>>>> Attachment: OFBIZ-3379.patch
>>>>>>>>
>>>>>>>> Here is the patch for review.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> 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
>>>>>>>>> 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.
>>>>>>>>> The fix the issue, we need to send this via two connection to mail client.
>>>>>>>>>
>>>>>>>>
>>>>
>>
>>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by Ruth Hoffman <rh...@aesolves.com>.
Hi Tim:
Please see my comments in line:
Tim Ruppert wrote:
> I won't dispute that there needs to be something in the system that better allows you to see whether or not emails are able to be sent - but are you really saying that, as someone who's focusing on users, if you put your email address, that you want to be notified on when orders are submitted, into the BCC field - for a silent copy of it (not the same as the To and CC), that you would want a customer's invalid email address to cause you not to be notified? That's the simple question here.
>
>
So the real problem is that when an order is placed, and the email
notification fails, someone else (presumably the store owner) will not
be notified of, what? The order? The order confirmation? The failed
email delivery? Seems to me that the email service isn't broken, the
process is.
The change you are suggesting will cause a false sense of security.
Since now someone is getting a "confirmation" via copy that this email
went out. How will the copied recipient(s) even know that the original
failed? What have I missed here?
What you seem to be doing is increasing the complexity of the send mail
code and introducing more potential points of failure.
> I'll be happy to sit down and do a weeks worth of research into all of the different mail sending programs - and how configurable they are as to this particular issue - but please just start there. Is is better for the person who's requesting that they get a silent copy of this email - to not get it because of a user error?
>
>
I say, in this case yes. If the email didn't go through, then as far as
the sender is concerned, it did not get sent. In this case, the sender
should get a notification that the email failed. Hence my original
suggestion to modify the application.
> There are too many people who don't use OFBiz for every part of their world - and this is limiting to them in a big way. We can make this configurable on To or CC, but since this isn't the bug or the fix that's provided - we can choose to talk about that when someone makes another JIRA issue and we can discuss it there.
>
>
Well, I wouldn't be so picky about all this except that someone has done
a really nice job changing the sendMail ECA all in the name of
validating HTML. Such a nice job, that I have to disable it to use the
sendMail service. So, all I'm suggesting is that when you make basic -
seemingly innocuous - changes like this, consider the possibility of any
unintended consequences.
> Cheers,
> Ruppert
> --
> Tim Ruppert
> HotWax Media
> http://www.hotwaxmedia.com
>
> o:801.649.6594
> f:801.649.6595
>
> On Dec 25, 2009, at 3:44 PM, Ruth Hoffman wrote:
>
>
>> Hi Tim:
>> Where does the specification say that the existing OFBiz implementation is wrong? Where does it say that a CC and/or BCC of an email should be sent using a separate "connection"?
>>
>> Regards,
>> Ruth
>> ----------------------------------------------------
>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>> ruth.hoffman@myofbiz.com
>>
>> Tim Ruppert wrote:
>>
>>> The email behavior is wrong by the simple specification of the way that the messages are supposed to be sent - this shouldn't even be disputed.
>>> We need to fix out email sender to work the same way that email is supposed to work - we can do whatever we want to with the CSR application - but this is a no brainer and needs to be put into the project ASAP.
>>>
>>> Cheers,
>>> Ruppert
>>> --
>>> Tim Ruppert
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> o:801.649.6594
>>> f:801.649.6595
>>>
>>> On Dec 25, 2009, at 9:14 AM, Ruth Hoffman wrote:
>>>
>>>
>>>
>>>> Hi Pranay:
>>>> Perhaps you should change the way the CSR application works instead of changing the email behavior? Maybe you could add some status indicators and status event notifications (using a separate email) in the CSR application to track the success or failure of an email notification. After all, that is why OFBiz keeps track of email events and the status thereof, isn't it?
>>>>
>>>> Regards,
>>>> Ruth
>>>> ----------------------------------------------------
>>>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>>>> ruth.hoffman@myofbiz.com
>>>>
>>>>
>>>> Pranay Pandey wrote:
>>>>
>>>>
>>>>> Hi Ruth,
>>>>>
>>>>> Thanks for looking into it and replying.
>>>>> I imagine a case where customer is asking for the status of his order to Company CSR as he was successful in placing an order from ecommerce application with a wrong email address, which was syntactically correct. But company didn't receive any email because of email sending failure. I accept that there is a way for CSR to go to the order manager and find the appropriate order but usually CSR or Company executive logs in to the order manager only when they receive an email for an order. Also the general behavior of mail client.
>>>>>
>>>>> Also think of an organization where they don't want to login to the back office application and they manage their order in other systems based on the order email notifications. Then the only way to know about any order placed is the email notification that company receives as a BCC receiver.
>>>>>
>>>>> There may be other ways of handling this or as you said this can be a configuration setting. I would love to hear community opinion on this.
>>>>>
>>>>> Thanks & Regards
>>>>> --
>>>>> Pranay Pandey
>>>>> HotWax Media | www.hotwaxmedia.com
>>>>> Direct: +91 98260 35576
>>>>> Ext: 442
>>>>>
>>>>>
>>>>>
>>>>> Ruth Hoffman wrote:
>>>>>
>>>>>
>>>>>> But, I would think in the normal business setting, if the original failed for some reason, you would not want to sent the BCC. Why send a copy if the original failed?
>>>>>> Ruth
>>>>>> Pranay Pandey (JIRA) wrote:
>>>>>>
>>>>>>
>>>>>>> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>>
>>>>>>> Pranay Pandey updated OFBIZ-3379:
>>>>>>> ---------------------------------
>>>>>>>
>>>>>>> Attachment: OFBIZ-3379.patch
>>>>>>>
>>>>>>> Here is the patch for review.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> 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
>>>>>>>> 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.
>>>>>>>> The fix the issue, we need to send this via two connection to mail client.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>>
>
>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one connection for To/CC/BCC causing issues
Posted by Tim Ruppert <ti...@hotwaxmedia.com>.
I won't dispute that there needs to be something in the system that better allows you to see whether or not emails are able to be sent - but are you really saying that, as someone who's focusing on users, if you put your email address, that you want to be notified on when orders are submitted, into the BCC field - for a silent copy of it (not the same as the To and CC), that you would want a customer's invalid email address to cause you not to be notified? That's the simple question here.
I'll be happy to sit down and do a weeks worth of research into all of the different mail sending programs - and how configurable they are as to this particular issue - but please just start there. Is is better for the person who's requesting that they get a silent copy of this email - to not get it because of a user error?
There are too many people who don't use OFBiz for every part of their world - and this is limiting to them in a big way. We can make this configurable on To or CC, but since this isn't the bug or the fix that's provided - we can choose to talk about that when someone makes another JIRA issue and we can discuss it there.
Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Dec 25, 2009, at 3:44 PM, Ruth Hoffman wrote:
> Hi Tim:
> Where does the specification say that the existing OFBiz implementation is wrong? Where does it say that a CC and/or BCC of an email should be sent using a separate "connection"?
>
> Regards,
> Ruth
> ----------------------------------------------------
> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
> ruth.hoffman@myofbiz.com
>
> Tim Ruppert wrote:
>> The email behavior is wrong by the simple specification of the way that the messages are supposed to be sent - this shouldn't even be disputed.
>> We need to fix out email sender to work the same way that email is supposed to work - we can do whatever we want to with the CSR application - but this is a no brainer and needs to be put into the project ASAP.
>>
>> Cheers,
>> Ruppert
>> --
>> Tim Ruppert
>> HotWax Media
>> http://www.hotwaxmedia.com
>>
>> o:801.649.6594
>> f:801.649.6595
>>
>> On Dec 25, 2009, at 9:14 AM, Ruth Hoffman wrote:
>>
>>
>>> Hi Pranay:
>>> Perhaps you should change the way the CSR application works instead of changing the email behavior? Maybe you could add some status indicators and status event notifications (using a separate email) in the CSR application to track the success or failure of an email notification. After all, that is why OFBiz keeps track of email events and the status thereof, isn't it?
>>>
>>> Regards,
>>> Ruth
>>> ----------------------------------------------------
>>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>>> ruth.hoffman@myofbiz.com
>>>
>>>
>>> Pranay Pandey wrote:
>>>
>>>> Hi Ruth,
>>>>
>>>> Thanks for looking into it and replying.
>>>> I imagine a case where customer is asking for the status of his order to Company CSR as he was successful in placing an order from ecommerce application with a wrong email address, which was syntactically correct. But company didn't receive any email because of email sending failure. I accept that there is a way for CSR to go to the order manager and find the appropriate order but usually CSR or Company executive logs in to the order manager only when they receive an email for an order. Also the general behavior of mail client.
>>>>
>>>> Also think of an organization where they don't want to login to the back office application and they manage their order in other systems based on the order email notifications. Then the only way to know about any order placed is the email notification that company receives as a BCC receiver.
>>>>
>>>> There may be other ways of handling this or as you said this can be a configuration setting. I would love to hear community opinion on this.
>>>>
>>>> Thanks & Regards
>>>> --
>>>> Pranay Pandey
>>>> HotWax Media | www.hotwaxmedia.com
>>>> Direct: +91 98260 35576
>>>> Ext: 442
>>>>
>>>>
>>>>
>>>> Ruth Hoffman wrote:
>>>>
>>>>> But, I would think in the normal business setting, if the original failed for some reason, you would not want to sent the BCC. Why send a copy if the original failed?
>>>>> Ruth
>>>>> Pranay Pandey (JIRA) wrote:
>>>>>
>>>>>> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>>
>>>>>> Pranay Pandey updated OFBIZ-3379:
>>>>>> ---------------------------------
>>>>>>
>>>>>> Attachment: OFBIZ-3379.patch
>>>>>>
>>>>>> Here is the patch for review.
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 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
>>>>>>> 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.
>>>>>>> The fix the issue, we need to send this via two connection to mail client.
>>>>>>>
>>>>>>
>>
>>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by Ruth Hoffman <rh...@aesolves.com>.
Hi Tim:
Where does the specification say that the existing OFBiz implementation
is wrong? Where does it say that a CC and/or BCC of an email should be
sent using a separate "connection"?
Regards,
Ruth
----------------------------------------------------
Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
ruth.hoffman@myofbiz.com
Tim Ruppert wrote:
> The email behavior is wrong by the simple specification of the way that the messages are supposed to be sent - this shouldn't even be disputed.
>
> We need to fix out email sender to work the same way that email is supposed to work - we can do whatever we want to with the CSR application - but this is a no brainer and needs to be put into the project ASAP.
>
> Cheers,
> Ruppert
> --
> Tim Ruppert
> HotWax Media
> http://www.hotwaxmedia.com
>
> o:801.649.6594
> f:801.649.6595
>
> On Dec 25, 2009, at 9:14 AM, Ruth Hoffman wrote:
>
>
>> Hi Pranay:
>> Perhaps you should change the way the CSR application works instead of changing the email behavior? Maybe you could add some status indicators and status event notifications (using a separate email) in the CSR application to track the success or failure of an email notification. After all, that is why OFBiz keeps track of email events and the status thereof, isn't it?
>>
>> Regards,
>> Ruth
>> ----------------------------------------------------
>> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
>> ruth.hoffman@myofbiz.com
>>
>>
>> Pranay Pandey wrote:
>>
>>> Hi Ruth,
>>>
>>> Thanks for looking into it and replying.
>>> I imagine a case where customer is asking for the status of his order to Company CSR as he was successful in placing an order from ecommerce application with a wrong email address, which was syntactically correct. But company didn't receive any email because of email sending failure. I accept that there is a way for CSR to go to the order manager and find the appropriate order but usually CSR or Company executive logs in to the order manager only when they receive an email for an order. Also the general behavior of mail client.
>>>
>>> Also think of an organization where they don't want to login to the back office application and they manage their order in other systems based on the order email notifications. Then the only way to know about any order placed is the email notification that company receives as a BCC receiver.
>>>
>>> There may be other ways of handling this or as you said this can be a configuration setting. I would love to hear community opinion on this.
>>>
>>> Thanks & Regards
>>> --
>>> Pranay Pandey
>>> HotWax Media | www.hotwaxmedia.com
>>> Direct: +91 98260 35576
>>> Ext: 442
>>>
>>>
>>>
>>> Ruth Hoffman wrote:
>>>
>>>> But, I would think in the normal business setting, if the original failed for some reason, you would not want to sent the BCC. Why send a copy if the original failed?
>>>> Ruth
>>>> Pranay Pandey (JIRA) wrote:
>>>>
>>>>> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>>
>>>>> Pranay Pandey updated OFBIZ-3379:
>>>>> ---------------------------------
>>>>>
>>>>> Attachment: OFBIZ-3379.patch
>>>>>
>>>>> Here is the patch for review.
>>>>>
>>>>>
>>>>>
>>>>>> 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
>>>>>> 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.
>>>>>> The fix the issue, we need to send this via two connection to mail client.
>>>>>>
>>>>>>
>>>>>
>>>>>
>
>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one connection for To/CC/BCC causing issues
Posted by Tim Ruppert <ti...@hotwaxmedia.com>.
The email behavior is wrong by the simple specification of the way that the messages are supposed to be sent - this shouldn't even be disputed.
We need to fix out email sender to work the same way that email is supposed to work - we can do whatever we want to with the CSR application - but this is a no brainer and needs to be put into the project ASAP.
Cheers,
Ruppert
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com
o:801.649.6594
f:801.649.6595
On Dec 25, 2009, at 9:14 AM, Ruth Hoffman wrote:
> Hi Pranay:
> Perhaps you should change the way the CSR application works instead of changing the email behavior? Maybe you could add some status indicators and status event notifications (using a separate email) in the CSR application to track the success or failure of an email notification. After all, that is why OFBiz keeps track of email events and the status thereof, isn't it?
>
> Regards,
> Ruth
> ----------------------------------------------------
> Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
> ruth.hoffman@myofbiz.com
>
>
> Pranay Pandey wrote:
>> Hi Ruth,
>>
>> Thanks for looking into it and replying.
>> I imagine a case where customer is asking for the status of his order to Company CSR as he was successful in placing an order from ecommerce application with a wrong email address, which was syntactically correct. But company didn't receive any email because of email sending failure. I accept that there is a way for CSR to go to the order manager and find the appropriate order but usually CSR or Company executive logs in to the order manager only when they receive an email for an order. Also the general behavior of mail client.
>>
>> Also think of an organization where they don't want to login to the back office application and they manage their order in other systems based on the order email notifications. Then the only way to know about any order placed is the email notification that company receives as a BCC receiver.
>>
>> There may be other ways of handling this or as you said this can be a configuration setting. I would love to hear community opinion on this.
>>
>> Thanks & Regards
>> --
>> Pranay Pandey
>> HotWax Media | www.hotwaxmedia.com
>> Direct: +91 98260 35576
>> Ext: 442
>>
>>
>>
>> Ruth Hoffman wrote:
>>> But, I would think in the normal business setting, if the original failed for some reason, you would not want to sent the BCC. Why send a copy if the original failed?
>>> Ruth
>>> Pranay Pandey (JIRA) wrote:
>>>> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>>
>>>> Pranay Pandey updated OFBIZ-3379:
>>>> ---------------------------------
>>>>
>>>> Attachment: OFBIZ-3379.patch
>>>>
>>>> Here is the patch for review.
>>>>
>>>>
>>>>> 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
>>>>> 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.
>>>>> The fix the issue, we need to send this via two connection to mail client.
>>>>>
>>>>
>>>>
>>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by Ruth Hoffman <rh...@aesolves.com>.
Hi Pranay:
Perhaps you should change the way the CSR application works instead of
changing the email behavior? Maybe you could add some status indicators
and status event notifications (using a separate email) in the CSR
application to track the success or failure of an email notification.
After all, that is why OFBiz keeps track of email events and the status
thereof, isn't it?
Regards,
Ruth
----------------------------------------------------
Find me on the web at http://www.myofbiz.com or Google keyword "myofbiz"
ruth.hoffman@myofbiz.com
Pranay Pandey wrote:
> Hi Ruth,
>
> Thanks for looking into it and replying.
> I imagine a case where customer is asking for the status of his order
> to Company CSR as he was successful in placing an order from ecommerce
> application with a wrong email address, which was syntactically
> correct. But company didn't receive any email because of email sending
> failure. I accept that there is a way for CSR to go to the order
> manager and find the appropriate order but usually CSR or Company
> executive logs in to the order manager only when they receive an email
> for an order. Also the general behavior of mail client.
>
> Also think of an organization where they don't want to login to the
> back office application and they manage their order in other systems
> based on the order email notifications. Then the only way to know
> about any order placed is the email notification that company receives
> as a BCC receiver.
>
> There may be other ways of handling this or as you said this can be a
> configuration setting. I would love to hear community opinion on this.
>
> Thanks & Regards
> --
> Pranay Pandey
> HotWax Media | www.hotwaxmedia.com
> Direct: +91 98260 35576
> Ext: 442
>
>
>
> Ruth Hoffman wrote:
>> But, I would think in the normal business setting, if the original
>> failed for some reason, you would not want to sent the BCC. Why send
>> a copy if the original failed?
>> Ruth
>> Pranay Pandey (JIRA) wrote:
>>> [
>>> https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>> ]
>>>
>>> Pranay Pandey updated OFBIZ-3379:
>>> ---------------------------------
>>>
>>> Attachment: OFBIZ-3379.patch
>>>
>>> Here is the patch for review.
>>>
>>>
>>>> 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
>>>> 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.
>>>> The fix the issue, we need to send this via two connection to mail
>>>> client.
>>>>
>>>
>>>
>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by Pranay Pandey <pr...@hotwaxmedia.com>.
Hi Ruth,
Thanks for looking into it and replying.
I imagine a case where customer is asking for the status of his order to
Company CSR as he was successful in placing an order from ecommerce
application with a wrong email address, which was syntactically correct.
But company didn't receive any email because of email sending failure. I
accept that there is a way for CSR to go to the order manager and find
the appropriate order but usually CSR or Company executive logs in to
the order manager only when they receive an email for an order. Also the
general behavior of mail client.
Also think of an organization where they don't want to login to the back
office application and they manage their order in other systems based on
the order email notifications. Then the only way to know about any order
placed is the email notification that company receives as a BCC receiver.
There may be other ways of handling this or as you said this can be a
configuration setting. I would love to hear community opinion on this.
Thanks & Regards
--
Pranay Pandey
HotWax Media | www.hotwaxmedia.com
Direct: +91 98260 35576
Ext: 442
Ruth Hoffman wrote:
> But, I would think in the normal business setting, if the original
> failed for some reason, you would not want to sent the BCC. Why send a
> copy if the original failed?
> Ruth
> Pranay Pandey (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Pranay Pandey updated OFBIZ-3379:
>> ---------------------------------
>>
>> Attachment: OFBIZ-3379.patch
>>
>> Here is the patch for review.
>>
>>
>>> 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
>>> 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.
>>> The fix the issue, we need to send this via two connection to mail
>>> client.
>>>
>>
>>
Re: [jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by Ruth Hoffman <rh...@aesolves.com>.
But, I would think in the normal business setting, if the original
failed for some reason, you would not want to sent the BCC. Why send a
copy if the original failed?
Ruth
Pranay Pandey (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Pranay Pandey updated OFBIZ-3379:
> ---------------------------------
>
> Attachment: OFBIZ-3379.patch
>
> Here is the patch for review.
>
>
>> 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
>> 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.
>> The fix the issue, we need to send this via two connection to mail client.
>>
>
>
[jira] Updated: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Pranay Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pranay Pandey updated OFBIZ-3379:
---------------------------------
Attachment: OFBIZ-3379.patch
Here is the patch for review.
> 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
> 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.
> The 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.
[jira] Commented: (OFBIZ-3379) Email sending process using one
connection for To/CC/BCC causing issues
Posted by "Ruth Hoffman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OFBIZ-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794405#action_12794405 ]
Ruth Hoffman commented on OFBIZ-3379:
-------------------------------------
I'm wondering why you would want to send the bcc if the original failed. If your intention is to keep a record of success or failure of the email event - then isn't this better done somewhere else? IMO, BCC were never intended to be used as email telemetry.
Please do not make this change. If desired, make this a configuration option....
> 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
> 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.