Platform
Learn
Community
Support
Partner Center
Sign up
or
Log in
logout
Account Settings
Profile
messages
Messages
logout
Logout
Platform
Home
Downloads
IPP
Licensing
Project Sizing
Learn
Training
Documentation
Evaluation Guide
What's New
Community
Home
Forums
Forge
Ideas
Members
Support
Partner Guide
Resources Library
Opportunities
Account Management
Sign up
or
Log in
Home
Forums
Forge
Ideas
Members
Dear ,
What would improve your OutSystems Community experience? Let us know by taking this 2-minute survey.
Pick up the survey
Community
›
Forums
›
Technology & Integration
Outsystems 5.1 / SSL / SMTP Problem
Community
›
Forums
›
Technology & Integration
Outsystems 5.1 / SSL / SMTP Problem
New Post
New Post
Paulo Moreira
Posted on 2011-04-26
Paulo Moreira
Rank: #6309
Posted on 2011-04-26
Good afternoon,
Our client has an Outsystems 5.1 infrastructure, and recently acquired and installed a Certificate on the Production Server, to allow secure outside access to their Outsystems Applications.
One of the features developed was the ability for sending automatic notifications by email, using one of the Client's SMTP Servers. Problem is, after the certificate was installed, the sending of those email messages stopped working, returning the following error:
Error creating Email. The remote server returned an error: (403) Forbidden.
Is there any aditional configuration setting we have to make on the Outsystems Platform, or on the Clients SMTP Server (i.e. change the protocol from SMTP to Secure SMTP)?
Fact: One of the Client's system administrators was able to relay an email message manualy, by establishing a telnet session on port 25 to the SMTP server.....
Client is running Outsystems 5.1.1.16 on Windows Server 2003, with a remote SQL Server instance.
Has anyone already came accross with such a scenario?
Thank you all in advance.
Ricardo Araújo
Posted on 2011-04-27
Ricardo Araújo
Rank: #87
Posted on 2011-04-27
Solution
Hi Paulo,
can you give the detail of that error log?
Thanks
RNA
Solution
Paulo Moreira
Posted on 2011-04-27
Paulo Moreira
Rank: #6309
Posted on 2011-04-27
Solution
Good morning Ricardo,
As requested, here is the error log:
at System.Net.HttpWebRequest.GetResponse()
at OutSystems.HubEdition.RuntimePlatform.Email.EmailHelper.HttpGetContent(String ssUrl, String method, String contentType, String userAgent, Cookie cookie, QueryParameter[] parameters, String& ssContent, String& ssContentEncoding)
at OutSystems.HubEdition.RuntimePlatform.Email.EmailHelper.HttpPost(String ssUrl, QueryParameter[] parameters, String userAgent, Cookie cookie, String& ssContent, String& ssContentEncoding)
at OutSystems.HubEdition.RuntimePlatform.Email.EmailProcessor.SendEmailRequest(String url, String from, String to, String cc, String bcc, Int32 activityId, String emailDefSSKey, Boolean storeContent, EmailType type) On
at OutSystems.HubEdition.RuntimePlatform.Email.EmailProcessor.SendEmailRequest(String url, String from, String to, String cc, String bcc, Int32 activityId, String emailDefSSKey, Boolean storeContent, EmailType type)
at ssSIOP.Flows.FlowLoginFlow.ScrnPopup_RecuperarPassword.CommandEnviar_Ajax(HeContext heContext)
-Env-
eSpaceVer: 20 (Id=218, PubId=341, CompiledWith=5.1.1.16)
RequestUrl: https://192.168.211.24/siop/Popup_RecuperarPassword.aspx
AppDomain: /LM/W3SVC/1/Root/SIOP-1-129483004702799524
FilePath: C:\...\PS\running\SIOP.1081032105\Popup_RecuperarPassword.aspx
Locale: pt-PT
DateFormat: yyyy-MM-dd
PID: 4356 ('w3wp', Started='4/26/2011 1:59:27 PM', Priv=128Mb, Virt=5448Mb)
TID: 11
.NET: 2.0.50727.3620
Thank you very much in advance.
PM
Solution
Ricardo Araújo
Posted on 2011-04-27
Ricardo Araújo
Rank: #87
Posted on 2011-04-27
Solution
Hi,
that seems to be a http error and not a smtp problem.
Did you published the solution after you installed the certificate?
RNA
Solution
Paulo Moreira
Posted on 2011-04-27
Paulo Moreira
Rank: #6309
Posted on 2011-04-27
Solution
Ricardo,
The solution was fully published after the installation of the Certificate.
PM
Solution
João Rosado
Posted on 2011-05-02
João Rosado
Rank: #13
Posted on 2011-05-02
Solution
Hi Paulo,
Did you turn off http connections completly to force the https? It's required to allow http in local connections (127.0.0.1:80).
If that is not your problem, try checking your IIS logs to see what request is actually returning the 403.
Regards,
João Rosado
Solution
Quick Reply
attachment
Choose File
No file chosen
Submit
Login to reply
New Post
Available Forums
Technology & Integration
News and Announcements
Forge Discussions
Meta
Community Quick Guides
Usability
Installation Troubleshooting
Personal Environment Troubleshooting
Forum Notifications
Email Digest Settings
Loading...