Forum Replies Created
The instructions “Add a 2nd Domain” have been updated to work in the foreign key environment. Cursory testing of the new domain has been performed but as per the warning in this topic, you should fully test all the features you wish to use prior to putting your new domain into production.
The foreign key logic breaks the alternate domain logic. I need to do a deep dive on it for a fix.
Concerning site thinking you are a bot, did you have and check the reCaptcha “I’m not a robot” box? It is something that I added recently to help assure that real people are signing up and sending messages on this site.
I just uploaded an update that add a set_aging flag field to the si_preferences table. When loaded, the first access will update the database and set this field to 1 (true) for the preference ID of 1. All others will be 0 (false). You can then set the other preference records however you like to cause them to set the aging field. So no longer will the aging logic be tied to pref_id of 1, but to this new flag field setting.
I’ll have to look at the domain_id write up. It was written before I added foreign keys and likely does need to be updated to account for this.
What is the meta http-equiv line setting in your template?
I was able to send email through my comcast ISP account. Not that it used port 587 for SSL. You might try the SSL setting rather than TLS on yours.
I did load some updates on github and recommend you pull them before you continue testing. The changes adds additional LOG statements to trace activity via the si.log file and also adds error handling in the case of thrown error messages that previously were not reported.
Let me know how this works out.
I run my development system on Win 10 using xampp. I run my production system on a Namecheap server for a hosting package I have from which I host a number of websites including my production SI site. I currently use the smtp server through my namecheap site for both development and production. In the past, I have also used smtp through my Comcast and Gmail accounts. I haven’t tried those servers since switching to Swiftmailer but I will give them a try on my development system.
Anything I suggest you try is just throwing ideas against the wall and seeing if one sticks. For instance, you can try using port 587 and TLS which is semi-standard. However, the bottom line is what you host email provider requires. So again I suggest you contact them to have them review their logs and tell you why your authentication is being rejected.
Did you follow the four steps at http://datatables.net/tn/1 to find the data transmitted? What did it show?
To upload the file, you will need to either put it in a zip file or (I think this will work) rename it to be a txt file rather than an sql file.