Re: [WebDNA] Help with STMP Setup using Authentication with Google

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113289
interpreted = N
texte = 882 Hi folks, Just wanted to report back to the community on using sendmail with = WebDNA 8.2 in a macOS Sierra environment. I suspect that=E2=80=99s = something is going is going on with whatever process WebDNA is using to = craft & send out email. WebDNA is clearly able to interact and = authenticate with a third-party service (Because it will report a = Success when the correct information is entered - - - i.e. checking the = Email Folders & Email log on the server - - - - but fail with a general = email error when deliberately using incorrect authentication = information). Also done testing with manual STMP logins in the command = line. Furthermore, I=E2=80=99ve had no success being able to using mail = services on localhost to generate email messages either, which is what = we have been able to use on our production server in the past. So, I=E2=80=99m planning to submit a request to @support to report the = issue and see if I can gather additional information and feedback. To = that end, does any one have knowledge on exactly what process WebDNA = uses to both queue, create, and send the email through the sendmail = call? Does it rely on built-in modules? Apache-mods? Assume certain = components are in the OS? I=E2=80=99d really like to be able to debug = the process so I can do additional investigation on my own but also = provide more feedback to the support team when I inevitably get asked=E2=80= =A6 Thanks for all the helpful suggestion so far! Andrew Burger > On Dec 22, 2016, at 9:10 PM, Andrew Burger = wrote: >=20 > Hmm, that=E2=80=99s good to know. Thanks! >=20 > Andrew Burger >=20 >=20 >> On Dec 22, 2016, at 8:03 PM, Donovan Brooke wrote: >>=20 >> currently the only encryption option is TLS (unless I missed = something), so yes, uncheck is PLAIN.=20 >>=20 >> Donovan >>=20 >>=20 >>=20 >> On Dec 22, 2016, at 2:00 PM, Andrew Burger = wrote: >>=20 >>> Hi Tom, >>>=20 >>> Yes - I was aware of this setting but I tried this anyway. No = success. You usually get an email message if an insecure app tries to = access your account like that. Also tried the UnlockCapta option too to = see if that was involved in blocking somehow. >>>=20 >>> I=E2=80=99m looking into the SMTP authentication handshake like = Donovan suggested. The more I think about it, the more that I=E2=80=99m = more inclined to think it has something to do with the SSL communication = with certificates over port 465 (587 doesn=E2=80=99t seems to work even = though it=E2=80=99s an option), the particular way in which Google = accepts user logins & application passwords in an SMTP session, or = perhaps even the MX / security settings associated on Google=E2=80=99s = end. I=E2=80=99m starting there first and then circle back to WebDNA = once I eliminate a bunch of those variables. >>>=20 >>> A question on the implementation for the Email Setup (WebDNA = Preferences). For the checkbox that says Require TLS, I assume that = means it will try to communicate through an encrypted TLS connection = (and in my case, over port 465) when checked. However, if the TLS box = unchecked, put in the User Authentication Information, and specify port = 465, what type of connection is used? Does it initiate an unencrypted = connection through that specified port (like you would typically do with = say=E2=80=A6 port 25=E2=80=A6) or does it open an encrypted connection = over SSL to port 465? It would be helpful to understand the logic of = how it tries to connect when NOT requiring TLS. >>>=20 >>> Thanks again guys! >>>=20 >>>=20 >>> Andrew Burger >>>=20 >>>> On Dec 22, 2016, at 10:54 AM, Tom Duke = wrote: >>>>=20 >>>> Andrew, >>>>=20 >>>> Hi - if you're trying to deal with Gmail / Google Apps maybe you = have to "allow less secure access" to your account: >>>>=20 >>>> https://support.google.com/accounts/answer/6010255?hl=3Den >>>>=20 >>>> - Tom >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Digital Revolutionaries >>>> 1st Floor, Castleriver House >>>> 14-15 Parliament Street >>>> Temple Bar,Dublin 2 >>>> Ireland >>>> ---------------------------------------------- >>>> [t]: + 353 1 4403907 >>>> [e]: >>>> [w]: >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>=20 >>>> On 22 December 2016 at 01:27, Donovan Brooke = wrote: >>>> Google "smtp telnet" test. >>>>=20 >>>> Do your test with the server you are using, via the terminal. >>>>=20 >>>> D. Brooke Mobile >>>>=20 >>>>> On Dec 21, 2016, at 4:40 PM, Andrew Burger = wrote: >>>>>=20 >>>>> Of course. It's a possibility with a new release of a relatively = new OS. Do you (or anyone) have any feedback or knowledge of being able = to get SMTP Authentication to work with Google Apps at all? Or other = widely implemented cloud-hosted email services? Yes - I do acknowledge = the unique weirdness sometimes associated with Google Services in = general compared to other standard email approaches. >>>>>=20 >>>>> The new server machine is powered Server (under-the-hood Apache = 2.2), which ran and is practically unchanged from El Capitan (OS X = 10.11), at least in respect to the Website services=E2=80=A6 Do you = happen to know if sendmail / WebDNA 8 has similar problems under El = Capitan? It would be really helpful if anyone could verify that = something like this has worked before going down the route of starting = up a whole new test server. I=E2=80=99d also prefer not to go too far = back on the OS version, as that=E2=80=99s one of the major reasons for = the server migration to begin with=E2=80=A6 >>>>>=20 >>>>> Donovan - Definitely appreciate the help and time you=E2=80=99ve = put in so far and any additional insight you are willing to give. = Keeping my fingers crossed... >>>>>=20 >>>>> If anyone else has any experience with running WebDNA 8 on = relatively recent OS X/macOS versions, please feel free to pipe in too. >>>>>=20 >>>>>=20 >>>>> Thanks again! >>>>>=20 >>>>>=20 >>>>> Andrew Burger >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On Dec 21, 2016, at 8:56 PM, Donovan Brooke = wrote: >>>>>>=20 >>>>>> Hi Andrew, >>>>>> I=E2=80=99m sure it helps, but I haven=E2=80=99t worked on this = OS (sierra) in a server capacity. >>>>>> This is where I=E2=80=99ll have to pass off to someone else :-) >>>>>>=20 >>>>>> (My hunch is that the problem is something to do with that OS) >>>>>>=20 >>>>>> Donovan >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On Dec 21, 2016, at 2:02 PM, Andrew Burger = wrote: >>>>>>>=20 >>>>>>> We are moving from a machine with OS X 10.8.5 (Mountain Lion) to = macOS 10.12.2 (Sierra - latest public build). WebDNA is using Server = Unlimited license on both. Partly why we are going through this=E2=80=A6 >>>>>>>=20 >>>>>>> Here=E2=80=99s some quick information from WebCatalog to help = you better understand our environment. >>>>>>>=20 >>>>>>> Mountain Lion Statistics (Old machine): >>>>>>>=20 >>>>>>> WebDNA - Enterprise Edition is currently in Full-Working = Unlimited mode >>>>>>> This serial number is licensed to run 1 copy >>>>>>> This serial number is licensed to run Unlimited = Domains >>>>>>> This serial number is licensed to open Unlimited = databases at one time >>>>>>> WebDNA - Enterprise Edition is running as unix-Macintosh = OS X Apache Module version 6.2 >>>>>>>=20 >>>>>>> Sierra Statistics (New machine): >>>>>>>=20 >>>>>>> WebDNA - Enterprise Edition is currently in Full-Working = Unlimited mode >>>>>>> This serial number is licensed to run 1 copy >>>>>>> This serial number is licensed to run Unlimited = Domains >>>>>>> This serial number is licensed to open Unlimited = databases at one time >>>>>>> WebDNA - Enterprise Edition is running as unix-Macintosh = OS X Apache Module version 8.2 >>>>>>>=20 >>>>>>>=20 >>>>>>> Hope that helps! >>>>>>>=20 >>>>>>>=20 >>>>>>> Andrew Burger >>>>>>>=20 >>>>>>>=20 >>>>>>>> On Dec 21, 2016, at 7:35 PM, Donovan Brooke = wrote: >>>>>>>>=20 >>>>>>>> Is this a different operating system than the 6 server? If so, = what OS and version? >>>>>>>>=20 >>>>>>>> Is this the latest WebDNA Server 8 version? >>>>>>>>=20 >>>>>>>> Donovan >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On Dec 21, 2016, at 1:30 PM, Andrew Burger = wrote: >>>>>>>>>=20 >>>>>>>>> Hi Donovan. >>>>>>>>>=20 >>>>>>>>> Excellent question. Not using server sandboxes in this case = (because this is not a shared server situation). We are using a = dedicated physical server for this. >>>>>>>>>=20 >>>>>>>>> We can do whatever is needed on the server in every respect, = with the exception of what I=E2=80=99m trying to pass through Google = Apps with Auth/SMTP, etc. Ideally, I=E2=80=99d prefer not configure / = troubleshoot / secure-harden mail services there (since that is a real = pain) if possible. But, that being said, I=E2=80=99ll do what I have to = do. ;-) >>>>>>>>>=20 >>>>>>>>> Also, thanks for the note regarding bug reporting. Now that I = have the info from email notices, I=E2=80=99ll go ahead and report that. >>>>>>>>>=20 >>>>>>>>> Thanks! >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Andrew Burger >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>> On Dec 21, 2016, at 6:40 PM, Donovan Brooke = wrote: >>>>>>>>>>=20 >>>>>>>>>> One common mistake (I still make this mistake sometimes)=E2=80=A6= >>>>>>>>>> Are you using WebDNA Server SandBoxes by chance? >>>>>>>>>>=20 >>>>>>>>>> Regarding bug reporting, there is a link at the bottom of = this email. >>>>>>>>>>=20 >>>>>>>>>> Sincerely, >>>>>>>>>> Donovan >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On Dec 21, 2016, at 12:11 PM, Andrew Burger = wrote: >>>>>>>>>>>=20 >>>>>>>>>>> Hello Everyone, >>>>>>>>>>>=20 >>>>>>>>>>> Objective: >>>>>>>>>>> We are currently in the middle of migrating our production = WebDNA 6 server to a new one with WebDNA 8. The remaining piece left to = get working is having WebDNA send out email message via the sendmail = command. >>>>>>>>>>>=20 >>>>>>>>>>> Current Setup: >>>>>>>>>>> The current production WebDNA 6 server works via localhost = (although exactly how that works is a little bit of a mystery to me = since we haven=E2=80=99t done any additional mail services setup on that = server but anyway=E2=80=A6). More to the point, I=E2=80=99ve been able = to get the current production WebDNA server to work, as long as the = proper SPF record was in place. So we have a working routine in = production now. >>>>>>>>>>>=20 >>>>>>>>>>> Steps Taken to Troubleshoot: >>>>>>>>>>> With the new WebDNA 8 server, I=E2=80=99ve been unable to = get the sendmail command to send out a valid message. I have done = verifications through WebDNA Email Folders. EmailCompleted have properly = processed the message and confirmed that it =E2=80=9Csent=E2=80=9D in = the Email log file. However, no message appears to go through to the = recipients. I=E2=80=99ve even gone through an additional setup of = setting up the G Suite SMTP relay server and whitelisted the originating = IP address of the new WebDNA server inside the Relay settings and = whitelisting the IP for emails in Google Admin for regular SMTP (in = addition to the proper SPF record like I did for the currently working = server). I haven=E2=80=99t gotten any SPF passes or rejections though, = so I=E2=80=99m not even entirely confident that it=E2=80=99s even = getting to Google servers yet for processing. >>>>>>>>>>>=20 >>>>>>>>>>> Has anyone else had any luck getting email authentication = working with Google Apps email? I would truly appreciate anyone that = has some insight from anyone that=E2=80=99s got this to work or whether = we can confirm if something has changed with the mechanism used for the = sendmail command between WebDNA 6 or 8... >>>>>>>>>>>=20 >>>>>>>>>>> Sorry if that=E2=80=99s a lot of information up front but = wanted to explain what I=E2=80=99m trying to accomplish and the steps = taken so far to generate some useful feedback. >>>>>>>>>>>=20 >>>>>>>>>>> Thanks so much and happy holidays! >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> Andrew Burger >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> PS - Pleased to meet all of you. Just subscribed to the = list and looking forward to getting to learn from the rest of you. >>>>>>>>>>>=20 >>>>>>>>>>> PPS - Also uncovered an issue in the WebCatalog Email Setup = preferences in WebDNA Server 8. It doesn=E2=80=99t appear to be = possible to uncheck STMP Auth and Require TLS through the web interface = once you enable it. Had to manually force the param value back to 0 = through a WebDNA call to switch back and test =E2=80=98localhost' = settings. Is there a proper way to report bugs like this or is already = a known issue?--------------------------------------------------------- >>>>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>>>> the mailing list . >>>>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>>>=20 >>>>>>>>>> --------------------------------------------------------- >>>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>>> the mailing list . >>>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>>=20 >>>>>>>>> --------------------------------------------------------- >>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>> the mailing list . >>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>=20 >>>>>>>> --------------------------------------------------------- >>>>>>>> This message is sent to you because you are subscribed to >>>>>>>> the mailing list . >>>>>>>> To unsubscribe, E-mail to: >>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>> Bug Reporting: support@webdna.us >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  2. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  3. Re: [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Donovan Brooke 2016)
  4. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  5. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  6. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Tom Duke 2016)
  7. Re: [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Donovan Brooke 2016)
  8. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  9. Re: [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Donovan Brooke 2016)
  10. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  11. Re: [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Donovan Brooke 2016)
  12. Re: [WebDNA] Help with STMP Setup using Authentication with Google (Andrew Burger 2016)
  13. Re: [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Donovan Brooke 2016)
  14. [WebDNA] Help with STMP Setup using Authentication with Google Apps in WebDNA (Andrew Burger 2016)
882 Hi folks, Just wanted to report back to the community on using sendmail with = WebDNA 8.2 in a macOS Sierra environment. I suspect that=E2=80=99s = something is going is going on with whatever process WebDNA is using to = craft & send out email. WebDNA is clearly able to interact and = authenticate with a third-party service (Because it will report a = Success when the correct information is entered - - - i.e. checking the = Email Folders & Email log on the server - - - - but fail with a general = email error when deliberately using incorrect authentication = information). Also done testing with manual STMP logins in the command = line. Furthermore, I=E2=80=99ve had no success being able to using mail = services on localhost to generate email messages either, which is what = we have been able to use on our production server in the past. So, I=E2=80=99m planning to submit a request to @support to report the = issue and see if I can gather additional information and feedback. To = that end, does any one have knowledge on exactly what process WebDNA = uses to both queue, create, and send the email through the sendmail = call? Does it rely on built-in modules? Apache-mods? Assume certain = components are in the OS? I=E2=80=99d really like to be able to debug = the process so I can do additional investigation on my own but also = provide more feedback to the support team when I inevitably get asked=E2=80= =A6 Thanks for all the helpful suggestion so far! Andrew Burger > On Dec 22, 2016, at 9:10 PM, Andrew Burger = wrote: >=20 > Hmm, that=E2=80=99s good to know. Thanks! >=20 > Andrew Burger >=20 >=20 >> On Dec 22, 2016, at 8:03 PM, Donovan Brooke wrote: >>=20 >> currently the only encryption option is TLS (unless I missed = something), so yes, uncheck is PLAIN.=20 >>=20 >> Donovan >>=20 >>=20 >>=20 >> On Dec 22, 2016, at 2:00 PM, Andrew Burger = wrote: >>=20 >>> Hi Tom, >>>=20 >>> Yes - I was aware of this setting but I tried this anyway. No = success. You usually get an email message if an insecure app tries to = access your account like that. Also tried the UnlockCapta option too to = see if that was involved in blocking somehow. >>>=20 >>> I=E2=80=99m looking into the SMTP authentication handshake like = Donovan suggested. The more I think about it, the more that I=E2=80=99m = more inclined to think it has something to do with the SSL communication = with certificates over port 465 (587 doesn=E2=80=99t seems to work even = though it=E2=80=99s an option), the particular way in which Google = accepts user logins & application passwords in an SMTP session, or = perhaps even the MX / security settings associated on Google=E2=80=99s = end. I=E2=80=99m starting there first and then circle back to WebDNA = once I eliminate a bunch of those variables. >>>=20 >>> A question on the implementation for the Email Setup (WebDNA = Preferences). For the checkbox that says Require TLS, I assume that = means it will try to communicate through an encrypted TLS connection = (and in my case, over port 465) when checked. However, if the TLS box = unchecked, put in the User Authentication Information, and specify port = 465, what type of connection is used? Does it initiate an unencrypted = connection through that specified port (like you would typically do with = say=E2=80=A6 port 25=E2=80=A6) or does it open an encrypted connection = over SSL to port 465? It would be helpful to understand the logic of = how it tries to connect when NOT requiring TLS. >>>=20 >>> Thanks again guys! >>>=20 >>>=20 >>> Andrew Burger >>>=20 >>>> On Dec 22, 2016, at 10:54 AM, Tom Duke = wrote: >>>>=20 >>>> Andrew, >>>>=20 >>>> Hi - if you're trying to deal with Gmail / Google Apps maybe you = have to "allow less secure access" to your account: >>>>=20 >>>> https://support.google.com/accounts/answer/6010255?hl=3Den >>>>=20 >>>> - Tom >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>> Digital Revolutionaries >>>> 1st Floor, Castleriver House >>>> 14-15 Parliament Street >>>> Temple Bar,Dublin 2 >>>> Ireland >>>> ---------------------------------------------- >>>> [t]: + 353 1 4403907 >>>> [e]: >>>> [w]: >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>=20 >>>> On 22 December 2016 at 01:27, Donovan Brooke = wrote: >>>> Google "smtp telnet" test. >>>>=20 >>>> Do your test with the server you are using, via the terminal. >>>>=20 >>>> D. Brooke Mobile >>>>=20 >>>>> On Dec 21, 2016, at 4:40 PM, Andrew Burger = wrote: >>>>>=20 >>>>> Of course. It's a possibility with a new release of a relatively = new OS. Do you (or anyone) have any feedback or knowledge of being able = to get SMTP Authentication to work with Google Apps at all? Or other = widely implemented cloud-hosted email services? Yes - I do acknowledge = the unique weirdness sometimes associated with Google Services in = general compared to other standard email approaches. >>>>>=20 >>>>> The new server machine is powered Server (under-the-hood Apache = 2.2), which ran and is practically unchanged from El Capitan (OS X = 10.11), at least in respect to the Website services=E2=80=A6 Do you = happen to know if sendmail / WebDNA 8 has similar problems under El = Capitan? It would be really helpful if anyone could verify that = something like this has worked before going down the route of starting = up a whole new test server. I=E2=80=99d also prefer not to go too far = back on the OS version, as that=E2=80=99s one of the major reasons for = the server migration to begin with=E2=80=A6 >>>>>=20 >>>>> Donovan - Definitely appreciate the help and time you=E2=80=99ve = put in so far and any additional insight you are willing to give. = Keeping my fingers crossed... >>>>>=20 >>>>> If anyone else has any experience with running WebDNA 8 on = relatively recent OS X/macOS versions, please feel free to pipe in too. >>>>>=20 >>>>>=20 >>>>> Thanks again! >>>>>=20 >>>>>=20 >>>>> Andrew Burger >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On Dec 21, 2016, at 8:56 PM, Donovan Brooke = wrote: >>>>>>=20 >>>>>> Hi Andrew, >>>>>> I=E2=80=99m sure it helps, but I haven=E2=80=99t worked on this = OS (sierra) in a server capacity. >>>>>> This is where I=E2=80=99ll have to pass off to someone else :-) >>>>>>=20 >>>>>> (My hunch is that the problem is something to do with that OS) >>>>>>=20 >>>>>> Donovan >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>> On Dec 21, 2016, at 2:02 PM, Andrew Burger = wrote: >>>>>>>=20 >>>>>>> We are moving from a machine with OS X 10.8.5 (Mountain Lion) to = macOS 10.12.2 (Sierra - latest public build). WebDNA is using Server = Unlimited license on both. Partly why we are going through this=E2=80=A6 >>>>>>>=20 >>>>>>> Here=E2=80=99s some quick information from WebCatalog to help = you better understand our environment. >>>>>>>=20 >>>>>>> Mountain Lion Statistics (Old machine): >>>>>>>=20 >>>>>>> WebDNA - Enterprise Edition is currently in Full-Working = Unlimited mode >>>>>>> This serial number is licensed to run 1 copy >>>>>>> This serial number is licensed to run Unlimited = Domains >>>>>>> This serial number is licensed to open Unlimited = databases at one time >>>>>>> WebDNA - Enterprise Edition is running as unix-Macintosh = OS X Apache Module version 6.2 >>>>>>>=20 >>>>>>> Sierra Statistics (New machine): >>>>>>>=20 >>>>>>> WebDNA - Enterprise Edition is currently in Full-Working = Unlimited mode >>>>>>> This serial number is licensed to run 1 copy >>>>>>> This serial number is licensed to run Unlimited = Domains >>>>>>> This serial number is licensed to open Unlimited = databases at one time >>>>>>> WebDNA - Enterprise Edition is running as unix-Macintosh = OS X Apache Module version 8.2 >>>>>>>=20 >>>>>>>=20 >>>>>>> Hope that helps! >>>>>>>=20 >>>>>>>=20 >>>>>>> Andrew Burger >>>>>>>=20 >>>>>>>=20 >>>>>>>> On Dec 21, 2016, at 7:35 PM, Donovan Brooke = wrote: >>>>>>>>=20 >>>>>>>> Is this a different operating system than the 6 server? If so, = what OS and version? >>>>>>>>=20 >>>>>>>> Is this the latest WebDNA Server 8 version? >>>>>>>>=20 >>>>>>>> Donovan >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>> On Dec 21, 2016, at 1:30 PM, Andrew Burger = wrote: >>>>>>>>>=20 >>>>>>>>> Hi Donovan. >>>>>>>>>=20 >>>>>>>>> Excellent question. Not using server sandboxes in this case = (because this is not a shared server situation). We are using a = dedicated physical server for this. >>>>>>>>>=20 >>>>>>>>> We can do whatever is needed on the server in every respect, = with the exception of what I=E2=80=99m trying to pass through Google = Apps with Auth/SMTP, etc. Ideally, I=E2=80=99d prefer not configure / = troubleshoot / secure-harden mail services there (since that is a real = pain) if possible. But, that being said, I=E2=80=99ll do what I have to = do. ;-) >>>>>>>>>=20 >>>>>>>>> Also, thanks for the note regarding bug reporting. Now that I = have the info from email notices, I=E2=80=99ll go ahead and report that. >>>>>>>>>=20 >>>>>>>>> Thanks! >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> Andrew Burger >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>> On Dec 21, 2016, at 6:40 PM, Donovan Brooke = wrote: >>>>>>>>>>=20 >>>>>>>>>> One common mistake (I still make this mistake sometimes)=E2=80=A6= >>>>>>>>>> Are you using WebDNA Server SandBoxes by chance? >>>>>>>>>>=20 >>>>>>>>>> Regarding bug reporting, there is a link at the bottom of = this email. >>>>>>>>>>=20 >>>>>>>>>> Sincerely, >>>>>>>>>> Donovan >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>> On Dec 21, 2016, at 12:11 PM, Andrew Burger = wrote: >>>>>>>>>>>=20 >>>>>>>>>>> Hello Everyone, >>>>>>>>>>>=20 >>>>>>>>>>> Objective: >>>>>>>>>>> We are currently in the middle of migrating our production = WebDNA 6 server to a new one with WebDNA 8. The remaining piece left to = get working is having WebDNA send out email message via the sendmail = command. >>>>>>>>>>>=20 >>>>>>>>>>> Current Setup: >>>>>>>>>>> The current production WebDNA 6 server works via localhost = (although exactly how that works is a little bit of a mystery to me = since we haven=E2=80=99t done any additional mail services setup on that = server but anyway=E2=80=A6). More to the point, I=E2=80=99ve been able = to get the current production WebDNA server to work, as long as the = proper SPF record was in place. So we have a working routine in = production now. >>>>>>>>>>>=20 >>>>>>>>>>> Steps Taken to Troubleshoot: >>>>>>>>>>> With the new WebDNA 8 server, I=E2=80=99ve been unable to = get the sendmail command to send out a valid message. I have done = verifications through WebDNA Email Folders. EmailCompleted have properly = processed the message and confirmed that it =E2=80=9Csent=E2=80=9D in = the Email log file. However, no message appears to go through to the = recipients. I=E2=80=99ve even gone through an additional setup of = setting up the G Suite SMTP relay server and whitelisted the originating = IP address of the new WebDNA server inside the Relay settings and = whitelisting the IP for emails in Google Admin for regular SMTP (in = addition to the proper SPF record like I did for the currently working = server). I haven=E2=80=99t gotten any SPF passes or rejections though, = so I=E2=80=99m not even entirely confident that it=E2=80=99s even = getting to Google servers yet for processing. >>>>>>>>>>>=20 >>>>>>>>>>> Has anyone else had any luck getting email authentication = working with Google Apps email? I would truly appreciate anyone that = has some insight from anyone that=E2=80=99s got this to work or whether = we can confirm if something has changed with the mechanism used for the = sendmail command between WebDNA 6 or 8... >>>>>>>>>>>=20 >>>>>>>>>>> Sorry if that=E2=80=99s a lot of information up front but = wanted to explain what I=E2=80=99m trying to accomplish and the steps = taken so far to generate some useful feedback. >>>>>>>>>>>=20 >>>>>>>>>>> Thanks so much and happy holidays! >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> Andrew Burger >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> PS - Pleased to meet all of you. Just subscribed to the = list and looking forward to getting to learn from the rest of you. >>>>>>>>>>>=20 >>>>>>>>>>> PPS - Also uncovered an issue in the WebCatalog Email Setup = preferences in WebDNA Server 8. It doesn=E2=80=99t appear to be = possible to uncheck STMP Auth and Require TLS through the web interface = once you enable it. Had to manually force the param value back to 0 = through a WebDNA call to switch back and test =E2=80=98localhost' = settings. Is there a proper way to report bugs like this or is already = a known issue?--------------------------------------------------------- >>>>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>>>> the mailing list . >>>>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>>>=20 >>>>>>>>>> --------------------------------------------------------- >>>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>>> the mailing list . >>>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>>=20 >>>>>>>>> --------------------------------------------------------- >>>>>>>>> This message is sent to you because you are subscribed to >>>>>>>>> the mailing list . >>>>>>>>> To unsubscribe, E-mail to: >>>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>>> Bug Reporting: support@webdna.us >>>>>>>>=20 >>>>>>>> --------------------------------------------------------- >>>>>>>> This message is sent to you because you are subscribed to >>>>>>>> the mailing list . >>>>>>>> To unsubscribe, E-mail to: >>>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>>> Bug Reporting: support@webdna.us >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> This message is sent to you because you are subscribed to >>>>>>> the mailing list . >>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>>> Bug Reporting: support@webdna.us >>>>>>=20 >>>>>> --------------------------------------------------------- >>>>>> This message is sent to you because you are subscribed to >>>>>> the mailing list . >>>>>> To unsubscribe, E-mail to: >>>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> This message is sent to you because you are subscribed to >>>>> the mailing list . >>>>> To unsubscribe, E-mail to: >>>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>>=20 >>>> --------------------------------------------------------- This = message is sent to you because you are subscribed to the mailing list . = To unsubscribe, E-mail to: archives: = http://mail.webdna.us/list/talk@webdna.us Bug Reporting: = support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us . Andrew Burger

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Assigning Serialized Customer Numbers (1997) webcatalog 2.1.3 ACGI Weirdness? (1998) Sending Faxes (2003) Fwd: [WebDNA] Fails to recognize comma-separated db (2010) different show next (1997) New commands in Final candidate (1997) Country & Ship-to address & other fields ? (1997) [WebDNA] Server load (2008) international time (1997) Protect (1997) WebSTAR 2.1 freezes my Mac (1997) Problem searching bw & ne of a word (1999) Setting up shop (1997) The future of WebCatalog is coming with 4.0... (2000) Web Site (2000) WebCat2 - Getting to the browser's username/password data (1997) Running 2 two WebCatalog.acgi's (1996) Sorry - the list went haywire... (1998) [WebDNA] Different results for [THISURL] (2018) WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)