I think I’ve uncovered a bug in Internet Commands. When setting up the code to send a new email, I use this command:
$lError:=IT_SetPort (12;465) which should enable SSL and have the SMTP_Send command use port 465. When I see what is actually going on using Wireshark, I see that 4D is ignoring my request to use port 465 and tries to connect on port 25 instead. I haven’t noticed this bug for years because my previous email host allowed port 25 as a fallback. My new one (I think correctly) does not, so the SMTP server rejects my attempt to connect to it. I’ve created a tech support case, but am wondering if anyone else has noticed this or figured out any workarounds. Thanks. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Dec 6, 2017, at 4:17 PM, Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Is anyone using 4D to send email through a FastMail account? I just switched > an email address to FastMail and think I have things set up in 4D to send to > it through the smtp server, but it isn’t working. Using WireShark I can see > it connects to the server on the TCP level, but that’s about all that happens > until it times out. I’m wondering if there are any tricks I’m missing. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************