I'm using most of the smtpserver.xml defaults but have the following changes.
1. Three servers enabled: one each for ports 25, 465 and 587 and each one uses its own local JKS keystore. Here are the changes: Port 25: <tls socketTLS="false" startTLS="true"> <helloName autodetect="false">myservername.com</helloName> <authRequired>announce</authRequired> Enabled: <authorizedAddresses>127.0.0.0/8</authorizedAddresses> <verifyIdentity>true</verifyIdentity> <handler class="org.apache.james.smtpserver.fastfail.SpamAssassinHandler"> <spamdHost>127.0.0.1</spamdHost> <spamdPort>783</spamdPort> <spamdRejectionHits>10</spamdRejectionHits> </handler> Port 465: <tls socketTLS="true" startTLS="false"> <helloName autodetect="false">myservername.com</helloName> <authRequired>true</authRequired> <verifyIdentity>true</verifyIdentity> Port 587: <tls socketTLS="false" startTLS="true"> <helloName autodetect="false">myservername.com</helloName> <authRequired>true</authRequired> <verifyIdentity>true</verifyIdentity> By the way, some users send out mail on port 465 and other on port 587. The behavior is the same either way. I will look at the SMTP traffic further. It seems like the message is making it to the server because the smtpserver.log has the entry: "Successfully spooled mail... for ..." and it lists all of the recipients including the BCC recipient. I'm using file-based mail storage and I verified that there is NO mail in the 'new' folder for the local BCC recipient. On 9/5/2018 10:25 AM, Raphael OUAZANA wrote: > Hi again, > > I tried to reproduce it by different ways, but did not succeed. > > Can you please: > - share your mailetcontainer.xml configuration file > - share your smtpserver.xml configuration file > - take a capture of the smtp traffic while sending the email. Maybe > your email client is doing some weird things that James does not > handle yet. > > Regards, > Raphaël Ouazana. > > Le 2018-09-05 11:19, Raphael OUAZANA a écrit : >> 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> >>> BCC: ad...@externalcompany.com<mailto:ad...@externalcompany.com> >>> BCC: 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> >>> BCC: ad...@mylocalhost.com<mailto:ad...@mylocalhost.com> >>> BCC: 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> >>> BCC: ad...@mylocalhost.com<mailto:ad...@mylocalhost.com> >>> BCC: collea...@mylocalhost.com<mailto:collea...@mylocalhost.com> >>> >>> In this case, neither >>> ad...@mylocalhost.com<mailto:ad...@mylocalhost.com> nor >>> collea...@mylocalhost.com<mailto:collea...@mylocalhost.com> receive >>> the email. >>> >>> Scenario 4: >>> TO: ad...@mylocalhost.com<mailto:ad...@mylocalhost.com> >>> BCC: ad...@externalcompany.com<mailto:ad...@externalcompany.com> >>> BCC: collea...@externalcompany.com<mailto:collea...@externalcompany.com> >>> >>> In this case, 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 >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org > . >
