Unable to get SMTP working with GoDaddy **solved**

[mikejeep]

I am using Meteobridge 3.1 (Aug 17 2016, build 10256) on a TP-Link TL-MR3020. It works wonderfully except I cannot get SMTP push services to work. My hosting provider is GoDaddy. After consulting with GoDaddy support, I have not made any progress. I have the server (smtpout.secureserver.net), port (3535), username (my email), and password correct. The authentication settings I have tried are as follows:

none

Code: Select all

msmtp: server message: 530 authentication required msmtp: could not send mail

This makes sense, as I know authentication is required by GoDaddy.


basic

Code: Select all

msmtp: cannot use a secure authentication method msmtp: could not send mail

This does not make sense; I would expect this authentication method to work but the error message does not seem clear.


tls or starttls

Code: Select all

msmtp: the server does not support TLS via the STARTTLS command msmtp: could not send mail

This is not surprising, as GoDaddy states to use SSL on a different port...


If I try to use their given secure port (465) with any authentication

Code: Select all

msmtp: network read error: the operation timed out msmtp: could not send mail

If I attempt to reach the server via telnet:465, it works, so not sure why Meteobridge cannot reach it.


I had also tried this on a previous Meteobridge release (August 9 I believe) with the same results. Any help would be appreciated. Thanks!

-Mike

[admin]

Seems to be a problem with the setup of the godaddy mail account.

Please read here on page 3: https://discussions.apple.com/thread/51 ... 0&tstart=0

[mikejeep]

Thanks; I've been working with GoDaddy and they claim there are no issues. I am able to use other applications on the same network for SMTP relay without any trouble.

The 'basic' authentication method apparently sends the password in a manner that GoDaddy's non-SSL connections do not permit, hence the error message from msmtp on the Meteobridge (see here: https://sourceforge.net/p/msmtp/mailman/message/649438/).

I'd prefer to use SSL (TLS/STARTTLS) anyway, but as I mentioned, the Meteobridge is timing out when attempting to connect to port 465. I disabled my router firewall and successfully used applications to connect to 465, that's why I was curious if there was possibly an issue with the Meteobridge.

I will keep researching but I'd appreciate any suggestions anyone might have. I'm sure there are plenty of Meteobridge users using SMTP without any trouble.

Thanks,
-Mike

[admin]

When you are fine with using the linux shell, you might experiment directly to send smtp connects from there.

This is what meteobridge does when sending a mail (to/from are my meteobridge email accounts to be changed, host and user masked by XXXX):

Code: Select all

echo -ne 'date: Sat, 20 Aug 2016 11:03:00 +0200\nto: info@meteobridge.com\nfrom: info@meteobridge.com\nsubject: TEST\nContent-Type: text/plain; charset=utf-8\n\n' | /home/msmtp/msmtp --read-recipients --timeout=10 --auth=on --tls=on --tls-starttls=on --host=XXXX --port=587 --user='XXXXX' --passwordeval=/home/msmtp/getpasswd --tls-certcheck=off --from=info@meteobridge.com

May be that makes testing more easy. When you get it working, please let us know what needs to be changed for godaddy.

[mikejeep]

Thank you, that is very helpful! I will do some testing next week. At first glance, changing auth=on to auth=plain may do the trick, but I would like to do some testing to confirm that.

Just to be clear, if the user has selected 'basic' authentication, the tls=on and tls-starttls=on flags would be set to off, correct?

Thanks,
-Mike

[mikejeep]

I believe that my initial thoughts may be correct. Would it be possible to add a 'plain' authentication option that sets "auth=plain" instead of "auth=on" in the msmtp command string, but otherwise keeps the same options as the 'basic' option?

As I asked above, if the user has selected 'basic' authentication, the tls=on and tls-starttls=on flags would be set to off, correct? It would appear that might be causing the issue as well.

Thanks,
-Mike

[mikejeep]

When you get it working, please let us know what needs to be changed for godaddy.

Admin, just curious if my suggestion above (add a 'plain' authentication option that sets "auth=plain" instead of "auth=on") could be considered for a future version? I believe that might do the trick but it is difficult to test as I don't have access to a true linux shell. I could create a temporary SMTP account for you to test if that would be better. Thanks!

Thanks,
-Mike

[admin]

yes, please setup a temporary smtp account at godaddy for me, so that I can test changes before going into production with it.

[mikejeep]

Thank you, Boris! This issue is fixed by using the "plain" e-mail authentication option available from build 10434 and later.

-Mike