Hi Raphaël --

Thanks for your response.  I'm using the default mailetcontainer.xml but made 
the following changes:

1.  Added this in section <processor state="root" enableJmx="true">:
<mailet match="RecipientIsLocal" class="RecipientToLowerCase"/>


2.  Added this in section <processor state="transport" enableJmx="true">:
<mailet match="SenderIsLocal" class="RemoveMimeHeader">
    <name>Received</name>
</mailet>


3.  Removed this in section <processor state="transport" enableJmx="true">:
<mailet match="SenderIsLocal" class="ToSenderFolder">
    <folder>Sent</folder>
    <consume>false</consume>
</mailet>


4.  Also, I use SMTP authentication so I disabled this:
<mailet match="RemoteAddrNotInNetwork=127.0.0.1" class="ToProcessor">
    <processor>relay-denied</processor>
    <notice>550 - Requested action not taken: relaying denied</notice>
</mailet>


This happens on both James 3.0.1 and 3.1.0 running on Java 1.8.0_181 on CentOS 
7.



On 9/5/2018 5:19 AM, Raphael OUAZANA wrote:
Hi,

Thank you for you detailed report. We'll look at reproducing it, and open a bug 
if necessary.
In the mean time, can you please share your mailetcontainer.xml configuration 
file?

Regards,
Raphaël Ouazana.

Le 2018-09-01 04:35, Rich P a écrit :
When I send an email to an external recipient (outside domain) and
BCC: an internal recipient (local domain), the BCC: recipient never
receives the email.  Also, if an internal recipient is in the TO:
field and an external recipient in the BCC: field, the external
recipient gets the email but the internal recipient does not.  I can
consistently reproduce this.  For example:

Scenario 1:
TO:  
b...@microsoft.com<mailto:b...@microsoft.com><mailto:b...@microsoft.com><mailto:b...@microsoft.com>
BCC:  
ad...@externalcompany.com<mailto:ad...@externalcompany.com><mailto:ad...@externalcompany.com><mailto:ad...@externalcompany.com>
BCC:  
collea...@externalcompany.com<mailto:collea...@externalcompany.com><mailto:collea...@externalcompany.com><mailto:collea...@externalcompany.com>

In this case, everyone receives their email as expected.

Scenario 2:
TO:  
fri...@mylocalhost.com<mailto:fri...@mylocalhost.com><mailto:fri...@mylocalhost.com><mailto:fri...@mylocalhost.com>
BCC:  
ad...@mylocalhost.com<mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com>
BCC:  
collea...@mylocalhost.com<mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com>

Again, in this case, everyone receives their email as expected.

Scenario 3:
TO:  
b...@microsoft.com<mailto:b...@microsoft.com><mailto:b...@microsoft.com><mailto:b...@microsoft.com>
BCC:  
ad...@mylocalhost.com<mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com>
BCC:  
collea...@mylocalhost.com<mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com>

In this case, neither
ad...@mylocalhost.com<mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com>
 nor
collea...@mylocalhost.com<mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com><mailto:collea...@mylocalhost.com>
 receive
the email.

Scenario 4:
TO:  
ad...@mylocalhost.com<mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com>
BCC:  
ad...@externalcompany.com<mailto:ad...@externalcompany.com><mailto:ad...@externalcompany.com><mailto:ad...@externalcompany.com>
BCC:  
collea...@externalcompany.com<mailto:collea...@externalcompany.com><mailto:collea...@externalcompany.com><mailto:collea...@externalcompany.com>

In this case, 
ad...@mylocalhost.com<mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com><mailto:ad...@mylocalhost.com>
doesn't receive the email but the external recipients do receive the
email!

It appears that as long as the recipients are either all in external
domains or all in the same local domain, it works Ok.  But when a BCC:
recipient is specified and the other recipients are split across
external and internal domains, the local recipients never get the mail
regardless of whether they were in the BCC: or TO: fields.

Has anyone seen this behavior?

Thanks,
Rich
.


Reply via email to