Jump to content

An error occurred: Invalid Addresses:.....


taylorsharpe
 Share

This topic is 2826 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I am using FMPA 13.0v5 with 360Works Email plugin v2.11 on a Mac Pro 10.10.2.  Actually, I mostly use the CNS plugin, but since I like some of the other 360Works plugins, I thought I would give this a try.  

 

I am running on another machine my Mac Mini Mail Server with SMTP on it, SSL, TLS, and a verified SSL certificate (Comodo).   

 

I can connect to this server using port 587 and TLS using both the CNS plugin and FileMaker's Send Mail script step, and both work just fine.  

 

When I run it on 360 Email, I keep getting an error saying I have Invalid Addresses that I am trying to send to.  To make things simple, I am sending to a single email.  Since it didn't like my company email, I tried my gmail one to no avail.  I made sure there were no spaces or anything wrong and even ran the IsValidEmail to confirm the email to send was valid.  

 

Normally the send email is grouped into one Set Variable script step and I couldn't tell where it was going wrong.  So I broke everything down into simple steps:  EmailRegister, EmailConnectSMTP, EmailCreate, EmailSetBody, EmailSend and EmailDisconnect.  They all return the result of 1 for successful except the EmailSend.  It returns a 0 and if I ask the EmailLastError, I get the "An error occurred:  Invalid Address:  [email protected]" (one of several emails I tried).  

 

I finally went to the 360Works Email Plugin Examples file and opened it up.  I click the connect Advanced connect and turn on StartTLS and put the host name in, my user name and password and press connect.  It works.  

 

I fill out the "Quick Send" example and press Send and I get the same error that I get when I made my own script.  I tried different emails to no avail.  I tried the Send HTML email too and it failed also with the same error.  

 

I guess I don't have to use this plugin, but wonder what I might be doing wrong since the FileMaker Email script step works and so does the CNS email plugin.  The main reason for using the plugin is for HTML support.  

 

Any suggestions on what I may be doing wrong or what to try would be appreciated.  Thanks.

 

TAYLOR SHARPE

[email protected]

214-522-5525

 

 

EmailRegister("###My License No.###"; "Taylor Made Services") and

EmailConnectSMTP( "taylormadeservices.com" ; "###UserName###" ; "###Password###" ; "tls=true" ) and

EmailCreate( "[email protected]" ; "[email protected]" ; "Some Subject Name" ) and

   //  I make sure the from and to are not the same on my tests and that they are valid 

EmailSetBody( GetAsCSS( $HTML ); "html" ) and

EmailSend and

EmailDisconnect

 

 

 

 

 

Link to comment
Share on other sites

Hi Taylor - nice to see you here!! 

 

Are you sure you want to put your personal information in an open forum message?  It is quite possible that you will get more than you bargained for. :-)

Link to comment
Share on other sites

Since this error is coming on the EmailSend function, and not on the EmailCreate function, it seems like it's an error coming from the SMTP server in question. Are you using the same SMTP information in your tests with the Filemaker script step and CNS plugin? If so, I would be surprised to see that it was working for them. If you can attach your plug log (which should be at ~/Library/Logs/360Plugin Logs/360Plugin_FMAdvanced.log ), I can see if there's more information in there, but I would expect your SMTP server logs would be more elucidating. 

Link to comment
Share on other sites

360Plugins_FMAdvanced.txt

 

Yes, I am rather certain I am putting the information in correctly.  Then again, I am new to this plugin and it could be misunderstanding something obvious and may eat crow about it.  But I certainly have no problem getting this to work on CNS, Dacons and FileMaker sending mail functions and only have a problem with 360 Works Email plugin.  I am very familiar with running SMTP servers and do this for many servers.  So obviously this is an issue with my understanding of this particularly plugin or there is a technical issue because I set this up on machines quite regularly every week.  

 

I am attaching the log file (had to change the extension to .txt so it would upload here).  Note line 216 is where the failure occurs and it simply says "Invalid Addresses:  [email protected]".  This is one of several emails I have tested and they all fail the same way.  Below in line  230, the com.sun.mail.smtp.SMTPAddressFailedException says that it needs a fully qualified hostname, of which that email is fully qualified and so was the gmail address I tested too.  FYI, I tried adding a dot to the end of the email and simply got an error saying I can't have a dot at the end of the email, which should be obvious.  But I was just trying other ways to make sure it was fully qualified.  Maybe you'll see something else in the log file I overlooked.  Any input is appreciated.  

 

 

Since this error is coming on the EmailSend function, and not on the EmailCreate function, it seems like it's an error coming from the SMTP server in question. Are you using the same SMTP information in your tests with the Filemaker script step and CNS plugin? If so, I would be surprised to see that it was working for them. If you can attach your plug log (which should be at ~/Library/Logs/360Plugin Logs/360Plugin_FMAdvanced.log ), I can see if there's more information in there, but I would expect your SMTP server logs would be more elucidating. 

Link to comment
Share on other sites

Hey Laretta... used to seeing you on Technet in the past.  Hope all is well.  Regarding the post, I only used my name and company, which are publicly available hopefully people will pay attention to the company name (www.TaylorMadeServices.com) if they need a FileMaker developer in the Dallas area <grin>.  But the licensing, user IDs and passwords were all removed from my post since that is not appropriate in a public forum.  If only we could be anonymous in life, but I think technology has changed things and I expect to loose even more privacy in the future unfortunately.  

 

 

Hi Taylor - nice to see you here!! 

 

Are you sure you want to put your personal information in an open forum message?  It is quite possible that you will get more than you bargained for. :-)

Link to comment
Share on other sites

FYI, I tried using the GoDaddy server (smtpout.secureserver.net, port 465, ssl) and it worked other than my HTML ended up as plain text, but that was probably my mistake.  

 

I'm still disappointed that the Email plugin doesn't work with the Mac OS X SMTP server when CNS and FileMaker do.  Looking forward to figuring it out so I can make use of it.  Anyone else connecting the 360Works Email server to a Mac OS X SMTP server over TLS connection?

Link to comment
Share on other sites

Okay, so the 'Invalid Addresses' error message is a little misleading. The real problem is, as you noted, the line farther down:

504 5.5.2 <192.168.1.11>: Helo command rejected: need fully-qualified hostname

This is an error message from your OS X Server indicating that the hostname that your client (our plugin, in this case) identified with isn't a fully qualified domain name. Indeed, from this message, you can see that the hostname we gave was '192.168.1.11', which isn't a FQDN.

 

There are two ways you can keep this from happening. One way is to remove the default requirement of OS X Server to require fully qualified hostnames. You can find good information how to do this at http://topicdesk.com/faqs/os-x-server-mail-services-faq/188-helo-command-rejected. The changes made on this site allow users without FQDNs to connect as long as they authenticate (which from your log, I can see you're doing) or if their inside the local network (which you also are), so you're not losing much security, if any.

 

The alternative to that is to add a fully qualified hostname to the hosts file on your FMPro machine, which should be /etc/hosts on OS X. The Javamail library, which we use, grabs the hostname from this file, so if you add an entry that looks like this:

192.168.1.11 client.serverhost.com

then Javamail should pick that up automatically and you should be able to send successfully. The downside to this method is that you'd need to do this for any client who wants to use the plugin.

 

Please let me know if you have any more questions!

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

This topic is 2826 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.