ACS commons 5.3.0 Email service not working with AEM 6.5

Hi Mayur, 
Yes, I have checked this thread and checked the permissions as well.  That template has read permission even for anonymous and acs-commons-email-user as well.

Regards,
Anil

Hi Milind,

I have changed the template path to e.g 

/etc/notification/email/XXXX/en.txt

Now, I do not get that error anymore but still, emails are not going. 
I am trying to understand which user is being used by my servlet for sending emails.  So, I am trying to print the user name and I am getting anonymous.  Ideally, it should be acs-commons-email-service user.

If I try to enforce in the code to use acs-commons-email-service user then it throws login exception.

final ResourceResolver resolver = request.getResourceResolver();

if(resolver == null){
    log.debug("resolver is null");
} else {
    log.info("resolver is NOT null");
    Session session = resolver.adaptTo(Session.class);

    String userId = session.getUserID();

    log.info("USER ID :--" + userId);
}

The code above is an old code and used to work fine with acs-commons 4.3.2.  I am just trying to print the username (hitting from dispatcher, if logged in publish and testing there in same browser then it picks that logged in user which we do not want so hitting from dispatcher)

 However, if I try to enforce something like this:

// Map for service user details
Map<String, Object> xmlReaderMap = new HashMap<>();
xmlReaderMap.put(ResourceResolverFactory.SUBSERVICE, "acs-commons-email-service");

// Getting ResourceResovler
ResourceResolver resolver = null;
Session session = null;
try {
resolver = resourceResolverFactory.getServiceResourceResolver(xmlReaderMap);
} catch (LoginException e) {
log.error("LoginException " + e.getCause());
}

then I get LoginException, root cause null.

It had all worked well when I reverted back to old pkg of acs-commons 4.3.2 and started receiving emails but today facing issues with that too. So, not sure what is going on.

thanks

check in the logs if you are getting the correct service user.  For me, it was somehow permissions related.  Moving the template under /etc resolved the issue for me.