Re: Setting up SMTP Mailing service
Reply #15 –
Keep your notes, because at some point when it stops working, you'll want to get things configured "correctly" to be sure the problem isn't related to the "misconfiguration" that is "working anyway" at the moment..
Re: Setting up SMTP Mailing service
Reply #25 –
Set up the email account(s) for your foum on your host like you would any other type of email account.
You will want at least an account for elkArte to use to send and receive emails (copies/notifications of forum posts, newsletters, whatever..), and one for webmaster communications. If you are going to allow Post By Email, that will be a different set of issues, let's crawl before trying to stand and run..
Now, go into ElkaArte Admin and configure communications to use each account.
That's all you have to do.
If it doesn't work right, or at all, then debug the EA configuration, and/or figure out what's going on with the host SMTP email handling.
It's been more than 5 years now since I set up email communications with ElkArte so I'm going to have to think/look back, but as I recall, this part was very simple. (What took some trickery was the fact that I have about 20 "boards" and PBE, and some fun cron jobs running to make that work). I think I had to work with spuds a bit to resolve some legacy issues in the php sendmail (EA v 1.16), but those have been corrected in later releases..
The only time I've ever had any issues with sending and receiving email with EA is when my host's email servers were "updated " and the new configurations broke the process, that my host had to go back in and fix..
So, make sure you have your own separate "user" (in addition to admin or "webmaster" account) and email addy for it, so you can "test" what your users will see, but more important, see when stuff just mysteriously stops working and know your host just did something to the email server!
Forget Sendgrid, don't worry about anything re: php unless your testing shows there's a problem there, and if you can't figure that out, come to us and we can focus on solving the problem rather than finding a suitable bandaid or work around that nobody has ever used before..
Your host's email doesn't know or care where on the server domain EA resides, and EA doesn't care where it is either - mydomain.com/forum, or forum.mydomain.com/forum, it doesn't matter when it comes to email handling. EA just needs to know the email account addy, and credentialing to get into it. The host's email has no idea where the account access attempt is coming from(*), just needs to know it had the right credentialing.
*exception: there's some handshaking and checks that now goes on between the SMTP email server and the accessing "client" (EA in this case) for security purposes, but that should be moot if EA is on the same box as the server - there should be no 'security 'handshaking" you have to worry about in that situation.
What I recommend is to close down this thread, and the Email template thread, then start over - reconfigure your installation for local host email, and create a new email thread if you run into problems, based on resolving the problem, not trying to configure the workaround attempt. Trust EA to work as intended "out of the box" and don't try to deal with theoretical problems unless you actually encounter them. If they do manifest, then fix it, rather than try to sidestep it.
Oh, and unless there's a very good reason to operate in a subdomain, don't complicate things unnecessarily.
[EDIT: I believe C-Panel softaculous has listserve support/ties at the server level, which may (or may not) be an easier/more elegant solution if your forum becomes so successful it outgrows your host's email volume tolerance. But worry about dealing with that problem only if you actually encounter it.