You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Won't work out of the box. Not sure if I should integrate this into the simplified installer or not.
Don't want to end up with too much fields either (Mailserver host, email address, password, optional port) Could move email credentials to /../security.php and force a no-reply@ setting (fewer field)
This still urges user to create mail user straight away..
Making mailing work with same mailserver on installed webserver: 1) Create the user no-reply@yourdomain.ex, note your settings. (yourdomain.ex must match your website address) 2) In /src/Data/UserDAO.php match these settings on lines 295, 298 and optinally 300 (SMTP port)
Moved to app/config/config.php, settings are initialized for SMTP. No SMTP? Change email() function in UserDAO.php
Good practice might be to troubleshoot your no-reply@domainname.ex first without the application. Can you send (/receive)?
The text was updated successfully, but these errors were encountered:
Won't work out of the box. Not sure if I should integrate this into the simplified installer or not.
Don't want to end up with too much fields either (Mailserver host, email address, password, optional port)
Could move email credentials to /../security.php and force a no-reply@ setting (fewer field)This still urges user to create mail user straight away..
Making mailing work with same mailserver on installed webserver:1) Create the user no-reply@yourdomain.ex, note your settings. (yourdomain.ex must match your website address)2) In /src/Data/UserDAO.php match these settings on lines 295, 298 and optinally 300 (SMTP port)Moved to app/config/config.php, settings are initialized for SMTP. No SMTP? Change email() function in UserDAO.php
Good practice might be to troubleshoot your no-reply@domainname.ex first without the application. Can you send (/receive)?
The text was updated successfully, but these errors were encountered: