• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 30 replies
  • Subscribers 9 subscribers
  • Views 8902 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Issues with Configuring Email Server

Venu

Hi,

I am trying to configure mail server in Appian V7.10 so an email can be sent using office365 account.
While sending emails Appian reads the configurations mentioned in custom.properties (configuarations suggested in forum.appian.com/.../Mail_Server_Setup.html). But we are facing problem while sending mails.

Steps followed:

we configured office365 as mail server, configured this as SMTP host.
we did the setting as mentioned in forum. forum.appian.com/.../Mail_Server_Setup.html
conf.mailhandler.mail.smtp.host=SMTP_HOST:PORT
conf.mailhandler.mail.smtp.auth=true
conf.mailhandler.mail.user=myuser@abc.com
conf.mailhandler.mail.transport.protocol=smtp
password is mentioned in password.properties file.
conf.password.SMTP=mypassword

Notification sender is also configured.
conf.mailhandler.ntf_sndr_addr=myuser@abc.com
conf.mailhandler.ntf_sndr_name=myuser

We tested the connectivity from the appian...

OriginalPostID-167251

OriginalPostID-167251

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    The application server makes a GET request via conf.suite.MAIL_SCHEME://conf.suite.MAIL_SERVER_AND_PORT to retrieve the JSP that will be used as a template to render the body of the email. This step is called "Rendering the email body". If these settings are not defined the URL defaults to
    conf.suite.SCHEME://conf.suite.SERVER_AND_PORT.

    In this particular case, as Eliot mentioned, there's an SSL handshake error in the logs which suggests you're using a self-signed certificate meaning it won't be trusted by the application server JDK when making the GET request.

    You can search here on Forum for this error for more information but basically the SSL handshare and the java.net.ConnectException: Connection refused: connect are not problems between APP_SERVER and MAIL_SERVER. Since this is failing even before sending the email, in the body rendering part, we can tell the issue is between APP_SERVER and WEB_SERVER in the GET request I describe above.

    To fix this simply configure these two settings in custom.properties to point to HTTP and APP_SERVER. For example:

    conf.suite.MAIL_SCHEME=http
    conf.suite.MAIL_SERVER_AND_PORT=myappserver.mycompany.com:8080

    and restart it. This way the GET request made by the app server will be made to itself and not the web server, which is indeed not required.
Reply
  • 0
    Appian Employee
    The application server makes a GET request via conf.suite.MAIL_SCHEME://conf.suite.MAIL_SERVER_AND_PORT to retrieve the JSP that will be used as a template to render the body of the email. This step is called "Rendering the email body". If these settings are not defined the URL defaults to
    conf.suite.SCHEME://conf.suite.SERVER_AND_PORT.

    In this particular case, as Eliot mentioned, there's an SSL handshake error in the logs which suggests you're using a self-signed certificate meaning it won't be trusted by the application server JDK when making the GET request.

    You can search here on Forum for this error for more information but basically the SSL handshare and the java.net.ConnectException: Connection refused: connect are not problems between APP_SERVER and MAIL_SERVER. Since this is failing even before sending the email, in the body rendering part, we can tell the issue is between APP_SERVER and WEB_SERVER in the GET request I describe above.

    To fix this simply configure these two settings in custom.properties to point to HTTP and APP_SERVER. For example:

    conf.suite.MAIL_SCHEME=http
    conf.suite.MAIL_SERVER_AND_PORT=myappserver.mycompany.com:8080

    and restart it. This way the GET request made by the app server will be made to itself and not the web server, which is indeed not required.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.