Hi Mark, sorry for the late answer. To get a more personalized mail post processing, you will have to edit **mailetcontainer.xml** file.
Bounce is returned to the sender address advertized in the SMTP envelope. You will need to detect "fake" incoming SMTP connections. Several mechanisms exists to achieve this purpose: - SPF. One intern in my company wrote a blog post about it [1] - DKIM. I did not tested it so far but it should work. Look at JDKIM mailet to achieve this. - Reverse DNS resolution. You look that the given mail address correspond to the domain of the address of the sender in the SMTP envelope. Rather easy to implement but this feature is missing. I will open a relevant ticket for this. Cheers, Benoit [1] https://medium.com/linagora-engineering/installing-james-3-0-with-spf-verification-421b26b92f11 Le 30/11/2017 à 00:42, Mark Gordon a écrit : > Hi, > > I have my james system setup. It is working great. > > What I would like to do is have James only handle smtp for a domain. So in > the case of a bounce I would like for James to send the email to the system > handling email for the domain. > > So bounce is one problem, but also if another domain tries to send an email > to another domain on the james system the email is sent to the local user. > I want it sent to the real mailbox. > > I am not doing a good job of explaining this. Sorry. > > It looks like james is not checking the MX record of the email and simply > sending the email to the local user. > > How do I stop it from delivering the email locally. > > Thanks > > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
