#Process Model #Delete Folder # Object Moved Email Have a process mod

That doesn't seem to be related to the Delete Folder smart service itself, it seems you deleted one of the email templates.

What's the URL you see (sanitize the server name before pasting but leave the rest) if you do a right click in the "may be found here" link -> Properties?

If we configure the email templates are the issue I'll let you know what script will restore them

It seems there's an issue with this file

runtime_ear|ear|suite.ear\\web.war\
tf\\emailHtml\\rocessModelPublishingParent_emailHtml.jsp

1. Does the URL look the same in all emails you have received of this type?
2. How many files do you have under runtime_ear|ear|suite.ear\\web.war\
tf\\emailHtml
3. What version of Appian is this?
4. Can you double check these settings on your application server's custom.properties and make sure they look exactly like these ones

conf.suite.MAIL_SCHEME=http
conf.suite.MAIL_SERVER_AND_PORT=localhost:8080

1) yes the urls look same
server.com/.../newTaskOthers_emailHtml.jsp
2) There are 70 files. guess all are .jsp files (attached list of files)
3 ) 7.4 version
4) yes MAiL_SCHEME property is set to http.
MAIL_SERVER_AND_PORT , dont you expect to have the internal mail server and port rather than localhost:8080. I am waiting on the server admin to verify that,

appian-emailFiles.txt

Based on what you have posted here I think everything looks good except for 4). You need to make sure these two properties look exactly as below

conf.suite.MAIL_SCHEME=http
conf.suite.MAIL_SERVER_AND_PORT=localhost:8080

these settings are used to retrieve and later populate the JSP required to render the email body, since these JSPs are NOT static content and they are stored in the app server, the values above have to be exactly those in custom.properties on JBoss to guarantee JBoss uses its "own URL" to render the mail body bypassing the web server, since this is dynamic content then there's no need to pass the request through the web browser. It seems that is the root cause.

Thank you Eduardo. correcting the MAIL_SERVER_AND_PORT to localhost:8080 solved the issue