{ "id": "159523", "key": "AC-3497", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12217", "key": "AC", "name": "Appcelerator - INBOX", "projectCategory": { "id": "10000", "description": "", "name": "Customer Service" } }, "resolution": { "id": "6", "description": "", "name": "Hold" }, "resolutiondate": "2016-05-04T18:35:49.000+0000", "created": "2016-04-12T19:09:49.000+0000", "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2016-05-04T18:35:49.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [], "description": "When I set up email settings in my ArrowDB instance, the google SMTP server works just fine (no errors). However, using my own SMTP server is causing issues - when I save settings, I get the error \"The SMTP settings are not valid.\" which is not at all descriptive. Our SMTP server doesn't even show any logs suggesting the Appcelerator server is trying to connect, so there is absolutely no way to figure out what is wrong.\r\n\r\nPlease advise what to do in that case. Can the ArrowDB be fixed to provide a more descriptive error when it is \"testing\" SMTP settings during \"Save Changes\"?", "attachment": [], "flagged": false, "summary": "Provide ips of api and upload nodes for smtp whitelisting", "creator": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "382515", "author": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~parijatsahai], this is a copy of the case, it was moved internally for work. \r\n\r\nThe IP addresses aren't static and are subject to change every time we update the cloud infrastructure. Though we are working on a permanent solution to this. \r\n\r\nI suggest testing that a firewall is the issue. Here are some steps for testing your smtp server remotely:\r\n\r\n*auth setup*\r\n{code}\r\necho -n \"\\000emailaddress@email.com\\000password\" | openssl base64 //resultingPassword\r\n{code}\r\n\r\n*Send the email*\r\n{code}\r\nopenssl s_client -connect :PORT\r\nAUTH PLAIN resultingPassword\r\n235 2.0.0 OK\r\nmail from: \r\n250 2.1.0 Ok\r\nrcpt to: \r\n250 2.1.5 Ok\r\ndata\r\n354 End data with .\r\nFrom: Me \r\nTo: Me \r\nSubject: Testing this\r\n \r\nIt is a test!\r\n.\r\n250 2.0.0 Ok: queued as 65896680117\r\nquit\r\n221 2.0.0 Bye\r\nclosed\r\n// Mail gets received successfully\r\n{code}", "updateAuthor": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-04-12T19:17:44.000+0000", "updated": "2016-04-12T19:18:06.000+0000" }, { "id": "382523", "author": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "body": "Please send us the IP addresses anyway for now to test with. We definitely have a firewall that prevents ANY outside connection unless it is whitelisted IP address. So, if the IP addresses for Appcelerator change, that is certainly not a good thing and should be addressed sooner rather than later. But for the short term, I need the IP addresses. And whenever they change again, I'd like Appcelerator to resend the new IP addresses or provide me with instructions to retrieve them on my own.\r\n\r\nHow do other customers of Appcelerator handle the SMTP server issue - I'd assume most if not all of them would have firewalls.", "updateAuthor": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "created": "2016-04-12T19:43:25.000+0000", "updated": "2016-04-12T19:43:25.000+0000" }, { "id": "382526", "author": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "body": "\r\n52.37.208.23 52.38.180.221 52.33.16.197\r\n", "updateAuthor": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-04-12T20:08:35.000+0000", "updated": "2016-04-12T20:08:35.000+0000" }, { "id": "382604", "author": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "body": "We whitelisted the ip addresses and ran the test as you suggested as well, but although below test was successful, the SMTP settings on Appcelerator platform continue to give us the same error message as before. Hence, the issue is elsewhere.\r\n\r\nroot@server:~# openssl s_client -starttls smtp -connect mail.rekonnex.com:587 -quiet -CApath /usr/lib/ssl\r\ndepth=2 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate Signing, CN = StartCom Certification Authority\r\nverify return:1\r\ndepth=1 C = IL, O = StartCom Ltd., OU = StartCom Certification Authority, CN = StartCom Class 1 DV Server CA\r\nverify return:1\r\ndepth=0 CN = rekonnex.com\r\nverify return:1\r\n250 DSN\r\nAUTH PLAIN\r\n334 \r\n\r\n235 2.7.0 Authentication successful\r\nmail from:help@rekonnex.com\r\nrcpt to:admin@rekonnex.com\r\ndata\r\nfrom:help@rekonnex.com\r\nto:admin@rekonnex.com\r\nsubject: Email Test from Help Account for Appcelerator\r\nThis is a test email\r\n.\r\n250 2.1.0 Ok\r\n250 2.1.5 Ok\r\n354 End data with .\r\n250 2.0.0 Ok: queued as 3E9A3129594", "updateAuthor": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "created": "2016-04-13T15:58:54.000+0000", "updated": "2016-04-13T15:58:54.000+0000" }, { "id": "382611", "author": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "body": "As per our tech person, he suspects the following:\r\n\r\n\"they do not have our root CA in their list of trusted certs\"\r\n\r\nWe use StartCom’s root cert. Can you please check if that is a possible issue? \r\n", "updateAuthor": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "created": "2016-04-13T16:43:39.000+0000", "updated": "2016-04-13T16:43:39.000+0000" }, { "id": "382638", "author": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "body": "[~parijatsahai], I would suggest trying the different login methods, \"plain\", \"login\", etc", "updateAuthor": { "name": "stoda", "key": "stoda", "displayName": "Seth Toda", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2016-04-13T18:39:37.000+0000", "updated": "2016-04-13T18:39:37.000+0000" }, { "id": "382642", "author": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "body": "Please elaborate.", "updateAuthor": { "name": "parijatsahai", "key": "parijatsahai", "displayName": "Parijat sahai", "active": true, "timeZone": "America/New_York" }, "created": "2016-04-13T19:29:27.000+0000", "updated": "2016-04-13T19:29:27.000+0000" } ], "maxResults": 9, "total": 9, "startAt": 0 } } }