Open Dental Forum

We just started trying the email function for recalls and have a few issues.
The first is that it seems that only the guarantor's email address gets used, even if the patient has their own email address entered.
Second, we set up a gmail account to use and we successfully sent about 25 emails, then we got an error whereby one address was incorrectly entered, so the process stopped. We correctly the address and when we restarted the process by refreshing the list and hitting the email button, we keep getting an error that says," The SMTP Server requires a secure connection or the client was not authenticated. The Server response was: 5.5.1 Authentication Required. Learn more at Patient: [OK].
I've got the SSL checked in the email setup and this error happens no matter which patient(s) is/are selected.

Any ideas on how to correct these "bugs"?
thanks,
rich

What version? Are you grouping by family or not?

As far as the authentication, do you have the SSL box checked in email setup?

v7.0, yes I'm grouping by families, which explains the use of guarantor's email, but the ssl box is checked and it did send the beginning of the list before I started getting this error. I've tried unchecking the SSL box, which gives a different error, then rechecking it, which returns the original error.
rich

I am using Version 13.3.8 and just received the same error today. Did I jump the gun compiling a beta version?

I'm pretty sure this particular issue was fixed quite a while ago. v13.3 is a version that was never released to the public so you might as well go to v14.1 because we will not fix any bugs for you in that version. What email service are you using? What port are you using and is the SSL box checked?

jsalmon wrote:I'm pretty sure this particular issue was fixed quite a while ago. v13.3 is a version that was never released to the public so you might as well go to v14.1 because we will not fix any bugs for you in that version. What email service are you using? What port are you using and is the SSL box checked?

I just started using Office365 because I was told it was HIPAA compliant. I folled their instructions on their tech site:

http://technet.microsoft.com/en-us/libr ... 54323.aspx

Outgoing Port 25, Incoming Port 995, outgoing server smtp.office365.com, incoming server outlook.office365.com, and SSL button checked.

Would you suggest a different email for HIPAA compliance? Goggle Apps for business?

I think you should be using outbound port 587, not 25, as a lot of ISPs block port 25 to combat spam.

Office 365 is HIPAA compliant, but you'll need to sign a business associate agreement with them.

I realize this is not an OD issue, but since we are on the topic of Office 365, I am a bit confused. Regarding Office 365 being Hipaa compliant, assuming you signed a BAA with MS, can you send PHI (protected health info) from Outlook in Office 365? Is that encrypted and Hipaa compliant? Do you have to do anything else special to make it compliant?

wjstarck wrote:...you should be using outbound port 587...

Based on a lot of forums I've come across, they all seem to mention using port 587 is best.

I also stumbled upon this little gem:

Office 365 is SUPER picky about the message’s From Name. It needs to match the account you are logging in as. BUT it needs to match BOTH the From Name as well as the From Address.

So maybe make sure your Username and E-mail address of sender are identical in the email setup window?
http://www.opendental.com/manual/emailsetup.html

How is the new encrypted email in 14.1 working? What are the requirements for it to be HIPAA compliant?

One word... Direct
http://www.opendental.com/manual/directstandard.html

ONC and most likely CMS have decided (for EHR systems) that Direct is what everyone is going to use for HIPAA compliant practice to practice communications.
So in theory, sending secure email / patient information to other EHR systems will be a warm tropical breeze. However, you won't be able to send secure email to your patients.

Well... unless they implement Direct, accept your public certificate, etc. and lets face it. That's just not going to happen. Therefore, they can use our patient portal to send secure messages directly to their primary provider!

Patient Portal??? Hmmm....http://www.opendental.com/manual/patientportal.html

Since it's not available till 14.2 how difficult is it to host our own patient portal?


"Purchase and install a certificate from any certificate authority for a few hundred dollars."

Are certificates really a few hundred or can we use the $10 ones from enom Rapid SSL?

B.Thomas wrote:...how difficult is it to host our own patient portal?

That's like asking how hard is it to understand quantum physics. For some it's probably easy as pie, for others... not so much.
For tech savvy people I'd say its roughly a 7 out of 10 difficulty. Which is why in 14.2 we're going to have it so users only have to open one port on their router and push a button within OD and we'll do all the heavy lifting.

B.Thomas wrote:Are certificates really a few hundred or can we use the $10 ones from enom Rapid SSL?

Self signed certs are free. So um... yeah, I'd imagine there are cheap ones and expensive ones. Much like buying vehicles.

I had Office 365 working for a while through open dental but now I am receiveing error messages stating "The SMTP server requires a secure connections". I tried checking the SSL box in email settings with the same result. I contacted Microsoft and they stated the email client needs TLS support. Is this an something open dental can do or is it a requested feature?

A lot of times email providers will host two different kinds of SSL (or TLS) for SMTP on different ports. Open Dental can usually talk with either, but some seem to throw a tantrum every now and again. You might Google what SSL SMTP ports are available for your email provider and try the other port option (there are often two to choose from) that you are not using and see if that works.

Off the top of my head I think the two ports used most often are 25 and 465

I had to drop Office 365. Microsoft requires one of two options which neither worked:

1) Open Dental to have TLS support
2) Use the less secure route of using port 25 which my internet provider (Verizon) completely blocks

I will give Google Apps a try.