Thanks Riyad, but I actually need to use SES and not the other way around.
Finally I got it working. It seems like Play! is hardcoding some configurations from application.conf when creating JavaMail Session.
You can see it in play.libs.Mail in getSession()
It totally ignores any configuration you might add for Amazon SES.
So what I had to do as a workaround is creating a Boostrap class that changes Session configuration in runtime like this:
@OnApplicationStart
public class Bootstrap extends Job {
public void doJob() {
Properties props = play.libs.Mail.getSession().getProperties();
props.setProperty("mail.transport.protocol.rfc822","aws");
props.setProperty("mail.aws.user", "youruser");
props.setProperty("mail.aws.password", "yourpassword");
}
}
Probably this is something that should be fixed in next versions of Play! so it integrates smoother with different JavaMail providers.