There are a lot of different ways you could do this.
If you have a license for SDL Audience Manager and Outbound E-mail, I would recommend using that. Audience Manager comes with sample ASP.NET and JSP pages that show how you can create a new Contact and sign them up for a newsletter.
You can then use Triggered Mailings in Outbound E-mail to send out the ...
Error reading contents of xml file: formdata.xml for session TWF_B1FD2C99DCD508DA73725176F4BA7FE130E06C4F, Premature end of file., Premature end of file.
It looks like above error causes due to the formdata.xml contains invalid XML.
So when it reaches to getComponentPresentation, function gets values as text and not the tcm id.
And also I suspect that:
If your Tridion webform is running under the SDL CMS website and CMS url having https means you need to have certificate to access the site.
As per my knowledge tridion webform use one "webformWS" webservice and it must be installed some where in IIS.
Please check the webservice named with Webform in your IIS and check the property.
as per your ...
DXA 1.6 provides basic support for HTML Forms. See http://docs.sdl.com/LiveContent/content/en-US/SDL%20DXA-v6/GUID-2C331449-7CF4-4031-8080-85B3F478F700
This support includes:
Support for managing form text (labels, validation messages) in CM
Support for doing server-side validation and View Model mapping of form fields
Support for preventing CSRF attacks
Yes you can achieve that but it is not recommended. It is available mainly for backward compatibility purposes. If you would like to configure in that way, follow the sdl docs to show the publication targets in CME as like in Tridion 2013 SP1 and implement the legacy style .NET web app with cd_storage_conf.xml specified in the config folder under the webapp\...
My limited understanding of how this works is as follows.
When an ASP.NET HTTP module first accesses the POST data for a particular HTTP request, the stream containing the request body is consumed, parsed into the ASP.NET request context and then disposed. From this point on, the POST data is not available to any native IIS modules, which run outside of ASP....
It seems to be some logical error, as clearly visible in your message that ComponentPresentationFactory.getComponentPresentation(String, String) is expecting both component and template prefixed with "tcm"
Have you checked this?