email subsystem not created in 5.0.a community

[fsasse]

I have a fresh install of Alfresco 5.0.a Community edition running on a Windows Server 2012 R2 64 bit server.
The install works, but we cannot get an email invite to go through on the very first site we create.
I know the Exchange server and relay host are configured correctly, because they relay mail fine from our other 4.2.e Community server.

So, I noticed that *NO* $Alfresco_Home\Tomcat\webapps\alfresco\WEB-INF\classes\alfresco\subsystems\email directory was created as part of the install, as was the case in 4.2.e Community.  Should it have been?

My Outbound SMTP settings are pretty basic, with no authentication between Alfresco and the Mail server.
From alfresco-global.properties:

# Outbound Email Configuration
#————-
mail.host=mail-relay-server
mail.port=25
mail.username=root@alfrescoserver
mail.password=
mail.encoding=UTF-8
mail.from.default=alfresco@alfresco.org
mail.smtp.auth=false
mail.smtp.starttls.enable=false

### E-mail site invitation setting ###
notification.email.siteinvite=true

And from alfresco.log:

08:28:22,775 ERROR [org.alfresco.repo.action.executer.MailActionExecuter] [http-apr-80-exec-9] Failed to send email to first.last@companyxyz.com
org.springframework.mail.MailAuthenticationException: Authentication failed; nested exception is javax.mail.AuthenticationFailedException: No authentication mechanisms supported by both server and client

Site email invites in the previous version of Alfresco Community (4.2.e/f) worked out of the box.  What am I doing wrong?
   

[sujaypillai]

From Alfresco Community Edition 5.0.a all the releases will be build using Maven and thus all the dependencies would be found in respective jars. You may find email subsystem in alfresco-repository-5.0.a.jar

[fsasse]

Thanks for the reply!

The email subsystem was included in the alfresco-repository-5.0.a.jar that came with the installer, it just didn't get deployed.
So I manually unzipped the .jar, and added the email directory and configured it the same as in alfresco-global.properties file.
I still get the same results.  The site says the email was sent, but the log shows it's not sent.

[heffron-jimmy]

Is there a resolution for this problem yet?

[mrogers]

What problem?   Need more details.

And there is no need to unzip the jar, that is not necessary.

[fsasse]

Alfresco 5.0.a email subsystem DOES NOT WORK out of the box as in previous releases of Community edition!
Why doesn't the jar deploy as it should in a standard install?
What other details do you need ???

[janmulder]

I had similar problems.
This is the way I got things running again:

mail.protocol=smtp
mail.smtp.auth=true
mail.host=my.inbox.com
mail.port=25
mail.username=xxx@inbox.com
mail.password=yyy

[fsasse]

Thank you Jan!
We have no authentication to our Exchange server through our mail relay host, so mail.smtp.auth=true with a mail.username and a mail.password won't work.
I did try a known working mail account and password and I receive the same errors in alfresco.log.  It is looking like Alfresco 5.0.a *requires* an authenticated connection to the mail server to be able to send outbound mail, I was hoping one of the Alfresco engineers would have confirmed this, or not.

[mrogers]

So far its not confirmed.   

It looks like the issue is a little more obscure than it appears at first glance.

[pzystorm]

I can confirm this error today, we also cannot send mails with mail.smtp.auth=false
The error is always:

 org.springframework.mail.MailAuthenticationException: Authentication failed; nested exception is javax.mail.AuthenticationFailedException: 501 5.5.0 Invalid input (User name and password must be UTF-8).

        at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:392)
        at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:340)
        at org.springframework.mail.javamail.JavaMailSenderImpl.send(JavaMailSenderImpl.java:336)
        at org.alfresco.repo.action.executer.MailActionExecuter.sendEmail(MailActionExecuter.java:953)
‍‍‍‍‍‍‍‍

and it does not matter if we use mail.username= and/or mail.username=anonymous and/or mail.password=bla and/or mail.password=
Playing with mail.encoding=UTF-8 does also not change the error message.