I hope not, otherwise there would be no email anymore.
Although… maybe that would be a good idea.
I understand what you mean, but your statement is incorrect and misleading.
to add to this - I’ve used the “coming soon 2” template to create the simple landing page you see
I used the default component ‘form’ and didn’t edit any source code (would not know where to start!)
I was heavily into Wordpress before joining Elements Beta almost at the beginning - I am NO expert at all so the help being provided is very much appreciated! 
Some ISPs don’t require authentication because the customer is identified via login.
There is also a small bug in generating config.php; the smtp_auth parameter always remains true, even if you haven’t specified a username and password. 
@ben Did you know that?
My host does require authentication for SMTP as I have multiple email accounts set up with them already for other purposes not related to this issue
I have not tried ‘no authentication’ however, but I guess it’s worth a try just in case, then I’ll have covered most of the things I can think of and what has been suggested so far
thank you
Not at all, port 25 is often blocked by default by most hosts and only opened if explicitly requested by the client. Of course there are some web hosts that don’t block 25 by default, but that number is decreasing steadily, kinda like insecure http sites (port 80) have been declining since all the browser companies started throwing security warnings for unencrypted sites.
Ports 465 and 587 are pretty much default now.
Edit: To clear up any semantics, I’m referring to web hosts blocking outgoing mail from being sent over port 25 for customer accounts on their servers due to potential Spam abuse, not the complete blocking of port 25 across the board. 
I have just tried it with ‘encryption’ set to ‘None’ and problem persists - no error messages on my page when submitting but the same little ‘flicker’ on the page on clicking submit then no error message or success message and no email comes through
I’ve also tested the ‘send only’ account to make sure it works and emails sent to the send only address are coming through to the default main contact email address I want it to for this website
Sent you a DM.
You won’t find a physical /email folder inside the api directory — and that’s completely expected.
The API is built using a router-based system, which means URLs like /api/email are virtual routes, not actual folders. When you make a request to /api/email, the request is routed internally by the app (via the api/index.php file) to the appropriate function or controller that handles email sending.
So even though the folder structure doesn’t show an email subdirectory, the logic for handling /email is still there, it’s just happens behind the scenes.
Please don’t do this, as it’ll cause issues with routing the requests correctly! 
thanks for the heads up, I’ll get that fixed ASAP!
Thank you. 
